From: "Dale Farnsworth" <dale@farnsworth•org>
To: vbarshak@ru•mvista.com, Linuxppc-dev@ozlabs•org
Subject: Re: [PATCH] PowerPC 440EPx Sequoia USB OHCI DTS entry
Date: 23 Oct 2007 14:40:00 -0700 [thread overview]
Message-ID: <20071023214000.424.qmail@farnsworth.org> (raw)
In-Reply-To: <471E2CDA.1080301@ru.mvista.com>
Valentine wrote:
> Actually I also don't see much reason for the
> USB_OHCI_HCD_PPC_OF_BE/USB_OHCI_HCD_PPC_OF_LE stuff.
> Is this really needed?
I think so. The SOC host controllers are BE and the PCI
host controllers are LE. Or, do you have an alternative
method of handling both types?
-Dale
next prev parent reply other threads:[~2007-10-23 21:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 14:26 [PATCH] PowerPC 440EPx Sequoia USB OHCI DTS entry Valentine Barshak
2007-10-23 15:33 ` Josh Boyer
2007-10-23 15:35 ` Valentine Barshak
2007-10-23 15:50 ` Josh Boyer
2007-10-23 17:03 ` Segher Boessenkool
2007-10-23 17:18 ` Valentine Barshak
2007-10-23 21:40 ` Dale Farnsworth [this message]
2007-10-24 11:19 ` Valentine Barshak
2007-10-24 12:08 ` Dale Farnsworth
2007-10-24 13:44 ` Valentine Barshak
2007-10-24 14:10 ` Dale Farnsworth
2007-10-24 14:23 ` Valentine Barshak
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=20071023214000.424.qmail@farnsworth.org \
--to=dale@farnsworth$(echo .)org \
--cc=Linuxppc-dev@ozlabs$(echo .)org \
--cc=vbarshak@ru$(echo .)mvista.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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