All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Williams <steve@icarus.com>
To: Matt Porter <mporter@kernel.crashing.org>, linuxppc-embedded@ozlabs.org
Subject: Re: PPC 405GPr support in linux 2.4.32
Date: Thu, 27 Apr 2006 11:32:45 -0700	[thread overview]
Message-ID: <44510E4D.5040504@icarus.com> (raw)
In-Reply-To: <20060427180743.GB11206@gate.ebshome.net>

Eugene Surovegin wrote:
> There are bigger problems with 4xx support in 2.4 mainline than just 
> missing some chips support.
> 
> Some parts which are already in 2.4 (e.g. ethernet driver) are of 
> non-production quality. 
> 
> I can imagine Marcelo agreeing to commit 405GPr/405EP support as this 
> change shouldn't break anything, but this will not make 2.4 support 
> really useful for real world deployments. I think we are stuck with 
> maintaining our own 2.4 trees with backports from 2.6. This is what I 
> do myself of all our products (and yeah, diff between stock 2.4.32 and 
> my internal version has already grown quite big to be acceptable for 
> 2.4 inclusion).
> 

Of course we are going to have to keep our own per-board trees.
but the blatantly common stuff, like the core 405gpr support and
certain drivers, might as well go in if the gatekeeper can be
convinced. You and I both probably have huge drivers for custom
devices hanging off our PPCs, with various hacks to squeeze extra
performance out. These make our transition to 2.6 difficult, and
surely we are not alone.

So 2.4 is going to be around for a while longer for us, so we might
as well make an effort to keep the house in some sort of order. It
serves no one to keep these fixes a secret:-)

In any case, if the patches I sent are rejected, then that's that.
We'll see.

-- 
Steve Williams                "The woods are lovely, dark and deep.
steve at icarus.com           But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."

  reply	other threads:[~2006-04-27 18:54 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 [this message]
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 ` PPC 405GPr support in linux 2.4.32 Tolunay Orkun
2006-04-27 16:48 ` 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=44510E4D.5040504@icarus.com \
    --to=steve@icarus.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=mporter@kernel.crashing.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.