From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Jon Smirl" <jonsmirl@gmail.com>
Cc: PowerPC dev list <Linuxppc-dev@ozlabs.org>
Subject: Re: ppc vs powerpc
Date: Mon, 10 Dec 2007 13:59:39 -0700 [thread overview]
Message-ID: <fa686aa40712101259h22be4b89ke4f36564a7c1866c@mail.gmail.com> (raw)
In-Reply-To: <9e4733910712101254r1bf8925o20ee6eacd3af6a18@mail.gmail.com>
On 12/10/07, Jon Smirl <jonsmirl@gmail.com> wrote:
> Is the plan for ppc to be completely merged with powerpc and then be
> eliminated? If so, how close is this to completion?
>
> What should we do with ppc users of mpc-i2c? If the plan is to
> eliminate ppc I would say to just copy the existing driver and then
> delete the old version when the rest of ppc gets deleted.
arch/ppc is scheduled to be removed middle of 2008. Don't break
arch/ppc users before then. Ideally there should be overlap between
the addition of support in arch/powerpc and the removal of support
from arch/ppc.
Personally, I structure the driver to support both platform bus and
of_platform bus. It's not hard to do and it keeps things
understandable. Take a look at drivers/block/xsysace for an example.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-12-10 20:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 20:54 ppc vs powerpc Jon Smirl
2007-12-10 20:59 ` Grant Likely [this message]
2007-12-10 21:04 ` Jon Smirl
2007-12-10 21:54 ` Jon Smirl
2007-12-10 22:01 ` Tony Breeds
-- strict thread matches above, loose matches on Subject: below --
2008-01-11 12:33 PPC vs POWERPC samppa
2008-01-11 14:52 ` Grant Likely
2008-01-15 10:38 ` Matias Sundman
2008-01-15 17:01 ` Jon Loeliger
2008-01-15 17:07 ` Scott Wood
2008-01-15 17:14 ` Jon Loeliger
2008-01-15 17:47 ` Matias Sundman
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=fa686aa40712101259h22be4b89ke4f36564a7c1866c@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=Linuxppc-dev@ozlabs.org \
--cc=jonsmirl@gmail.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).