public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Oleg Drokin <green@linuxhacker.ru>,
	Alan Cox <laughing@shared-source.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.5-ac7
Date: Sun, 3 Jun 2001 13:33:33 +0100	[thread overview]
Message-ID: <20010603133333.A25478@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200106030746.f537kSZ12820@linuxhacker.ru> <E156VvF-0004D1-00@the-village.bc.nu>
In-Reply-To: <E156VvF-0004D1-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sun, Jun 03, 2001 at 12:19:52PM +0100

On Sun, Jun 03, 2001 at 12:19:52PM +0100, Alan Cox wrote:
> > AC> 2.4.5-ac7
> > AC> o       Make USB require PCI                            (me)
> > Huh?!
> > How about people from StrongArm sa11x0 port, who have USB host controller (in
> > sa1111 companion chip) but do not have PCI?
> 
> The strongarm doesnt have a USB master but a slave.

Alan, a StrongARM 11x0 with its companion SA11x1 chip is a USB master.
Last time I looked, it was supported:

diff -urN 2.4.5-rmk2/linux/drivers/usb/usb-ohci-sa1111.h linux/drivers/usb/usb-ohci-sa1111.h
--- 2.4.5-rmk2/linux/drivers/usb/usb-ohci-sa1111.h      Wed Dec 31 19:00:00 1969
+++ linux/drivers/usb/usb-ohci-sa1111.h Tue May 29 16:49:47 2001
@@ -0,0 +1,692 @@
+/*
+ * usb-ohci-sa1111.h
+ *
+ * definitions and special code for Intel SA-1111 USB OHCI host controller
+ *
+ * 10/24/00 Brad Parker <brad@heeltoe.com>
+ * added memory allocation code
+ *
+ * 09/26/00 Brad Parker <brad@heeltoe.com>
+ * init code for the SA-1111 ohci controller
+ * special dma map/unmap code to compensate for SA-1111 h/w bug
+ *
+ */

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2001-06-03 13:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-02 23:23 Linux 2.4.5-ac7 Alan Cox
2001-06-03  7:46 ` Oleg Drokin
2001-06-03 11:19   ` Alan Cox
2001-06-03 12:33     ` Russell King [this message]
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-05 11:50       ` USB requiring PCI Bjorn Wesen
2001-06-03 14:56   ` Linux 2.4.5-ac7 Nicolas Pitre
2001-06-03 15:03     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2001-06-03 12:04 Mikael Pettersson
2001-06-03 15:49 Wayne.Brown
2001-06-04 20:10 ` Alan Cox
     [not found] <mailman.991555081.25242.linux-kernel2news@redhat.com>
2001-06-03 20:51 ` Pete Zaitcev
2001-06-04 12:27   ` Pavel Machek
2001-06-05 15:03     ` Dominik Kubla

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=20010603133333.A25478@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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