[linux-usb-devel] hao

2006-09-21 Thread df
现“AR纳米金属抗摩剂”面向全国部分地区诚征独家代理!有意向的朋友请联络AR中国总部负责人:朱现立 经理(13006689272 ) 深圳市新大华物资贸易有限公司是美国美商复润科技公司(AMYRICAN RECOVER LUBE TECHNOLOGY  CO。,LTD)中国区总代理。AR纳米金属抗摩剂不是普通的油品添加剂,而是真正的金属调理剂。其成分是对人体完全无害的单分子碳氢化合物,完全没有副作用,该产品安全、  无毒 、无害是目前世界上最尖端的高科技抗摩产品。获国际知名权威机构鉴定与支持。AR纳米金属抗摩剂应用广泛,适用与运输工具 生产设备  机电设备等需要润滑抗摩之物体表面。

Re: [linux-usb-devel] at91_ohci, strange problem

2006-09-21 Thread Aras Vaichas
David Brownell wrote: > What I'd need to see would be the output of the "ohci_dump()" emitted > after the OHCI_INTR_UE messages you showed. It should be in the syslog > data; if the kernel wedged so you couldn't access that, then a very handy > debug trick is "echo 8 > /proc/sysrq-trigger" to forc

Re: [linux-usb-devel] 2.6.18-rc6-mm2 (-mm1): ohci_hcd does not recognize new devices

2006-09-21 Thread Rafael J. Wysocki
On Thursday, 21 September 2006 16:56, Alan Stern wrote: > [Trimmed down the CC list] > > On Mon, 18 Sep 2006, Rafael J. Wysocki wrote: > > > On Monday, 18 September 2006 17:07, Alan Stern wrote: > > > On Mon, 18 Sep 2006, Rafael J. Wysocki wrote: > > > > > > > > Actually, the problem is ohci_hcd

Re: [linux-usb-devel] broken modules.alias entries for some USB devices

2006-09-21 Thread iSteve
On Thu, 21 Sep 2006 22:30:35 +0400 Sergey Vlasov <[EMAIL PROTECTED]> wrote: > The problem is that the bcdDevice field is supposed to be BCD - i.e., > its hex representation should contain only decimal digits 0..9. > Therefore a proper USB device cannot have bcdDevice == 0x030a. > Apparently some ib

[linux-usb-devel] [PATCH 2.6.18] xpad: dance pad support

2006-09-21 Thread Adam Buchbinder
From: Dominic Cerquetti <[EMAIL PROTECTED]> Adds support for dance pads to the xpad driver. Dance pads require the d-pad to be mapped to four buttons instead of two axes, so that combinations of up/down and left/right can be hit simultaneously. Known dance pads are detected, and there is a module

[linux-usb-devel] broken modules.alias entries for some USB devices

2006-09-21 Thread Sergey Vlasov
On Thu, 21 Sep 2006 16:54:24 +0200 iSteve wrote: > I've got one more question, this time regarding modules.usbmap. > > -modules.usbmap: > ibmcam 0x000f 0x0545 0x8080 0x0002 0x0002 0x00 0x00 0x00 0x00 0x00 0x00 0x0 > ibmcam 0x000f 0x0545 0x8080 0x030a 0x030a 0x00 0x00 0x00 0x00 0x00 0x00 0x0 > ibm

Re: [linux-usb-devel] [PATCH 2.6.17.11] xpad: dance pad support

2006-09-21 Thread Greg KH
On Thu, Sep 21, 2006 at 11:19:18AM -0400, Adam Buchbinder wrote: > From: Dominic Cerquetti <[EMAIL PROTECTED]> > > Adds support for dance pads to the xpad driver. Dance pads require the > d-pad to be mapped to four buttons instead of two axes, so that > combinations of up/down and left/right can b

Re: [linux-usb-devel] [PATCH 2.6.17.11] xpad: dance pad support

2006-09-21 Thread Dmitry Torokhov
On 9/21/06, Adam Buchbinder <[EMAIL PROTECTED]> wrote: > + > +static int dpad_to_buttons = 0; > +module_param(dpad_to_buttons, bool, S_IRUGO); > +MODULE_PARM_DESC(dpad_to_buttons, "Map D-PAD to buttons rather than axes for > unknown pads"); There is no need to initialize dpad_to_buttons to 0, it

[linux-usb-devel] [PATCH 2.6.17.11] xpad: dance pad support

2006-09-21 Thread Adam Buchbinder
From: Dominic Cerquetti <[EMAIL PROTECTED]> Adds support for dance pads to the xpad driver. Dance pads require the d-pad to be mapped to four buttons instead of two axes, so that combinations of up/down and left/right can be hit simultaneously. Known dance pads are detected, and there is a module

Re: [linux-usb-devel] 2.6.18-rc6-mm2 (-mm1): ohci_hcd does not recognize new devices

2006-09-21 Thread Alan Stern
[Trimmed down the CC list] On Mon, 18 Sep 2006, Rafael J. Wysocki wrote: > On Monday, 18 September 2006 17:07, Alan Stern wrote: > > On Mon, 18 Sep 2006, Rafael J. Wysocki wrote: > > > > > > Actually, the problem is ohci_hcd doesn't seem to recognize devices > > > > plugged > > > > into the USB

Re: [linux-usb-devel] OHCI bus suspend

2006-09-21 Thread Alan Stern
On Wed, 20 Sep 2006, David Brownell wrote: > On Wednesday 20 September 2006 10:09 am, Alan Stern wrote: > > Dave: > > > > I want to modify the bus_suspend and bus_resume routines in ohci-hub.c. > > The idea is to have versions that can operate entirely in interrupt > > context. > > > > Normal

[linux-usb-devel] [PATCH] asix - Add alternate device IDs for Dlink DUB-E100 Rev B1

2006-09-21 Thread David Hollis
It seems that the Dlink DUB-E100 Rev B1 has a few different device IDs that it may use. -- David Hollis <[EMAIL PROTECTED]> Add alternate device IDs for Dlink DUB-E100 Rev B1 Signed-off-by: David Hollis <[EMAIL PROTECTED]> diff --git a/drivers/usb/net/asix.c b/drivers/usb/net/asix.c index 470c

Re: [linux-usb-devel] at91_ohci, strange problem

2006-09-21 Thread David Brownell
On Wednesday 20 September 2006 7:18 pm, Aras Vaichas wrote: > David Brownell wrote: > David Brownell wrote: > > On Sunday 17 September 2006 9:59 pm, Aras Vaichas wrote: > >> I'm using an at91rm9200 with Linux 2.6.16. Under some unusual > >> circumstances, I > >> can create a failure. > > > > Can y

Re: [linux-usb-devel] Large control write transfers / zero-length-packet at end

2006-09-21 Thread David Brownell
> > > This really solves my problem. One fundamental problem (at least given > > > the SAM7 register set) remains: I have no indication to decide which of > > > the data OUT packets was the last, and when the device should return the > > > status stage IN packet. > > > > The at91_udc driver shou