[linux-usb-devel] BANNED FILENAME (MoreInfo.zip) IN MAIL FROM YOU

2004-06-03 Thread Sentex Support
BANNED FILENAME ALERT Our content checker found banned name: MoreInfo.zip in email presumably from you (<[EMAIL PROTECTED]>), to the following recipient: -> [EMAIL PROTECTED] Delivery of the email was stopped! The message has been blocked because it contains a component (as a MIME part or ne

Re: [linux-usb-devel] usb audio bug

2004-06-03 Thread Pete Zaitcev
On Thu, 03 Jun 2004 11:35:42 -0700 Dustin Hillard <[EMAIL PROTECTED]> wrote: > Jun 3 11:16:52 ballard kernel: usbaudio: warning: found 2 of 1 logical channels. > Jun 3 11:16:52 ballard kernel: usbaudio: no idea what's going on..., contact > [EMAIL PROTECTED] > Jun 3 11:16:52 ballard kernel:

Re: [linux-usb-devel] [patch] Patch to prevent overlapping access by usb-storage and usbfs

2004-06-03 Thread Olaf Hering
On Thu, Jun 03, Oliver Neukum wrote: > Am Donnerstag, 3. Juni 2004 18:39 schrieb Olaf Hering: > > This patch causes deadlocks if you unplug and replug an usb-storage > > device. > > Only on replug? yes. plug the usbstick in, reboot, everything works ok. unplug, still ok, replug, threads hang in

[linux-usb-devel] usb audio bug

2004-06-03 Thread Dustin Hillard
Hi - I've just finished compiling the 2.4.19 kernel with all the usb support to get my usb speakers working... which just worked - but I get an odd message in boot up so I thought I'd pass it on to you (because the message asks that...) At the bottom I get : warning: found 2 of 1 logical channe

[linux-usb-devel] Re: Suspend/resume questions

2004-06-03 Thread David Brownell
Alan Stern wrote: You could move the root hub vs. normal device distinction from __usb_suspend_device() down into hub_port_suspend(). Then root hubs would be suspended just like other devices, so they could be resumed the same way too. The hub to which the root hub is attached, and through a po

[linux-usb-devel] Re: can't locate HID device file

2004-06-03 Thread Charles Lepple
Damien McGivern wrote: Hi, I've just moved from a Mandrake 10 (2.6.3) to a Knoppix/Debian 2.6.6 install. I had C++ code that opened the device file (all of which were located in /dev/usb/hid) and sent and recieved commands to and from the device. But with the new install the the /dev/usb/hid direc

[linux-usb-devel] Re: 2.6-BK usb (printing) broken

2004-06-03 Thread Greg KH
On Sat, May 29, 2004 at 02:51:48PM -0400, Alan Stern wrote: > On Sat, 29 May 2004, Jens Axboe wrote: > > > > > Both 2.6.7-rc1 and BK current spit out a bunch of: > > > > > > > > drivers/usb/class/usblp.c: usblp1: nonzero read/write bulk status received: -2 > > > > drivers/usb/class/usblp.c: usblp

[linux-usb-devel] Re: [patch] Patch to prevent overlapping access by usb-storage and usbfs

2004-06-03 Thread Alan Stern
On Thu, 3 Jun 2004, Pete Zaitcev wrote: > It is definitely needed for 2.4 in Red Hat, however I tried to turn > it down for generic code even though it's not my area and Matt and Alan > didn't have a problem with it. The problem comes about because > Red Hat installer tries to optimize things and

Re: [linux-usb-devel] Linux 2.4.x mass storage devices

2004-06-03 Thread Alan Stern
On Thu, 3 Jun 2004, Pete Zaitcev wrote: > On 03 Jun 2004 13:05:01 -0700 > David Meggy <[EMAIL PROTECTED]> wrote: > > > When the 1st device is plugged in it will receive /dev/sda, and the > > second device will receive /dev/sdb. If I were to unplug the first > > device before plugging in the seco

[linux-usb-devel] Re: [patch] Patch to prevent overlapping access by usb-storage and usbfs

2004-06-03 Thread Matthew Dharm
On Thu, Jun 03, 2004 at 01:20:46PM -0700, Pete Zaitcev wrote: > On Thu, 3 Jun 2004 22:06:06 +0200 > Vojtech Pavlik <[EMAIL PROTECTED]> wrote: > > > The deadlocks might actually be my fault, as I re-used the serialize > > semaphore, while the original 2.4 patch used it's own. > > Et tu Brut :-) I

Re: [linux-usb-devel] Linux 2.4.x mass storage devices

2004-06-03 Thread Pete Zaitcev
On 03 Jun 2004 13:05:01 -0700 David Meggy <[EMAIL PROTECTED]> wrote: > When the 1st device is plugged in it will receive /dev/sda, and the > second device will receive /dev/sdb. If I were to unplug the first > device before plugging in the second device, the second device will > still get /dev/sd

[linux-usb-devel] Re: [patch] Patch to prevent overlapping access by usb-storage and usbfs

2004-06-03 Thread Pete Zaitcev
On Thu, 3 Jun 2004 22:06:06 +0200 Vojtech Pavlik <[EMAIL PROTECTED]> wrote: > The deadlocks might actually be my fault, as I re-used the serialize > semaphore, while the original 2.4 patch used it's own. Et tu Brut :-) I tried that as well, but the root problem is how dev->serialize is taken acr

[linux-usb-devel] Re: [patch] Patch to prevent overlapping access by usb-storage and usbfs

2004-06-03 Thread Vojtech Pavlik
On Thu, Jun 03, 2004 at 12:45:40PM -0700, Pete Zaitcev wrote: > I'm surprised that nobody noticed that the patch originates with Dell > people hitting a problem with Red Hat (on 2.4), and we discussed it > on the list. > > It is definitely needed for 2.4 in Red Hat, however I tried to turn > it

[linux-usb-devel] Linux 2.4.x mass storage devices

2004-06-03 Thread David Meggy
Hi I have a quick question about scsi names with Linux 2.4.x USB mass storage devices. When the 1st device is plugged in it will receive /dev/sda, and the second device will receive /dev/sdb. If I were to unplug the first device before plugging in the second device, the second device will still

[linux-usb-devel] Re: W996[87]CF decoder in kernel space as optional module

2004-06-03 Thread Luca Risolia
On Thu, 3 Jun 2004 12:51:50 -0400 Alan Cox <[EMAIL PROTECTED]> wrote: > The implementation looks ok although I don't see any low latency considerations > or is the camera sufficiently limited in quality you don't need to check for > yielding ? Last time I checked, there were no problems with Andr

[linux-usb-devel] Re: [patch] Patch to prevent overlapping access by usb-storage and usbfs

2004-06-03 Thread Pete Zaitcev
On Thu, 3 Jun 2004 12:07:50 -0700 Greg KH <[EMAIL PROTECTED]> wrote: > On Thu, Jun 03, 2004 at 02:05:42PM -0400, Alan Stern wrote: > > > > Greg, I'm afraid the patch from Vojtech has to be reverted. > > I agree. I've just done that, thanks. I'm surprised that nobody noticed that the patch orig

Re: [linux-usb-devel] [patch] Patch to prevent overlapping access by usb-storage and usbfs

2004-06-03 Thread Greg KH
On Thu, Jun 03, 2004 at 02:05:42PM -0400, Alan Stern wrote: > > Greg, I'm afraid the patch from Vojtech has to be reverted. I agree. I've just done that, thanks. greg k-h --- This SF.Net email is sponsored by the new InstallShield X. >From W

Re: [linux-usb-devel] W996[87]CF decoder in kernel space as optional module

2004-06-03 Thread James Courtier-Dutton
Tuukka Toivonen wrote: On Thu, 3 Jun 2004, James Courtier-Dutton wrote: I think that it would be greatly improved is there was a user land lib that applications talked to. With the kernel just doing the interface Have you looked at the GStreamer? It tries to be like this. It also tries to be much

Re: [linux-usb-devel] W996[87]CF decoder in kernel space as optional module

2004-06-03 Thread Tuukka Toivonen
On Thu, 3 Jun 2004, James Courtier-Dutton wrote: >I think that it would be greatly improved is there was a user land lib >that applications talked to. With the kernel just doing the interface Have you looked at the GStreamer? It tries to be like this. It also tries to be much more, which is why

Re: [linux-usb-devel] W996[87]CF decoder in kernel space as optional module

2004-06-03 Thread James Courtier-Dutton
Luca Risolia wrote: I am going to submit a patch for the Linux 2.6 adding the jpeg frame decoding feature (with integer arithmetics) to the w996[87]cf USB drivers. It is an _optional_ module, meaning that, even if compiled, the user can (load and) unload it whenever he wants to. I've not seen any o

Re: [linux-usb-devel] [patch] Patch to prevent overlapping access by usb-storage and usbfs

2004-06-03 Thread Alan Stern
On Thu, 3 Jun 2004, Olaf Hering wrote: > On Thu, Jun 03, Oliver Neukum wrote: > > > Am Donnerstag, 3. Juni 2004 18:39 schrieb Olaf Hering: > > > This patch causes deadlocks if you unplug and replug an usb-storage > > > device. > > > > Only on replug? > > yes. plug the usbstick in, reboot, ever

Re: [linux-usb-devel] Raced timeout

2004-06-03 Thread Pete Zaitcev
On Thu, 03 Jun 2004 12:35:30 -0400 David van Hoose <[EMAIL PROTECTED]> wrote: > I have been receiving the following weird message when connecting or > disconnecting my USB HP All-in-one. > > usb: raced timeout, pipe 0x8280 status 0 time left 0 Strictly speaking, it can happen infrequently on

Re: [linux-usb-devel] Raced timeout

2004-06-03 Thread David Brownell
David van Hoose wrote: usb: raced timeout, pipe 0x8280 status 0 time left 0 The synchronous control/bulk logic in 2.4 isn't correct in all cases ... it'd be good to just merge what 2.6 uses. That "raced" is an indication that you've hit a software bug. - Dave -

Re: [linux-usb-devel] memory leak in visor_write ?

2004-06-03 Thread Oliver Neukum
Am Donnerstag, 3. Juni 2004 18:43 schrieb nardelli: > I'm looking into possible memory leaks in the visor driver, > and I had a question regarding behavior of error handling on > failed urb submission. From what I understand, when > submitting a urb fails, the completion handler will not be > call

Re: [linux-usb-devel] [patch] Patch to prevent overlapping access by usb-storage and usbfs

2004-06-03 Thread Oliver Neukum
Am Donnerstag, 3. Juni 2004 18:39 schrieb Olaf Hering: > This patch causes deadlocks if you unplug and replug an usb-storage > device. Only on replug? Regards Oliver --- This SF.Net email is sponsored by the new Install

[linux-usb-devel] Re: memory leak in visor_write ?

2004-06-03 Thread Greg KH
On Thu, Jun 03, 2004 at 12:43:31PM -0400, nardelli wrote: > I'm looking into possible memory leaks in the visor driver, > and I had a question regarding behavior of error handling on > failed urb submission. From what I understand, when > submitting a urb fails, the completion handler will not be

[linux-usb-devel] Re: W996[87]CF decoder in kernel space as optional module

2004-06-03 Thread Alan Cox
On Thu, Jun 03, 2004 at 06:33:34PM +0200, Luca Risolia wrote: > V4L1 lacks the proper interface for decompression to be done in user > space, and none will (re-)write a V4L2 driver or patch the existing > V4L1 applications with new libraries, since a V4L1 driver > (with optional decoder in kernel s

[linux-usb-devel] Re: W996[87]CF decoder in kernel space as optional module

2004-06-03 Thread Tuukka Toivonen
On Thu, 3 Jun 2004, Luca Risolia wrote: >V4L1 lacks the proper interface for decompression to be done in user >space, and none will (re-)write a V4L2 driver or patch the existing I suppose you mean that V4L1 doesn't define the compressed format. You could add a device-specific format like qc-usb

[linux-usb-devel] memory leak in visor_write ?

2004-06-03 Thread nardelli
I'm looking into possible memory leaks in the visor driver, and I had a question regarding behavior of error handling on failed urb submission. From what I understand, when submitting a urb fails, the completion handler will not be called (as indicated in the api). It would appear that this case

Re: [linux-usb-devel] [patch] Patch to prevent overlapping access by usb-storage and usbfs

2004-06-03 Thread Olaf Hering
On Sun, May 30, Vojtech Pavlik wrote: > On Sun, May 30, 2004 at 02:52:27PM -0400, Alan Stern wrote: > > On Sun, 30 May 2004, Vojtech Pavlik wrote: > > > > > Okay, so can we all agree on this one? > > > > I don't know if it's really needed, but for consistency you might want to > > make a simil

[linux-usb-devel] Re: Raced timeout

2004-06-03 Thread David van Hoose
Hey again, Sorry for the extra message, but I'm not on the linux-usb-devel mailing list, so please CC responses. Thanks again, David David van Hoose wrote: Hello, I have been receiving the following weird message when connecting or disconnecting my USB HP All-in-one. usb: raced timeout, pipe 0x80

[linux-usb-devel] Re: W996[87]CF decoder in kernel space as optional module

2004-06-03 Thread Luca Risolia
On Thu, 3 Jun 2004 11:48:20 -0400 Alan Cox <[EMAIL PROTECTED]> wrote: > Why not do it in user space ? > > Also are you thinking of JPEG to RGB or JPEG to YUV420 or YUYV or > YV12 etc - each of which is the right answer depending on which > video card or further processing isbeing done. > I've co

[linux-usb-devel] Raced timeout

2004-06-03 Thread David van Hoose
Hello, I have been receiving the following weird message when connecting or disconnecting my USB HP All-in-one. usb: raced timeout, pipe 0x8280 status 0 time left 0 Sometimes the message is printed more than once each connection change. I have not noticed any problems with the printer portion.

Re: Re: [linux-usb-devel] Packet size too big error in usb host controller

2004-06-03 Thread Alan Stern
On Thu, 3 Jun 2004, sting sting wrote: > Hello, > Again thnxs; > I did added printk() as you suggested; I know now exactly where the problem > stems from; > it does not seems to me now a problem which comes from using big endian. > > in sl811.c we have the method sl811_submit_urb(struct urb* urb

[linux-usb-devel] Re: Suspend/resume questions

2004-06-03 Thread Alan Stern
On Wed, 2 Jun 2004, David Brownell wrote: > Alan Stern wrote: > > > > Right now, if I'm not mistaken, you don't enable remote wakeup on root > > hubs at all. So why should disabling it forever cause any problems? > > It's enabled as part of root hub registration, for root > hubs that report th

[linux-usb-devel] Re: W996[87]CF decoder in kernel space as optional module

2004-06-03 Thread Alan Cox
On Thu, Jun 03, 2004 at 05:45:47PM +0200, Luca Risolia wrote: > I am going to submit a patch for the Linux 2.6 adding > the jpeg frame decoding feature (with integer arithmetics) > to the w996[87]cf USB drivers. Why not do it in user space ? Also are you thinking of JPEG to RGB or JPEG to YUV420

[linux-usb-devel] W996[87]CF decoder in kernel space as optional module

2004-06-03 Thread Luca Risolia
I am going to submit a patch for the Linux 2.6 adding the jpeg frame decoding feature (with integer arithmetics) to the w996[87]cf USB drivers. It is an _optional_ module, meaning that, even if compiled, the user can (load and) unload it whenever he wants to. I've not seen any objections from the

Re: Re: [linux-usb-devel] Packet size too big error in usb host controller

2004-06-03 Thread sting sting
Hello, Again thnxs; I did added printk() as you suggested; I know now exactly where the problem stems from; it does not seems to me now a problem which comes from using big endian. in sl811.c we have the method sl811_submit_urb(struct urb* urb) in which I fail. The code in that method where the

[linux-usb-devel] can't locate HID device file

2004-06-03 Thread Damien McGivern
Hi, I've just moved from a Mandrake 10 (2.6.3) to a Knoppix/Debian 2.6.6 install. I had C++ code that opened the device file (all of which were located in /dev/usb/hid) and sent and recieved commands to and from the device. But with the new install the the /dev/usb/hid directory isn't being create

Re: Re: [linux-usb-devel] Packet size too big error in usb host controller

2004-06-03 Thread Alan Stern
On Thu, 3 Jun 2004, sting sting wrote: > Hello, > > Thanks a lot ! > > I had checked /proc/bus/usb/devices in both an x86 RedHat Linux and > with the platform with sl811 host controller; In both , maxpacket value is > <=64 > for non isochronous endpoints (most of these are Int.) > > the usb de

Re: Re: [linux-usb-devel] Packet size too big error in usb host controller

2004-06-03 Thread sting sting
Hello, Thanks a lot ! I had checked /proc/bus/usb/devices in both an x86 RedHat Linux and with the platform with sl811 host controller; In both , maxpacket value is <=64 for non isochronous endpoints (most of these are Int.) the usb device I use is not a mass storage device (but as I know this pl

[linux-usb-devel] Re: Hi

2004-06-03 Thread Autoresponder
Most likely the answer to your question is at: http://pc-magic.com/faq.htm Should you not find the answer to your question you will be told how to contact us directly. Thank you. (This is an automated response) --- This SF.Net email

[linux-usb-devel] Returned mail: see transcript for details

2004-06-03 Thread Mail Delivery Subsystem
The original message was received at Thu, 3 Jun 2004 03:27:37 -0400 (EDT) from localhost [127.0.0.1] - The following addresses had permanent fatal errors - <[EMAIL PROTECTED]> - Transcript of session follows - No directory entries found similar to '[EMAIL PROTECTED]' Please