Gaëtan Marti wrote:
The current ftdi_sio module is for the FT8U100AX, 8U232AM, as well as
for the USB to parallel converter (245).
Our application is using the FT232BM and I'm not sure the FTDI_SIO
module is designed for it!
The module works fine with the FT232BM chip and I talk from personal
David Brownell wrote:
For what it's worth I'm including my UDC driver as a patch against
your 2.4 gadget tree. I've only tried it with g_zero and
g_file_storage so those are the only changed gadgets. This patch
doesn't include any changes for stall free mass storage operation.
I'm sure ther
Daniel C. Casimiro wrote:
Hi,
I have a set of Altec Lansing ADA305 Speakers that can use USB to
control volume, base, treble, etc. Now, I noticed that the USB Audio
Class specification is capable of handling these parameters. However,
the usb audio module does not claim these speakers. I tri
G. Del Merritt wrote:
I have a simple hotplug script that works under 2.4.20.9; all it does is
chmod 0666 "${DEVICE}"
The device name passed for either kernel is the "old style" /proc/bus/usb/blah
name. When I do an "ls -l" on that file, I see the correct permissions, but
the /sys version of i
Follow-Up to my problem:
> You said there was no device connected -- so the root hub
> had no business trying to assign any addresses. It must
> have lied to the hub driver about port status. If there's
> no device there, of course any attempt to talk to it will
> time out ...
I solved my probl
On Wed, 29 Oct 2003, David Brownell wrote:
> I think I'll have to merge this in dribs'n'drabs. I can do the
> build/config support right away; a Config.in entry would be good too.
> Also that first file_storage.c change (assuming Alan doesn't object).
I don't mind. But first remove the #define
David Mosberger wrote:
On x86, there is no OOps, it just freezes. On ia64, I get a nice MCA
and from that we can infer that a USB host controller read from
address 0xf000 caused the problem but since this is asynchronous
to the kernel's code path, the instruction pointer etc. in the MCA
state
Perhaps I'm limited by the speed of my CPU, I'm only running at about
66MHz, which is half of the maximum speed of the device.
Yes, I'd expect that would hurt PIO throughput.
The main thing that makes me wonder "bug??" is the "ep3" handling,
which is incomplete. That's the 8-byte Interrupt-IN
On Wed, 29 Oct 2003, Greg KH wrote:
> On Mon, Oct 27, 2003 at 11:10:22AM -0500, Alan Stern wrote:
> > This patch makes config.c more liberal about the sorts of interface
> > numbering it will accept when reading interface descriptors. The current
> > code only allows interfaces numbered 0..(bNu
Since there probably aren't any devices
that list the descriptors out-of-order, the sort may not be needed.
Actually there are devices that list the descriptors in
non-numeric order. At least one CDC-Ether cable modem.
- Dave
---
This SF.n
David Brownell wrote:
I've just implemented ep3 and have tried to test it using g_zero
(substituting "ep3in-bulk" for "ep2in-bulk" as you suggest) but it
has caused the host usbtest driver to crash when I plugged it in:
If it's that early, it suggests there's something wrong with
the descripto
> On Thu, 30 Oct 2003 07:11:42 -0800, David Brownell <[EMAIL PROTECTED]> said:
David> David Mosberger wrote:
>> On x86, there is no OOps, it just freezes. On ia64, I get a nice MCA
>> and from that we can infer that a USB host controller read from
>> address 0xf000 caused the pro
http://www.nealsak.com"; target="_blank">http://www.nealsak.com/catalog/images/logoalsak.gif";
border="0">
Dünya
Onu Konuşuyor!
Büyük
Fırsatlar ve Türkiye'nin Yeni Alışveriş Sitesinle Tanışmak İçin http://www.nealsak.com"; target="_blank">Tıklayınız!
http://www.nealsak.com";
targe
--- Begin Message ---
En/na David Brownell ha escrit:
Josep Comas wrote:
Hello,
I am a developer of some ADSL USB modems
(https://sourceforge.net/users/jcomas/). I have some USB timeout
problems using kernel 2.4.22 and kernel 2.6.0test8. I have a program
in user space to send firmware to mod
After spending a bit more time on this, it looks to me like the
keyboard is crashing the system very early on. I added some
instrumentation printks and am seeing this:
# insmod hid.ko
drivers/usb/core/usb.c: registered new driver hiddev
calling usb_hid_configure()
calling hid_init_reports()
hid_s
15 matches
Mail list logo
