linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Scott Wood <scottwood@freescale.com>,
	linuxppc-dev <Linuxppc-dev@ozlabs.org>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: USB support on mpc5200 broken
Date: Mon, 29 Sep 2008 16:02:28 -0600	[thread overview]
Message-ID: <20080929220228.GA18313@secretlab.ca> (raw)
In-Reply-To: <9e4733910809291404y1b5f14b6j3f9d29cda6ce4bd5@mail.gmail.com>

On Mon, Sep 29, 2008 at 05:04:22PM -0400, Jon Smirl wrote:
> On Mon, Sep 29, 2008 at 4:18 PM, Scott Wood <scottwood@freescale.com> wrote:
> > On Mon, Sep 29, 2008 at 10:14:18AM -0400, Jon Smirl wrote:
> >> Shouldn't the driver already know it is being used on a BE machine?
> >
> > No.  Endianness of the CPU is not necessarily the same as the endianness
> > of device registers.
> >
> > For example, PCI OHCI on a big-endian host.
> 
> Endianess is encoded in the specific compatible string.
> 
> compatible = "fsl,mpc5200b-ohci","fsl,mpc5200-ohci";
> This is BE.
> 
> inside PCI bus section
> compatible = "my-pci-ohci-card"
> This would be LE
> 
> The specifically loaded driver knows it's endianess.
> 
> But now you're tell me I need
> compatible = "fsl,mpc5200b-ohci","fsl,mpc5200-ohci",  "ohci-be"

No, we can't do that.

You're right about the current data in compatible being sufficient.
The kernel needs to deal with what firmware hands it,
either by fixups to the device tree data or by teaching the driver
what fsl,mpc5200b-ohci means.

g.

  reply	other threads:[~2008-09-29 22:02 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 [this message]
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=20080929220228.GA18313@secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=jonsmirl@gmail.com \
    --cc=scottwood@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).