Hi folks,
Here are a couple of patches against a copy of Greg's usb-2.4 and
usb-2.5 bk trees to add a VID/PID for Omnidirectional Control
Technology's US101 USB to RS-232 converter. This has also been
rebadged by Dick Smith Electronics (New Zealand) as a XH6361 USB to
serial converter.
howdy: a quick question -
does the current linux usb protocol stack
have any support for this?: Mitsubishi M66591
I might be writing a driver for an embedded
single board linux computer with this chip
which in turn talks to a regular usb host computer.
- does the linux-usb stack have
[EMAIL PROTECTED] wrote:
howdy: a quick question -
does the current linux usb protocol stack
have any support for this?: Mitsubishi M66591
I don't know of any drviver for that particular
high speed controller. Someone would have to
write/debug/test the controller driver.
I might be writing
dear David, thanks for a speedy reply!
- does the linux-usb stack have support for
device (=not host contoller) side role?
Yes, see http://www.linux-usb.org/gadget/ for
more information. The frameworks's in stock
2.6 kernels, and is also used on 2.4 kernels.
wondeful :) I'll be
Alan Stern wrote:
Here's a piece from my system log, when I did apm --suspend. The
usb_device_suspend/resume messages are things I added for debugging.
That's progress ... last time I tried APM on 2.6 it failed horribly.
(This was after working fine until recently.)
Why was this routine called
I have a nice USB-2-capable compact flash reader that works perfectly on
my EHCI system, and that I've also verified some time ago on an UHCI setup
(but hey, the UHCI part could have rotted over time).
However, on a HP laptop I have with an ALI southbridge, the USB subsystem
dies badly
There's more to analyize, but on first inspection that babble looks bad.
We submitted a single URB with a 128 byte buffer. We received 64 bytes. I
don't think a babble is actually possible here
So something has gone bad at a lower level
Matt
On Sun, Sep 21, 2003 at 06:41:43PM -0700,
On Sun, 21 Sep 2003, Matthew Dharm wrote:
There's more to analyize, but on first inspection that babble looks bad.
We submitted a single URB with a 128 byte buffer. We received 64 bytes. I
don't think a babble is actually possible here
So something has gone bad at a lower level
Matthew Dharm wrote:
There's more to analyize, but on first inspection that babble looks bad.
We submitted a single URB with a 128 byte buffer. We received 64 bytes. I
don't think a babble is actually possible here
It's possible if the last packet received was bigger than
the endpoint's
On Sun, Sep 21, 2003 at 08:00:07PM -0700, David Brownell wrote:
Matthew Dharm wrote:
There's more to analyize, but on first inspection that babble looks bad.
We submitted a single URB with a 128 byte buffer. We received 64 bytes. I
don't think a babble is actually possible here
On Sun, Sep 21, 2003 at 06:41:43PM -0700, Linus Torvalds wrote:
Ideas? Anything that stands out except for the babble thing?
So, here is what I see in the log...
hub 2-0:0: new USB device on port 1, assigned address 2
usb-storage: USB Mass Storage device detected
usb-storage: act_altsetting
On Sun, 21 Sep 2003, Matthew Dharm wrote:
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command READ_CAPACITY (10 bytes)
SCSI device sda: 2000880 512-byte hdwr sectors (1024 MB)
Normal READ_CAPACITY -- is that size correct?
Yes. I've got a camera
On Sun, 21 Sep 2003, Linus Torvalds wrote:
Odd... why do we ask for the first 8 bytes of page 8? The header alone is
8 bytes anyway, the response looks good.
It tries to read the cache type. It tries to read the header first, in
order to figure out how much of page 8 it can read.
--
Subject: FAQ?
--text follows this line--
Is there a FAQ for this list?
I've got a Compact Flash reader that works well on my laptop, with an
ohci controller, but freezes up on my new (used) computer with a uhci
computer.
What information can I extract from my system that would be of use
14 matches
Mail list logo
