Hi,
here's a quirklist entry reported by Stephen Murphy.
Regards
Oliver
Signed-off-by: Oliver Neukum <[EMAIL PROTECTED]>
--- a/drivers/usb/class/cdc-acm.c 2007-02-06 14:14:48.0 +0100
+++ b/drivers/usb/class/cdc-acm.c 2007-02-12 08:45:03.0
Hi,
this is Joris' fixes reshuffelled and features renamed as David requested.
- acm_set_control is not mandatory, honour that
- throtteling is reset upon open
- throtteling is read consistently when processing input data
Regards
Oliver
Signed-off-by: Joris van Rantwijk
On Sun, Feb 11, 2007 at 10:47:27AM -0800, Greg KH wrote:
> It's in my queue and is on track to get in before 2.6.21-rc1 is out.
It breaks the build for everyone, please fast-forward the merging of
this.
Jeff
-
Usi
Followup to my last email. For example. Our IPanel that we just
blacklisted so that we can use our own driver is detected and loaded as
a mouse device by the HID driver. Why this is detected and parsed
properly and standard digitizers are not, I'm not sure. The issue I
think will be the same as
On Sun, 11 Feb 2007 17:17:35 -0500 (EST), Alan Stern <[EMAIL PROTECTED]> wrote:
> > @@ -935,7 +935,7 @@ struct usb_iso_packet_descriptor {
> > unsigned int offset;
> > unsigned int length;/* expected length */
> > unsigned int actual_length;
> > - unsigned int status;
> >
On Sun, 11 Feb 2007, Pete Zaitcev wrote:
> The status in usb_iso_packet_descriptor should be signed, for the benefit
> of someone who casts to a long or makes other benign misstep (the principle
> of least surprise).
>
> Signed-off-by: Pete Zaitcev <[EMAIL PROTECTED]>
>
> --- a/include/linux/usb
The status in usb_iso_packet_descriptor should be signed, for the benefit
of someone who casts to a long or makes other benign misstep (the principle
of least surprise).
Signed-off-by: Pete Zaitcev <[EMAIL PROTECTED]>
--- a/include/linux/usb.h
+++ b/include/linux/usb.h
@@ -935,7 +935,7 @@ struct
On Sun, 11 Feb 2007 11:18:11 +0300, Alexey Dobriyan <[EMAIL PROTECTED]> wrote:
> mon_bin_exit() and mon_text_exit() are called from __init code, so don't mark
> them as __exit.
> -void __exit mon_text_exit(void)
> +void mon_text_exit(void)
Got it, thanks.
-- Pete
--
On 2/11/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Sun, 11 Feb 2007, Guenther Sohler wrote:
>
> > Dear Users,
> >
> > On ebay I got a usb remote control. This is a ir receiver having a usb plug
> > and an ir remote control sender.
Most drivers for USB IR remote controls are out of tree. They
On Sun, 11 Feb 2007, Guenther Sohler wrote:
> Dear Users,
>
> On ebay I got a usb remote control. This is a ir receiver having a usb plug
> and an ir remote control sender.
>
> It is a Cypress Semiconductor eDio USB Multi Remote Controller
> from Formosa Industrial Computing, Inc.
> lsusb show
On Sun, 11 Feb 2007, Tilman Schmidt wrote:
> Prompted by the current discussion on LKML, I am considering adding
> proper suspend/resume support to the USB drivers I maintain. I have
> read Documentation/power/devices.txt but much of it just refers me
> to bus specific mechanisms.
>
> From what I
Dear Users,
On ebay I got a usb remote control. This is a ir receiver having a usb plug and
an ir remote control sender.
It is a Cypress Semiconductor eDio USB Multi Remote Controller
from Formosa Industrial Computing, Inc.
lsusb shows
Bus 003 Device 023: ID 147a:e006 Formosa Industrial Comput
On Sun, Feb 11, 2007 at 07:40:15PM +0100, Tilman Schmidt wrote:
> On Thu, 08 Feb 2007 14:02:31 +0100 I wrote:
> > Subject: Re: [linux-usb-devel] [PATCH 41/70] usbcore: remove unused
> > bandwith-related code
> >
> > This breaks compilation of drivers/isdn/gigaset/bas-gigaset.c.
> > If you pass on
On Thu, 08 Feb 2007 14:02:31 +0100 I wrote:
> Subject: Re: [linux-usb-devel] [PATCH 41/70] usbcore: remove unused
> bandwith-related code
>
> This breaks compilation of drivers/isdn/gigaset/bas-gigaset.c.
> If you pass on this patch, please pass on Andrew's
>
> fix-gregkh-usb-usbcore-remove-unus
Prompted by the current discussion on LKML, I am considering adding
proper suspend/resume support to the USB drivers I maintain. I have
read Documentation/power/devices.txt but much of it just refers me
to bus specific mechanisms.
From what I found on linux-usb-devel so far, if a USB driver does
n
> +/* devices supported by this driver */
> +static struct usb_device_id device_table[] = {
> + {USB_DEVICE(-1, -1)}, /* add your custom entry here ... */
> + {USB_DEVICE(0x08ca, 0x0109)},
> + {USB_DEVICE(0x041e, 0x4024)},
This ...
> +/* devices supported by this driver */
>
mon_bin_exit() and mon_text_exit() are called from __init code, so don't mark
them as __exit.
Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
---
drivers/usb/mon/mon_bin.c |2 +-
drivers/usb/mon/mon_text.c |2 +-
drivers/usb/mon/usb_mon.h |4 ++--
3 files changed, 4 insertions(+
17 matches
Mail list logo
