From: Julian Calaby <julian.calaby@gmail.com>
To: Sean MacLennan <smaclennan@pikatech.com>
Cc: linuxppc-dev@ozlabs.org, Richard Purdie <rpurdie@linux.intel.com>,
sparclinux@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Trent Piepho <tpiepho@freescale.com>
Subject: Re: "leds: Add openfirmware platform device support" breaks sparc
Date: Wed, 4 Mar 2009 11:40:50 +1100 [thread overview]
Message-ID: <646765f40903031640x39b3361fic8833a4bf15b1381@mail.gmail.com> (raw)
In-Reply-To: <20090303192932.31705cf7@lappy.seanm.ca>
On Wed, Mar 4, 2009 at 11:29, Sean MacLennan <smaclennan@pikatech.com> wrote:
> On Tue, 3 Mar 2009 16:09:06 -0800
> "Andrew Morton" <akpm@linux-foundation.org> wrote:
>
>> afacit that interface is powerpc-only.
>
> Yes it is. You might want a CONFIG_PPC with that.
>
> It has been..... uhhhh carry the two... longer than I want to admit
> since I worked on a sparc. Would GPIO based LEDS make sense on a sparc
> platform? Is sparc used much in the embedded world?
>
> If yes, the of_register_platform_driver is just a nice wrapper. It
> would be trivial to either change it to work on sparc, or add the
> wrapper to the sparc includes.
These inconsistencies are causing more problems with PPC drivers
depending on the generic infrastructure.
See: http://lkml.org/lkml/2009/1/11/376 for a similar issue.
Thanks,
--
Julian Calaby
Email: julian.calaby@gmail.com
.Plan: http://sites.google.com/site/juliancalaby/
prev parent reply other threads:[~2009-03-04 0:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 0:09 "leds: Add openfirmware platform device support" breaks sparc Andrew Morton
2009-03-04 0:15 ` Grant Likely
2009-03-04 0:28 ` Andrew Morton
2009-03-04 0:29 ` Sean MacLennan
2009-03-04 0:37 ` David Miller
2009-04-27 22:20 ` Andrew Morton
2009-04-28 3:59 ` Grant Likely
2009-04-28 9:01 ` David Miller
2009-03-04 0:40 ` Julian Calaby [this message]
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=646765f40903031640x39b3361fic8833a4bf15b1381@mail.gmail.com \
--to=julian.calaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rpurdie@linux.intel.com \
--cc=smaclennan@pikatech.com \
--cc=sparclinux@vger.kernel.org \
--cc=tpiepho@freescale.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).