On Saturday 07 December 2002 22:07, Pete Zaitcev wrote:
> > Please try the attached patch, and also send me the output
> > of your dmesg, taken after the test. There is a special printout
> > there to diagnose the problem.
Hello Pete,
With your patch, my problematic device connectes succesfully.
Hi David,
Then do you have any suggestion for me to fix the problem.
Should I use more update kernel (2.4.21 or 2.5.X) or apply other patch to my
current kernel?
Or could you show me some direction and I will try my best to try to fix the
problem.
Best Regards,
Jason Chan
- Original Mes
Hi,
disconnect and usbdev_open do locking with BKL.
usbdev_open allocates memory. That may drop BKL.
Thus memory allocation must be done before the
device is checked for validity. Change set included.
Note: my kernel currently refuses to compile
due to pci_quirks, thus it's untested.
Comments ?
> disconnect and usbdev_open do locking with BKL.
> usbdev_open allocates memory. That may drop BKL.
> Thus memory allocation must be done before the
> device is checked for validity. Change set included.
> Note: my kernel currently refuses to compile
> due to pci_quirks, thus it's untested.
> Comm
Am Sonntag, 8. Dezember 2002 07:18 schrieb Duncan Sands:
> > disconnect and usbdev_open do locking with BKL.
> > usbdev_open allocates memory. That may drop BKL.
> > Thus memory allocation must be done before the
> > device is checked for validity. Change set included.
> > Note: my kernel currently
Jason Chan wrote:
Hi David,
Then do you have any suggestion for me to fix the problem.
Should I use more update kernel (2.4.21 or 2.5.X) or apply other patch to my
current kernel?
Or could you show me some direction and I will try my best to try to fix the
problem.
No suggestions, sorry. I
This patch makes interrupt URBs one-shot for CBI transfers. This is good
for code reduction, simplification, and aborting.
transport.c | 163 +---
transport.h |5 +
usb.c | 63 +--
usb.h |8 --
4 f
This patch makes ss->ep_int just like ep_in and ep_out for improved code
symmetry and readability. It may (on some architectures) also shrink the
size of the per-device data structure.
transport.c |4 ++--
usb.c | 15 +--
usb.h |3 ++-
3 files changed, 13 insert
This patch primarily:
- Gets rid of usb_interface->{driver,private_data} since those
roles are handled now in the driver model core.
- Updates the driver model core to make the rest of that possible.
That means adding new methods so driver binding can be done in
the open, not just as a side
Hello,
I don't know if this is a bug, but it seems so...
The two fields "bcdUSB" and "bcdDevice" in the struct
"usb_device_descriptor" are, as the name indicates, BCD - Binary-Coded
Decimal. According to the "Universal Serial Bus Specification - Revision
1.1" pages 197 and 198:
BCD is nybble-oriented, not byte oriented. Look at the example you quoted:
2.10 is 0x0210, not 0x020a (as your suggestion would have it).
Matt
On Mon, Dec 09, 2002 at 05:26:55AM +, Rui Saraiva wrote:
> Hello,
>
> I don't know if this is a bug, but it seems so...
>
> The two fields "bcdUSB"
Tvrtko A. Ursulin wrote:
I got the following oops message (attached)
Can you reproduce it with 2.4.19 ? Are you using preemptible kernel patch?
I ask you this because I also have trouble with 2.4.20 and preemptible kernel
patch.
No I don't use the preemptible kernel patch.
And umm..
On Sun, 8 Dec 2002, Matthew Dharm wrote:
> BCD is nybble-oriented, not byte oriented. Look at the example you quoted:
> 2.10 is 0x0210, not 0x020a (as your suggestion would have it).
As I quoted, the format is OxJJMN, JJ is the major, M the minor and N the
sub version. In that example 0x0210, JJ
13 matches
Mail list logo
