From: Pete Zaitcev <zaitcev@redhat.com>
To: green@linuxhacker.ru, laughing@shared-source.org (Alan Cox),
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.5-ac7
Date: Sun, 3 Jun 2001 16:51:42 -0400 [thread overview]
Message-ID: <200106032051.f53Kpgg10681@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.991555081.25242.linux-kernel2news@redhat.com>
In-Reply-To: <mailman.991555081.25242.linux-kernel2news@redhat.com>
> AC> 2.4.5-ac7
> AC> o Make USB require PCI (me)
> How about people from StrongArm sa11x0 port, who have USB host controller
> (in sa1111 companion chip) but do not have PCI?
> Probably there are more such embedded architectures with USB controllers,
> but not PCI bus.
There is nothing that would bind USB to PCI architecturally.
OHCI and UHCI are PCI based, but that's just a matter of
implementation. I think that Alan was unwise at this point.
I know that some small Motorola parts (relatives of 860, perhaps)
do have USB controllers, but I have no idea if PCI is involved.
> How about ISA USB host controllers?
Those, unfortunately, do not exist. I was shopping for one
in vain for a long time. One formiddable difficulty is that
USB bandwidth is larger than ISA, so the only feasible way
to make a HC is to have all TD's in its onboard memory,
as in VGA.
In other follow-up Alan argued in favor of CONFIG_PCI for
a PCI-less machine. It may be a reasonable approach, for
instance JavaStation-1 has no PCI but requires CONFIG_PCI.
It adds a little of useless bloat, that I considered a
necessary evil in the abovementioned case.
-- Pete
next parent reply other threads:[~2001-06-03 21:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.991555081.25242.linux-kernel2news@redhat.com>
2001-06-03 20:51 ` Pete Zaitcev [this message]
2001-06-04 12:27 ` Linux 2.4.5-ac7 Pavel Machek
2001-06-05 15:03 ` Dominik Kubla
2001-06-03 15:49 Wayne.Brown
2001-06-04 20:10 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-06-03 12:04 Mikael Pettersson
2001-06-02 23:23 Alan Cox
2001-06-03 7:46 ` Oleg Drokin
2001-06-03 11:19 ` Alan Cox
2001-06-03 12:33 ` Russell King
2001-06-03 14:02 ` Oleg Drokin
2001-06-03 14:45 ` Alan Cox
2001-06-03 14:51 ` Oleg Drokin
2001-06-03 14:54 ` Alan Cox
2001-06-04 1:49 ` lists
2001-06-03 13:59 ` Oleg Drokin
2001-06-04 17:56 ` Tom Rini
2001-06-04 17:59 ` Alan Cox
2001-06-04 18:49 ` Nicolas Pitre
2001-06-03 18:16 ` Philip Blundell
2001-06-03 20:50 ` Tom Rini
2001-06-04 12:37 ` Geert Uytterhoeven
2001-06-04 12:59 ` johan.adolfsson
2001-06-03 14:56 ` Nicolas Pitre
2001-06-03 15:03 ` Alan Cox
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=200106032051.f53Kpgg10681@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=green@linuxhacker.ru \
--cc=laughing@shared-source.org \
--cc=linux-kernel@vger.kernel.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