Hello,
I am having a problem in probing a device in my
driver. The device parameters(configurations,
interfaces, endpoints, etc) show up during kernel
bootup and are fine but when I print out the
dev->descriptor fields in my module's probe function
the values seem all messed up i.e for exampl
On Sun, Dec 23, 2001 at 12:03:10AM +0100, Vojtech Pavlik wrote:
>
> One more for usbnet:
Thanks. Added to my 2.4 and 2.5 trees.
greg k-h
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/l
> > Feel like providing a patch?
>
> Well, I've never "patched" before ... is there some docs on the process?
Start with: /usr/src/linux/Documentation/SubmittingPatches ...
For a single file,
diff -u old.c new.c > my.patch
and you can test it on a new kernel by
patch -p0 < my.patch
On Sun, Dec 23, 2001 at 09:12:49PM -0500, [EMAIL PROTECTED] wrote:
>
> Well, I've never "patched" before ... is there some docs on the process?
See Documentation/SubmittingPatches in the kernel tree. It should
answer most of the questions on the process.
thanks,
greg k-h
> In this case I think correcting the documentation is the answer.
> Existing callers should work with the existing code ... though it
> may be worth sanity checking it.
>
> Since that error has been carried up the stack to many of the
> convenience wrappers around usb_control_msg(), they'll need
On Mon, Dec 24, 2001 at 02:22:08AM +0100, jeanseb wrote:
> this the 0.3 release of the linux driver for ECI HIFOUCS ADSL modem.
> It is mostly stable and work full speed now.
> This modem is based on glogspan titanium and cypress ez2131 chips so any
> modem based on the same couple of chpset may
> Now to try to get rid of those *_t and p* typedefs in usb.h...
Yes please. Luckily most driver authors don't use them ... :)
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-d
More detail on the lockup problem with the HP8200e CD writer. The
writer locks up about every second or third time I write a CD. Short
CDs are less likely to see the problem than long ones. Under windows,
the unit works fine.
I've tried unplugging the USB cable between runs, and unloading
On Sun, Dec 23, 2001 at 02:24:01AM -0500, Pete Zaitcev wrote:
>
> > Here's a patch against 2.4.17 that adds documentation for the FILL_*_URB
> > macros, and adds the usb_fill_*_urb() inline functions which are in the
> > 2.5 tree.
>
> Why are they inline? We do have macros, so it's not for speed
All:
I am looking for doucmentation for Linux usbdevfs, like just a general
description about how it works, and specifically
struct usbdevfs_bulktransfer
and how
ioctl()
interfaces with it. Thanks.
Neil Hodge
___
[EMAIL PROTECTED]
To unsubscrib
this the 0.3 release of the linux driver for ECI HIFOUCS ADSL modem.
It is mostly stable and work full speed now.
This modem is based on glogspan titanium and cypress ez2131 chips so any
modem based on the same couple of chpset may work. please report workin
/ not working device in order to main
In this case I think correcting the documentation is the answer.
Existing callers should work with the existing code ... though it
may be worth sanity checking it.
Since that error has been carried up the stack to many of the
convenience wrappers around usb_control_msg(), they'll need
to change t
Hi,
I noticed that the USB scanner module is still using the Linux 2.2
module locking scheme. Here is a patch to make it use the v2.4 scheme.
Cheers,
Chris
--- linux-2.4.17/drivers/usb/scanner.c.orig Sat Dec 22 00:10:06 2001
+++ linux-2.4.17/drivers/usb/scanner.c Sat Dec 22 00:13:14 2001
@
> From: Greg KH <[EMAIL PROTECTED]>
> To: Marcelo Tosatti <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Date: Fri, 21 Dec 2001 14:22:55 -0800
> Here's a patch against 2.4.17 that adds documentation for the FILL_*_URB
> macros, and adds the usb_fill_*_urb() inline functions which are in the
> 2.5
On Sat, Dec 22, 2001 at 03:00:03AM +, Chris Rankin wrote:
> Hi,
>
> I noticed that the USB scanner module is still using the Linux 2.2
> module locking scheme. Here is a patch to make it use the v2.4 scheme.
Thanks, but can you send this to the current scanner.c author, David
Nelson ([EMAIL
In usb/usb.c, usb_control_msg returns the value returned from
usb_internal_control_msg. If the send was successful, this is the length
of the send, otherwise, its the negative error. However, the comment for
usb_control_msg says "If successful, it returns 0, otherwise, a negative
error number". So
16 matches
Mail list logo
