linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: pterry@micromemory.com
Cc: Linuxppc-dev@ozlabs.org, David Woodhouse <dwmw2@infradead.org>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: Patches for ppc?
Date: Tue, 21 Aug 2007 20:09:43 +0200	[thread overview]
Message-ID: <a027a1e105da18fb17125235332c8504@kernel.crashing.org> (raw)
In-Reply-To: <1187716337.13726.48.camel@pterry-fc6.micromemory.com>

> So then I get worried, how do I know
> who's plan and schedule include/excludes my board/chip/issue?

The arch/ppc -> arch/powerpc changeover is exceptional for various
reasons.

First, it is a huge change taking multiple years to complete.
Only recently it has been decided when to finally drop arch/ppc
completely; and that's not going to happen until almost a year
from now.

Secondly, it really does change many things at the core.  It
is almost impossible for people without in-depth knowledge of
specific hardware too correctly port support code for that
hardware over those core changes, and certainly impossible to
actually test the ported code.  So the only sane approach was
to only port the hardware support code people _did_ have access
to.  Which isn't to say the other platforms still "in demand"
will be left behind of course, some are still being ported over,
and there is nothing preventing such a port even after arch/ppc
is dead and gone either.

Thirdly, Greg KH is talking more about generic drivers (PCI
device drivers, for example) than about low-level platform code;
at least that's my impression.  The good news is that in the
arch/powerpc world much more of the low-level stuff will be
abstracted away, or at least sanely abstracted at all, so in
the future we won't have all that many problems making even
the biggest core changes anymore.

> I was trying to raise that generic issue, which is why I tried to be
> generic. Didn't mean to gore anyones ox.

Don't worry, you didn't offend anyone as far as I can see :-)

All of the "more generic" stuff (e.g., CPU/SoC support) should
be ported over soon enough (if not, shout); some more specific
stuff (support for some specific board, etc.) you will have to
do yourself, or find someone else to do it for you.  And you can
always ask for help here, we're all very helpful and friendly
here (if you believe that ;-) )


Segher

  parent reply	other threads:[~2007-08-21 18:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-17  7:43 Patches for ppc? Johan Borkhuis
2007-08-17  8:00 ` Kumar Gala
2007-08-17 12:26 ` David Woodhouse
2007-08-17 14:36   ` Johan Borkhuis
2007-08-17 14:40     ` David Woodhouse
2007-08-17 14:43       ` Johan Borkhuis
2007-08-17 23:28         ` Satya
2007-08-21  5:25           ` David Gibson
2007-08-21 15:14             ` Segher Boessenkool
2007-08-21 16:11               ` Phil Terry
2007-08-21 16:35                 ` Josh Boyer
2007-08-21 16:40                 ` Kumar Gala
2007-08-21 17:12                   ` Phil Terry
2007-08-21 17:30                     ` Scott Wood
2007-08-21 18:09                     ` Segher Boessenkool [this message]
2007-08-21 17:22                 ` Linas Vepstas

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=a027a1e105da18fb17125235332c8504@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=dwmw2@infradead.org \
    --cc=pterry@micromemory.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).