-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 30 Jun 2003 15:38 pm, Schlup Rolf RUAG E wrote:
Hi,
I've developed a little application that allows me to control a DIS
entity with a spacemouse. It works fine using the /dev/js0 device. But now
I also need to send commands to the
On Sun, 29 Jun 2003, Adam Kessel wrote:
I got this message in kernel 2.5.73 after connecting my Neuros Audio
player:
usb-storage: Vendor: Frontier Labs
usb-storage: Product: Nex II Digital
usb-storage: This device (0451,5409) has unneeded SubClass and
Protocol entries in
I will try building 2.4.21 with usb-storage enabled. In the mean time,
I'm getting a lot of the same problems in 2.5.73, which I have built with
usb-storage.
Kernel output from usb-storage for 2.5.73 is here:
http://bostoncoop.net/adam/temp/kernel-log-2.5
The primary problem now seems to be
On Sun, Jun 29, 2003 at 12:16:01PM -0400, Alan Stern wrote:
On Sat, 28 Jun 2003, Matthew Dharm wrote:
If the files are the same now, then you should be able to apply this patch
to 2.4 -- that's one of the reasons Alan sent you a 2.4 patch to support
the US_*_DEVICE codes.
Matt
On Sat, Jun 28, 2003 at 10:46:30PM -0700, Matthew Dharm wrote:
This patch cleans up the logic involved in setting URB flags a bit so it's
more evident that some flags are always set and other flags are only set
under certain conditons.
Greg, please apply.
Applied, thanks.
greg k-h
On Sat, Jun 28, 2003 at 10:40:32PM -0700, Matthew Dharm wrote:
This patch avoids sending URBs which are part of the reset system when the
device is being disconnected. It also makes the control thread avoid
starting anything for a device in that state.
Greg, please apply.
Applied, thanks.
On Sat, Jun 28, 2003 at 10:36:37PM -0700, Matthew Dharm wrote:
This patch re-sorts unusual_devs.h and removes some duplicate entries.
Greg, please apply.
Applied, thanks.
greg k-h
---
This SF.Net email sponsored by: Free pre-built ASP.NET
On Sat, Jun 28, 2003 at 10:39:19PM -0700, Matthew Dharm wrote:
This patch creates an associate_dev(), which is the mirror to
disassociate_dev(). It also adds some more printout when identifiying
devices that qualify for US_*_DEVICE codes so we need less interaction with
the reporting user.
On Sat, Jun 28, 2003 at 10:43:18PM -0700, Matthew Dharm wrote:
This is some cosmetic cleanups. Things like changing dr to cr (they used
to stand for usb_devrequest, which is now usb_ctrlrequest), using strlcpy
instead of strncpy, and modifying some comments.
Greg, please apply.
Applied,
On Wed, Jun 25, 2003 at 09:56:38PM +0200, JOUANNE Mickael wrote:
Hello.
This is a patch for usbnet for working with Zaurus SL-C700.
The productid is different from other Zaurus, so i add an entry for it :)
Applied, thanks.
greg k-h
---
On Sat, Jun 28, 2003 at 10:45:35PM -0700, Matthew Dharm wrote:
This patch makes our private I/O buffer allocated such that it's pre-mapped
for DMA. We then add some logic to make sure that we don't try to re-map
it.
We also make the size of the buffer large enough for other sub-drivers,
On Sat, Jun 28, 2003 at 10:41:56PM -0700, Matthew Dharm wrote:
This patch creates a private I/O buffer for the 'core' subdrivers. This
allows us to fix all cases of DMAing to/from the stacks, statics, or other
bad places.
Greg, please apply.
Applied, thanks.
greg k-h
On Mon, 30 Jun 2003, Greg KH wrote:
On Sun, Jun 29, 2003 at 12:16:01PM -0400, Alan Stern wrote:
Perhaps they should be. One patch I sent in not too long ago removed some
flag bits that are completely unused in 2.5 and almost, but not quite,
entirely unused in 2.4. I believe the two
On Mon, 30 Jun 2003 [EMAIL PROTECTED] wrote:
Alan,
thank you *.debug works and *.* doesnt.
Here are the debug messages from kernel 2.4.21:
1. bootmessages regarding usb:
Boot messages are fine.
2. Now I connect the device:
That's also fine.
3. Now I mount the device and get the
Hi,
On 2.5.73 (and probably previously, I think I've seen this before), when
disconnecting a USB device from a UHCI host, I sometimes get the
following errors in my log.
drivers/usb/host/uhci-hcd.c: uhci_result_common() failed with status 44
[dec132a0] link (1ec13152) element (1ec00060)
0:
On Fri, Jun 27, 2003 at 05:03:21PM -0700, David Brownell wrote:
Greg KH wrote:
IMO this change would be worth considering for 2.5 even at this
late date, even though it'd break some TBD number of drivers.
What would break? At the worse, drivers would just spit back a bunch of
warnings
On Mon, Jun 30, 2003 at 05:48:56PM -0400, Johannes Erdfelt wrote:
On Mon, Jun 30, 2003, Greg KH [EMAIL PROTECTED] wrote:
On 2.5.73 (and probably previously, I think I've seen this before), when
disconnecting a USB device from a UHCI host, I sometimes get the
following errors in my log.
I
On Mon, Jun 30, 2003, Greg KH [EMAIL PROTECTED] wrote:
On 2.5.73 (and probably previously, I think I've seen this before), when
disconnecting a USB device from a UHCI host, I sometimes get the
following errors in my log.
I assume you mean unplug the device?
How reproducible is it now?
On Mon, Jun 30, 2003, Greg KH [EMAIL PROTECTED] wrote:
On Mon, Jun 30, 2003 at 05:48:56PM -0400, Johannes Erdfelt wrote:
On Mon, Jun 30, 2003, Greg KH [EMAIL PROTECTED] wrote:
drivers/usb/host/uhci-hcd.c: uhci_result_common() failed with status 44
[dec132a0] link (1ec13152) element
On Mon, Jun 30, 2003 at 06:09:54PM -0400, Johannes Erdfelt wrote:
Those kinda look like the driver is still trying to communicate with the
device like it's still there.
Are we sure the driver is getting the disconnect callback?
I hope so... This is for a USB trackball.
The fact the two
On Mon, Jun 30, 2003 at 03:02:32PM -0400, Alan Stern wrote:
Again, debugging output and the kernel log from the segfault would be
useful.
I thought this might be useful--this is from dmesg. In this case, it was
mount rather than umount which segfaulted:
Buffer I/O error on device sda1,
On Mon, Jun 30, 2003, Greg KH [EMAIL PROTECTED] wrote:
On Mon, Jun 30, 2003 at 06:09:54PM -0400, Johannes Erdfelt wrote:
I don't think this is a new thing, I think I've seen this in the past,
but haven't really tested removing devices a bunch on this machine
before (it's a USB 2.0
I haven't submitted any patches to uhci-hcd in a while so if this is
something recent, it could be something else has changed.
I don't think this is a new thing, I think I've seen this in the past,
but haven't really tested removing devices a bunch on this machine
before (it's a USB 2.0
Greg KH wrote:
Hm, in beating on this for a while, the only thing I saw odd was
reports of calls failing to usb_unlink_urb() by drivers in their
disconnect() functions. Which is what we would expect to have happen
here :)
In this case, no news is good news !! There are drivers that
don't bother
usb_disconnect() is never getting called from looking at the log.
Any other place you want me to put a message to see if it gets called?
With just CONFIG_USB_DEBUG enabled, I don't see any USB messages at all
before these start to loop.
It looks like from the messages you pasted that uhci-hcd
On Mon, Jun 30, 2003 at 04:27:41PM -0700, David Brownell wrote:
usb_disconnect() is never getting called from looking at the log.
Any other place you want me to put a message to see if it gets called?
With just CONFIG_USB_DEBUG enabled, I don't see any USB messages at all
before these start
On Mon, Jun 30, 2003 at 04:25:14PM -0700, David Brownell wrote:
Greg KH wrote:
Hm, in beating on this for a while, the only thing I saw odd was
reports of calls failing to usb_unlink_urb() by drivers in their
disconnect() functions. Which is what we would expect to have happen
here :)
On Mon, Jun 30, 2003 at 04:34:42PM -0700, Greg KH wrote:
Off to try no serial debug...
Heh, that works just fine. Ok, sorry for the noise here, this really
isn't a bug :)
Anyway, Johannes, mind if I turn down the debugging for that message, so
that isn't printed out all the time? I'll have to
David Brownell ([EMAIL PROTECTED]) said:
For any device X-Y in /sys/bus/usb/devices, it appears
X-Y:Z/name gives either Hub, or usb_make_path() interface Z.
Or whatever that interface's iInterface string provides,
or that interface's driver puts there. Those are purely
descriptive
On Mon, Jun 30, 2003 at 10:21:20PM -0400, Bill Nottingham wrote:
David Brownell ([EMAIL PROTECTED]) said:
For any device X-Y in /sys/bus/usb/devices, it appears
X-Y:Z/name gives either Hub, or usb_make_path() interface Z.
Or whatever that interface's iInterface string provides,
or
On Mon, 30 Jun 2003, Adam Kessel wrote:
I will try building 2.4.21 with usb-storage enabled. In the mean time,
I'm getting a lot of the same problems in 2.5.73, which I have built with
usb-storage.
Kernel output from usb-storage for 2.5.73 is here:
Alan,
thank you *.debug works and *.* doesnt.
Here are the debug messages from kernel 2.4.21:
1. bootmessages regarding usb:
-
Jun 30 20:26:08 debian kernel: usb.c: registered new driver usbdevfs
Jun 30 20:26:08 debian kernel: usb.c: registered new driver hub
Jun 30 20:26:08 debian
On Mon, Jun 30, 2003 at 03:10:56PM -0400, Alan Stern wrote:
On Mon, 30 Jun 2003, Greg KH wrote:
It looks like drivers/usb/storage/usb.c still checks for that value and
does something. Is that not needed anymore? If so, can we fix this up?
Yes, it still does check for that value and
Hi,
please have a look at:
buffer_free.patch:
dev-udev was set to NULL to indicate a device disconnect but we need
this value for usb_buffer_free() when device is still opened and cleanup is
delayed until skel_release().
I've added a dev-present for preventing device read, write and ioctl.
Also
Thanks
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
Thanks for helping me debug this!
On Mon, Jun 30, 2003 at 03:02:32PM -0400, Alan Stern wrote:
http://bostoncoop.net/adam/temp/kernel-log-2.5
I looked at this. It doesn't show any problems at all. Did you see
anything go wrong at the time this log was written?
I was experiencing some of
36 matches
Mail list logo
