I'm using a 2 port USB RS232 dongle to connect to a serial-IR cradle for
a bar code reader). Detecting the baudrate of the serial-IR involves
keeping DTR low while changing baudrate.
This works using normal 16550A serial ports as well as the FTDI driver
version 1.4.0 (Linux 2.6.8) but stopped
Hi,
As it turned out, libusb is not thread safe and I cannot simultaneously
BULK read and write to my USB2.0/Full Speed device.
I've looked at devio.c (the code which is responsible for direct IOCTL
calls of usbdevfs), but couldnt really conclude anything about it..
maybe using the USBDEVFS_SUBMI
Hi,
this patch fixes an "Invalid argument" error returned by a write to an
endpoint-file after reopening it in the
gadgetfs module in the kernel 2.6.12.
This was testet only with dummy_hcd module!
diff -u -r linux-2.6.12.orig/drivers/usb/gadget/inode.c
linux-2.6.12/drivers/usb/gadget/inode.c
2005/9/6, David Brownell <[EMAIL PROTECTED]>:
> Again, _transfers_ don't reserve bandwidth, endpoints do.
>
I think I misunderstood this point
> And when the endpoint's transfer queue is empty, it surrenders
> its bandwidth reservation.
>
Dave, I just want to be sure to well understand thi
> > Again, _transfers_ don't reserve bandwidth, endpoints do.
>
> I think I misunderstood this point
If you looked much at 2.4 code, that may be why. :)
> When you say NAK is not an error case, this is true except for setup
> stage. Functions cannot issue a NAK packet in response to a set
Hi,
I'm getting an oops on my MIPS system with a NEC EHCI USB controller and
Linux 2.4.30.
I have traced this to a NULL pointer dereference in start_unlink_async():
prev = ehci->async;
while (prev->qh_next.qh != qh) {
prev = prev->qh_next.qh;
2005/9/7, David Brownell <[EMAIL PROTECTED]>:
> > When you say NAK is not an error case, this is true except for setup
> > stage. Functions cannot issue a NAK packet in response to a setup
> > packet. In that case, it is an _error_, is it correct ?
>
> If they can't issue it, why are you worried a
Hi,
this patch fixes an "Invalid argument" error returned by a write to an
endpoint-file after reopening it in the
gadgetfs module in the kernel 2.6.12.
This was testet only with dummy_hcd module!
Pavol Kurina
Signed-off-by: Pavol Kurina <[EMAIL PROTECTED]>
--
diff -u -r -p linux-2
> Just to be sure, you mean if "URB1" is done at frameX then "URB2" must
> be done at frameX + URB2->intervall ? Can you point out the section of
> USB spec that explains this, please ?
Forget about URB2->interval; it's an error in the device driver if
that's not the same as URB1->interval (or URB
> Date: Wed, 07 Sep 2005 18:25:45 +0200
> From: Pavol Kurina <[EMAIL PROTECTED]>
> To: linux-usb-devel@lists.sourceforge.net, [EMAIL PROTECTED]
> Subject: [PATCH] gadgetfs: fixes an error on writing to endpoint file
>
> Hi,
>
> this patch fixes an "Invalid argument" error returned by a write to a
2005/9/7, David Brownell <[EMAIL PROTECTED]>:
> > Just to be sure, you mean if "URB1" is done at frameX then "URB2" must
> > be done at frameX + URB2->intervall ? Can you point out the section of
> > USB spec that explains this, please ?
>
> Forget about URB2->interval; it's an error in the device
On Wed, 7 Sep 2005, Istvan De wrote:
> Hi,
>
> As it turned out, libusb is not thread safe and I cannot simultaneously
> BULK read and write to my USB2.0/Full Speed device.
>
> I've looked at devio.c (the code which is responsible for direct IOCTL
> calls of usbdevfs), but couldnt really conclud
2005/9/7, David Brownell <[EMAIL PROTECTED]>:
> > BTW, in "balance" function, why does index "i" start to 0 and not to
> > current frame number ?
>
> Why not? All that it guarantees is periodicity. Linux-USB hasn't
> yet made any guarantees about the analogue of clock phase; once a
> periodic tr
Hi All,
I've noticed a potential problem with the USB serial driver layer and/or
the ipaq driver. I suspect it's not specific to the ipaq driver...
Anyways, If I have my USB device hooked up and talking to a userspace
program (minicom or whatever) and I turn off or unplug the device, the
userspa
Sep 7 22:47:10 proliant kernel: ohci_hcd :00:0f.1: wakeup
Sep 7 22:47:11 proliant kernel: usb 2-1: new full speed USB device
using address 2
Sep 7 22:47:11 proliant kernel: usb-storage: This device
(05ab,0060,1106 S 06 P 50) has unneeded SubClass and Protocol entries in
unusual_devs.h
Se
On Wed, 07 Sep 2005 15:28:02 -0500, Shane Anderson <[EMAIL PROTECTED]> wrote:
> I've done a bit of digging into the
> kernel source (2.6.8 on debian) and I think that the usb disconnect
> needs to let the tty layer know that something happened since (I think)
No surprise here. Remember the old jo
Hi all
i have developed a USB host and gadget driver for my USB hardware.
Now i want to test the drivers.
Can anyone please suggest
---
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA
17 matches
Mail list logo
