linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/44x: Fix address decoding setup of PCI 2.x cells
Date: Wed, 04 Feb 2009 07:55:08 +1100	[thread overview]
Message-ID: <1233694508.16867.86.camel@pasglop> (raw)
In-Reply-To: <alpine.LRH.2.00.0902031616130.21407@vixen.sonytel.be>


> Could it be my USB failures were due to the PPC440 USB host needing the various
> CONFIG*USB*BIG_ENDIAN* options, which may conflict with USB hosts on PCI
> plug-in cards?
> 
> The E1000 did work fine.

You need to enable support for both endians, that's supposed to work.

Ben.

  reply	other threads:[~2009-02-03 20:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02  0:24 [PATCH] powerpc/44x: Fix address decoding setup of PCI 2.x cells Benjamin Herrenschmidt
2009-02-02 12:13 ` Geert Uytterhoeven
2009-02-03 15:10 ` Josh Boyer
2009-02-03 15:19   ` Geert Uytterhoeven
2009-02-03 20:55     ` Benjamin Herrenschmidt [this message]
2009-02-17 12:37   ` Geert Uytterhoeven

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=1233694508.16867.86.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=Geert.Uytterhoeven@sonycom.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 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).