linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: How to add platform specific data to a of_device
Date: Mon, 16 Jul 2007 17:40:07 +1000	[thread overview]
Message-ID: <1184571607.8391.18.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <20070716065144.GH1678@pengutronix.de>

[-- Attachment #1: Type: text/plain, Size: 2588 bytes --]

On Mon, 2007-07-16 at 08:51 +0200, Robert Schwebel wrote:
> On Sun, Jul 15, 2007 at 06:48:53AM +1000, Benjamin Herrenschmidt wrote:
> > Your approach would work I suppose.... though it's a bit ugly.
> 
> Speaking of uggly, I'm still wondering why this oftree stuff for powerpc
> must be soooo complicated. If you come from the ARM-linux world like we
> do, the whole powerpc BSP stuff looks like a completely overengineered
> piece of code, introducing complexity where it isn't necessary. But it
> may be that it's just me not knowing powerpc kernel requirements deeply
> enough :)

And I don't know anything about ARM, so let's trade uninformed
opinions ... :)

# cd arch/arm
# du -sk kernel/ mach-* | sort -nk 1
16      mach-l7200
16      mach-s3c2400
24      mach-clps7500
24      mach-s3c2442
32      mach-iop33x
32      mach-rpc
32      mach-shark
36      mach-ebsa110
40      mach-aaec2000
48      mach-h720x
48      mach-ks8695
52      mach-iop32x
56      mach-davinci
60      mach-ixp23xx
60      mach-ns9xxx
60      mach-s3c2443
68      mach-clps711x
68      mach-s3c2412
72      mach-netx
72      mach-realview
72      mach-versatile
76      mach-s3c2440
80      mach-ep93xx
80      mach-imx
88      mach-ixp2000
96      mach-iop13xx
96      mach-lh7a40x
108     mach-pnx4008
124     mach-footbridge
124     mach-integrator
140     mach-ixp4xx
140     mach-s3c2410
252     mach-sa1100
272     mach-omap2
296     mach-omap1
296     mach-pxa
332     mach-at91
428     kernel/

# cd arch/powerpc
# du -sk kernel/ sysdev/ platforms/* | sort -nk 1
8       platforms/prep
12      platforms/4xx
24      platforms/44x
40      platforms/82xx
44      platforms/86xx
52      platforms/8xx
52      platforms/embedded6xx
56      platforms/maple
60      platforms/83xx
64      platforms/85xx
64      platforms/chrp
72      platforms/52xx
72      platforms/pasemi
140     platforms/celleb
212     platforms/ps3
280     platforms/iseries
300     platforms/pseries
412     platforms/powermac
412     sysdev/
544     platforms/cell		(spufs shared with ps3 (and celleb?))
1636    kernel/

Not to mention that ~8 of those platforms can be built into a single
vmlinux that will boot on any of the supported machines, including five
different hypervisors.

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-07-16  7:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-14 16:31 How to add platform specific data to a of_device Juergen Beisert
2007-07-14 20:48 ` Benjamin Herrenschmidt
2007-07-15  8:33   ` Juergen Beisert
2007-07-15  8:57     ` Benjamin Herrenschmidt
2007-07-16 16:13       ` Segher Boessenkool
2007-07-16  6:51   ` Robert Schwebel
2007-07-16  7:09     ` Benjamin Herrenschmidt
2007-07-16  7:19       ` Robert Schwebel
2007-07-16  7:29         ` Benjamin Herrenschmidt
2007-07-16 16:47         ` Segher Boessenkool
2007-07-16 16:28       ` Segher Boessenkool
2007-07-16  7:40     ` Michael Ellerman [this message]
2007-07-16 16:16     ` Segher Boessenkool

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=1184571607.8391.18.camel@concordia.ozlabs.ibm.com \
    --to=michael@ellerman.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=r.schwebel@pengutronix.de \
    /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).