All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Sealey <matt@genesi-usa.com>
To: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: USB support on mpc5200 broken
Date: Sun, 28 Sep 2008 20:30:56 -0500	[thread overview]
Message-ID: <48E02FD0.8000809@genesi-usa.com> (raw)
In-Reply-To: <1222307447.8277.147.camel@pasglop>


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 ? :-)

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.

We had this discussion a few months back (just before I released the
last version of the device tree supplement script) when patches were
being submitted that broke detection. It was agreed that at least one
of the Efika compatibles should stay in there, mostly likely the least
insane one.

The same patch also introduced a big-endian property to replace the
stupid encoding of endianness into the controller compatible entries,
and we all though that was a great idea. "ohci-bigendian" is simply
wrong by this regard, and if the policy has changed since then, then
we are looking at yet another device tree policy flip-flop which is
starting to move more towards annoying, than being simply an acceptable
fact of life due to the Linux development process.

Jon, just use efika.forth from http://www.powerdeveloper.org/ and add
in the appropriate entry, or make a snippet for it and add it to nvramrc.

If it doesn't work, bug me about it and I will release an update as I
have one which goes way overboard and includes every variation for
compatible USB drivers and tries to make gpio fit the new gpio specs
and i2c and can buses exposed.

-- 
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations

  parent reply	other threads:[~2008-09-29  1:30 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 [this message]
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
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=48E02FD0.8000809@genesi-usa.com \
    --to=matt@genesi-usa.com \
    --cc=Linuxppc-dev@ozlabs.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.