From: Sven Luther <sven@genesi-usa.com>
To: Matt Sealey <matt@genesi-usa.com>,
linuxppc-dev <Linuxppc-dev@ozlabs.org>
Cc: sven@genesi-usa.com
Subject: Re: USB support on mpc5200 broken
Date: Mon, 29 Sep 2008 17:18:54 +0200 [thread overview]
Message-ID: <20080929151854.GA29375@powerlinux.fr> (raw)
In-Reply-To: <20080929034329.GB8694@yookeroo.seuss>
On Mon, Sep 29, 2008 at 01:43:29PM +1000, David Gibson wrote:
> On Sun, Sep 28, 2008 at 08:30:56PM -0500, Matt Sealey wrote:
> >
> > Benjamin Herrenschmidt wrote:
> >> On Wed, 2008-09-24 at 21:09 -0400, Jon Smirl wrote:
> >>>> Last time I noticed it was working was about ten days ago. I don't use
> >>>> it everyday.
> >>> Efika is broken because of this:
> >>>
> >>> ohci-ppc-of.c...
> >>> is_bigendian =
> >>> of_device_is_compatible(dn, "ohci-bigendian") ||
> >>> of_device_is_compatible(dn, "ohci-be");
> >>>
> >>> Efika doesn't have either of those in it's compatible string.
> >>>
> >>> This doesn't look to me like a very reliable way to determine bigendian.
> >>
> >> You mean it's not reliable to expect people device-trees not to
> >> suck ? :-)
>
> Alas, this is true :(.
>
> > It's reasonable to expect that device-trees do not get updated with the
> > kernel for certain platforms (it does not fit into most quality assurance
> > schedules to reflash every user's firmware every time they want to move up
> > one revision to another, given the kernel release schedule of every 3-4
> > months) and when updating the search for compatible entries it should
> > take into account these platforms.
>
> This, of course, is exactly why I *don't* recommend embedded platforms
> move to including the device tree in the flashed firmware. Keeping
> the device tree in the bootwrapper means that it *is* updated with the
> kernel and we don't have to mess around with as much backwards
> compatibility junk.
This completely defeats the purpopse of having a separate device tree
though, no ? I mean, we could just as well hardcode the device-tree info
in the kernel in this case ?
(In embedded cases, the kernel is usyually in the flash as well, so you
just upgrade both at the same time :)
Friendly,
Sven Luther
next prev parent reply other threads:[~2008-09-29 15:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 21:51 USB support on mpc5200 broken Jon Smirl
2008-09-25 1:09 ` Jon Smirl
2008-09-25 1:50 ` Benjamin Herrenschmidt
2008-09-25 2:40 ` Jon Smirl
2008-09-29 1:30 ` Matt Sealey
2008-09-29 3:43 ` David Gibson
2008-09-29 14:14 ` Jon Smirl
2008-09-29 14:22 ` Peter Korsgaard
2008-09-29 14:28 ` Jon Smirl
2008-09-29 15:07 ` Peter Korsgaard
2008-09-29 20:18 ` Scott Wood
2008-09-29 21:04 ` Jon Smirl
2008-09-29 22:02 ` Grant Likely
2008-09-30 15:20 ` Matt Sealey
2008-10-01 3:31 ` Benjamin Herrenschmidt
2008-10-01 9:46 ` Carsten Schlote
2008-10-01 10:36 ` Benjamin Herrenschmidt
2008-10-06 21:06 ` Matt Sealey
2008-09-29 15:18 ` Sven Luther [this message]
2008-09-29 17:05 ` Peter Korsgaard
2008-09-30 1:12 ` David Gibson
2008-09-30 1:24 ` Raquel and Bill
2008-09-30 15:15 ` Matt Sealey
2008-11-03 15:41 ` Grant Likely
2008-11-03 16:21 ` Jon Smirl
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=20080929151854.GA29375@powerlinux.fr \
--to=sven@genesi-usa.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=matt@genesi-usa.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).