From: Steven Scholz <steven.scholz@imc-berlin.de>
To: "Williams, Kevin M." <kevin.m.williams@marconi.com>
Cc: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: USB and MPC855T/860T ???
Date: Mon, 29 Oct 2001 10:35:22 +0100 [thread overview]
Message-ID: <3BDD22DA.125C6EBB@imc-berlin.de> (raw)
In-Reply-To: A3E34B558F5CD211B4980008C7A4A99003C584CD@sparrow.gso.mcs.marconi.com
"Williams, Kevin M." wrote:
> Search the linux-usb-devel mailing list at sourceforge for "1161" and you
> should find source posted by Roman Weissgaerber for a Philips ISP1161. It's
> the only non-OHCI/UHCI external USB host controller I know of with a Linux
> Driver.
Thanks.
But why should I use a non-OHCI/UHCI external USB host controller?
Are there huge advantages of this solution?
Or big drawbacks when using a a UHCI chip?
Cheers,
Steven Scholz
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-29 9:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-26 16:54 USB and MPC855T/860T ??? Williams, Kevin M.
2001-10-29 9:35 ` Steven Scholz [this message]
2001-10-29 9:39 ` Steven Scholz
-- strict thread matches above, loose matches on Subject: below --
2001-10-26 7:37 Steven Scholz
2001-10-26 8:00 ` Frederic Soulier
2001-10-26 16:24 ` Steven Scholz
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=3BDD22DA.125C6EBB@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=kevin.m.williams@marconi.com \
--cc=linuxppc-embedded@lists.linuxppc.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).