From: Tolunay Orkun <betatester@orkun•us>
To: Stephen Williams <steve@icarus•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: PPC 405GPr support in linux 2.4.32
Date: Wed, 26 Apr 2006 18:48:04 -0500 [thread overview]
Message-ID: <445006B4.2050105@orkun.us> (raw)
In-Reply-To: <e2ov5s$1hn$1@sea.gmane.org>
Stephen Williams wrote:
> ... seems completely missing in the linux-2.3.32 tree from kernel.org.
> This used to be in the linuxppc-2.4 BK tree that no longer exists, so
> what happened to the ppc405GPr support?!
I guess nobody sent patches upstream and development shifted to 2.6
kernel. 405Gpr is not alone. 405EP and a number of other CPU support
that was present never got its way up kernel.org sources.
next prev parent reply other threads:[~2006-04-26 23:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 23:19 PPC 405GPr support in linux 2.4.32 Stephen Williams
2006-04-26 23:35 ` Matt Porter
2006-04-26 23:57 ` Stephen Williams
2006-04-27 18:01 ` Eugene Surovegin
2006-04-27 18:07 ` Eugene Surovegin
2006-04-27 18:32 ` Stephen Williams
2006-04-27 19:04 ` Eugene Surovegin
2006-04-30 16:40 ` Marcelo Tosatti
2006-05-01 15:21 ` Stephen Williams
2006-04-27 18:45 ` Re-configuring busybox that comes with DENX's ELDK SELF Randy Smith
2006-04-26 23:48 ` Tolunay Orkun [this message]
2006-04-27 16:48 ` PPC 405GPr support in linux 2.4.32 Stephen Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=445006B4.2050105@orkun.us \
--to=betatester@orkun$(echo .)us \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=steve@icarus$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox