Re: [linux-usb-devel] [PATCH] Add Digitech USB-Storage to unusual_devs.h

2006-11-14 Thread jkroon
On Tue, Nov 14, 2006 at 09:39:16PM -0800, Phil Dibowitz wrote: > Jaco Kroon wrote: > >The mass storage device from Digitech designed for Flash Cards, as found > >on (for example) the GNX4 device has issues with residue, similar to the > >bug report at http://kerneltrap.org/node/6297. This patch ad

Re: [linux-usb-devel] [PATCH] Add Digitech USB-Storage to unusual_devs.h

2006-11-14 Thread Phil Dibowitz
Jaco Kroon wrote: The mass storage device from Digitech designed for Flash Cards, as found on (for example) the GNX4 device has issues with residue, similar to the bug report at http://kerneltrap.org/node/6297. This patch adds the faulty storage device to unusual_devs.h, this not only reduces th

[linux-usb-devel] 邀请代理美国AVO 便携式LCR测试仪B131

2006-11-14 Thread 专业销售仪器仪表
This is a multi-part message in MIME format- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief survey

Re: [linux-usb-devel] How to hack the EHCI driver to send no more than a single transaction per frame

2006-11-14 Thread David Brownell
On Monday 13 November 2006 1:08 pm, Laurent Pinchart wrote: > Hi everybody, > > I'm investigating a hardware issue with a high-speed USB webcam. I would like > to hack the EHCI driver to send no more than a single transaction per frame. > > If I understand the big picture clearly, request are sp

Re: [linux-usb-devel] 2.6.19-rc5 regression: can't disable OHCI wakeup via sysfs

2006-11-14 Thread David Brownell
On Tuesday 14 November 2006 1:42 pm, Alan Stern wrote: > On Tue, 14 Nov 2006, David Brownell wrote: > > > On Monday 13 November 2006 9:15 am, Alan Stern wrote: > > > On Mon, 13 Nov 2006, David Brownell wrote: > > > > > > > It's a *driver model* API, which is also accessible from sysfs ... to > >

[linux-usb-devel] [PATCH] Add Digitech USB-Storage to unusual_devs.h

2006-11-14 Thread Jaco Kroon
The mass storage device from Digitech designed for Flash Cards, as found on (for example) the GNX4 device has issues with residue, similar to the bug report at http://kerneltrap.org/node/6297. This patch adds the faulty storage device to unusual_devs.h, this not only reduces the noise in dmesg but

Re: [linux-usb-devel] 2.6.19-rc5 regression: can't disable OHCI wakeup via sysfs

2006-11-14 Thread Alan Stern
On Tue, 14 Nov 2006, David Brownell wrote: > On Monday 13 November 2006 9:15 am, Alan Stern wrote: > > On Mon, 13 Nov 2006, David Brownell wrote: > > > > > It's a *driver model* API, which is also accessible from sysfs ... to > > > support > > > per-device policies, for example the (a) workaroun

Re: [linux-usb-devel] at91_udc: endless loop after rmmod g_file_storage and other problems

2006-11-14 Thread David Brownell
On Tuesday 14 November 2006 12:43 am, Viehweger Thomas wrote: > > Is this with 2.6.19-rc5, or some older kernel? > > The kernel itself is 2.6.12.1, at91_udc and file_storage (as example) are > patched from 2.6.18. > I have some trouble to port the BSP to a newer kernel. > But what can cause the de

[linux-usb-devel] [PATCH] OHCI: disallow autostop when wakeup is not available

2006-11-14 Thread Alan Stern
This patch (as822) prevents the OHCI autostop mechanism from kicking in if the root hub is not able or not allowed to issue wakeup requests. Signed-off-by: Alan Stern <[EMAIL PROTECTED]> --- Greg: This patch should go into 2.6.19-rc ASAP. It does solve a real problem. The larger-scale change

Re: [linux-usb-devel] 2.6.19-rc5 regression: can't disable OHCI wakeup via sysfs

2006-11-14 Thread David Brownell
On Monday 13 November 2006 9:15 am, Alan Stern wrote: > On Mon, 13 Nov 2006, David Brownell wrote: > > > It's a *driver model* API, which is also accessible from sysfs ... to > > support > > per-device policies, for example the (a) workaround. The mechanism exists > > even on kernels that don't

Re: [linux-usb-devel] [Bulk] Re: 2.6.19-rc5 regression: can't disable OHCI wakeup via sysfs

2006-11-14 Thread David Brownell
On Tuesday 14 November 2006 12:48 pm, Andrey Borzenkov wrote: > On Monday 13 November 2006 22:58, Alan Stern wrote: > > Andrey: > > > > Try this patch for 2.6.19-rc5. Although it doesn't make all the changes > > Dave and I have discussed, it ought to fix your problem. > > > > It did. Thank you T

Re: [linux-usb-devel] 2.6.19-rc5 regression: can't disable OHCI wakeup via sysfs

2006-11-14 Thread Andrey Borzenkov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 13 November 2006 22:58, Alan Stern wrote: > Andrey: > > Try this patch for 2.6.19-rc5. Although it doesn't make all the changes > Dave and I have discussed, it ought to fix your problem. > It did. Thank you - -andrey > Alan Stern > > > In

Re: [linux-usb-devel] [BUG] timeout on USB close (reproductible)

2006-11-14 Thread Alan Stern
On Tue, 14 Nov 2006, Romain Liévin wrote: > Hi Alan, > > > It is a bug in the Titanium firmware. In the logs for both handhelds > you > > can see where the kernel sends a Set-Interface request after your driver > releases the interface. (The kernel does this automatically so that the > interfac

Re: [linux-usb-devel] [PATCH] resume_device symbol conflict (v2)

2006-11-14 Thread Alan Stern
On Tue, 14 Nov 2006, Stephen Hemminger wrote: > Several functions in USB core overlap with global functions. > The linker appears to do the right thing, but it is bad practice and makes > debugging harder. Acked-by: Alan Stern <[EMAIL PROTECTED]> ---

Re: [linux-usb-devel] [BUG] timeout on USB close (reproductible)

2006-11-14 Thread Romain Liévin
Hi Alan, > It is a bug in the Titanium firmware. In the logs for both handhelds you > can see where the kernel sends a Set-Interface request after your driver releases the interface. (The kernel does this automatically so that the interface will be back in its original condition when the next dr

[linux-usb-devel] [PATCH] resume_device symbol conflict (v2)

2006-11-14 Thread Stephen Hemminger
Several functions in USB core overlap with global functions. The linker appears to do the right thing, but it is bad practice and makes debugging harder. --- drivers/usb/core/driver.c | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) --- orig/drivers/usb/core/drive

Re: [linux-usb-devel] [BUG] timeout on USB close (reproductible)

2006-11-14 Thread Romain Liévin
Hi, >> Problem is related to TI's hand-helds (TI84+ & Titanium >> graphing calculators). It only appears with Titanium under Linux >> although TI84+ and Titanium have (almost) the same USB descriptors. No >> troubles with my own Win32 WDM driver for both hand-helds. >> >> Problem appears both with

Re: [linux-usb-devel] [BUG] timeout on USB close (reproductible)

2006-11-14 Thread Alan Stern
On Tue, 14 Nov 2006, Romain Liévin wrote: > Hi, > > Problem is related to TI's hand-helds (TI84+ & Titanium > graphing calculators). It only appears with Titanium under Linux > although TI84+ and Titanium have (almost) the same USB descriptors. No > troubles with my own Win32 WDM driver for both

Re: [linux-usb-devel] [PATCH] resume_device symbol conflict

2006-11-14 Thread Alan Stern
On Mon, 13 Nov 2006, Stephen Hemminger wrote: > There are two definitions of resume_device. A global one is defined > in resume.c, and a local one is defined in USB core. The linker appears > to do the right thing, but it is bad practice and makes backtrace > decoding harder. If you're going to c

[linux-usb-devel] Majordomo results: Fw: Sexy

2006-11-14 Thread Majordomo
-- This is a multi-part message in MIME format. Command 'this' not recognized. --=_NextPart_3.94946396350861E-02 Command '--=_nextpart_3.94946396350861e-02' not recognized. Content-Type: text/html; format=flowed Command 'content-type:' not recognized. >>

[linux-usb-devel] You could order it on-line and get immediately!

2006-11-14 Thread Cross
Hi! Thousands of men know what it feels like, though few will admit they have a problem. Safe, efficient and covering all aspects, Extra-Time will help you forget the premature nightmare. Is not again the phrase you hear too often in bed with your partner? Enter: http://berhoj.com/y/et/ You will

[linux-usb-devel] Majordomo results: Fwd: Photo

2006-11-14 Thread Majordomo
-- This is a multi-part message in MIME format. Command 'this' not recognized. --=_NextPart_3.52683901786804E-02 Command '--=_nextpart_3.52683901786804e-02' not recognized. Content-Type: text/html; format=flowed Command 'content-type:' not recognized. >>

[linux-usb-devel] Majordomo results: Fwd: Crazy illegal Sex!

2006-11-14 Thread Majordomo
-- This is a multi-part message in MIME format. Command 'this' not recognized. --=_NextPart_2.58994042873383E-02 Command '--=_nextpart_2.58994042873383e-02' not recognized. Content-Type: text/plain; format=flowed Command 'content-type:' not recognized. >

Re: [linux-usb-devel] PXA270 problem USB host port 3

2006-11-14 Thread David Cano García
Hi everyone, I have read that USB host port 3 is single-ended mode. My specific hardware have the transceiver bad configured. regards, David El lun, 13-11-2006 a las 09:30 -0800, David Brownell escribió: > On Monday 13 November 2006 2:33 am, David Cano García wrote: > > Hello everyone, > > I n

Re: [linux-usb-devel] at91_udc: endless loop after rmmod g_file_storage and other problems

2006-11-14 Thread Viehweger Thomas
> Is this with 2.6.19-rc5, or some older kernel? The kernel itself is 2.6.12.1, at91_udc and file_storage (as example) are patched from 2.6.18. I have some trouble to port the BSP to a newer kernel. But what can cause the described behviour? ---