Re: [linux-usb-devel] hid drivers

2007-04-13 Thread John Wojnaroski
Ok, some progress... here is the output of a small test program to sent a three byte packet to the device. Had to recompile the kernel to keep it from trying to claim the device and attach the usbhid driver. Here is the enumeration data <<,, > T: Bus=05 Lev=01 Prnt=01 Port=00 Cnt

Re: [linux-usb-devel] transparent BULK message passthrough

2007-04-13 Thread Greg KH
On Sat, Apr 14, 2007 at 12:39:46PM +1000, Julian PG wrote: > Hi, > Is it possible to be able to pass usb BULK messages (READ/WRITE) directly to > a > device while its already been claimed by a driver? >From userspace, or from within another driver in the kernel? > Is it trivial to add support f

[linux-usb-devel] transparent BULK message passthrough

2007-04-13 Thread Julian PG
Hi, Is it possible to be able to pass usb BULK messages (READ/WRITE) directly to a device while its already been claimed by a driver? Is it trivial to add support for this?I understand that this can already be done with CONTROL messages. However it doesnt seem so with BULK. It would an advantag

Re: [linux-usb-devel] usbmon status && extended urb information for binary API

2007-04-13 Thread Pete Zaitcev
On Fri, 13 Apr 2007 09:27:59 +0200, Paolo Abeni <[EMAIL PROTECTED]> wrote: > p.s. BTW I saw your submission for 'usbmon: bus zero' and > and 'usbmon: Add class for binary interface'. > > I don't want to seam rude, but I hoped to get a 'Signed-off-by' in one > of them... Reply to them and sign

Re: [linux-usb-devel] Reading the frame number field

2007-04-13 Thread Danny Budik
On Apr 13, 2007, at 12:01 PM, Alan Stern wrote: > Depends what you mean. The kernel-build system is smart enough to > recompile only the files you have changed (and those that depend on > them). > If what you changed is in a module instead of built into the main > kernel > binary, then only t

Re: [linux-usb-devel] hid drivers

2007-04-13 Thread Jiri Kosina
On Fri, 13 Apr 2007, John Wojnaroski wrote: > I'm writing a simple little driver to read three bytes from a hid device > when plugged in it reports as hiddev96:__--usb-:00:1d.0-2 > and shows up in /dev/usb/hiddev0 and is enumerated in > /proc/bus/usb/devices. Thinking a simple usb_c

[linux-usb-devel] Yahoo! Groups: Welcome to alamgir882001. Visit today!

2007-04-13 Thread alamgir882001 Moderator
Hello, Welcome to the alamgir882001 group at Yahoo! Groups, a free, easy-to-use email group service. Please take a moment to review this message. To learn more about the alamgir882001 group, please visit http://groups.yahoo.com/group/alamgir882001 To start sending messages to members of this

[linux-usb-devel] ether.c:rx_complete() question

2007-04-13 Thread Matt Reimer
I'm getting a hang in s3c2410_udc.c's nuke() function which is due to the same usb_request being queued back-to-back, with the result that the request on the endpoint's queue points to itself, thus causing nuke() to loop infinitely. (See below for a pseudo-trace for illustration.) In trying to fig

[linux-usb-devel] hid drivers

2007-04-13 Thread John Wojnaroski
Hi, I'm writing a simple little driver to read three bytes from a hid device when plugged in it reports as hiddev96:__--usb-:00:1d.0-2 and shows up in /dev/usb/hiddev0 and is enumerated in /proc/bus/usb/devices. Thinking a simple usb_control_msg will be good and simple enough t

Re: [linux-usb-devel] Reading the frame number field

2007-04-13 Thread Laurent Pinchart
On Friday 13 April 2007, Danny Budik wrote: > On Apr 12, 2007, at 9:27 PM, Pete Zaitcev wrote: > > On Thu, 12 Apr 2007 17:42:49 -0400, Danny Budik <[EMAIL PROTECTED] > > > > traffic.com> wrote: > >> It looks like I can add a constant say USBDEVFS_FRAMENUM in > >> usbdevice_fs.h, add new case to ...

Re: [linux-usb-devel] Issue of HUAWEI E220 On Linux

2007-04-13 Thread Phil Dibowitz
linlei 60022748 wrote: > In fact, We got info about the path -- huaweiAktBbo.out month ago.We have > tested > it and it's OK for E220 to make both CD-ROM and serial devices > available.We've > checked the souce code of that software and noticed that it uses the same > method > as Windows OS t

Re: [linux-usb-devel] Reading the frame number field

2007-04-13 Thread Alan Stern
On Thu, 12 Apr 2007, Danny Budik wrote: > On Apr 12, 2007, at 6:25 PM, Alan Stern wrote: > > > On Thu, 12 Apr 2007, Danny Budik wrote: > > > >> Would it be possible to add my own constant to /usr/include/linux/ > >> usbdevice_fs.h and write an underlying function that would call > >> usb_get_curr

[linux-usb-devel] [PATCH 5b/6] USB: make hub driver's release more robust

2007-04-13 Thread Alan Stern
This revised patch (as893b) improves the method used by the hub driver to release its private data structure. The current code is non-robust, relying on a memory region not getting reused by another driver after it has been freed. Signed-off-by: Alan Stern <[EMAIL PROTECTED]> --- It turned out

Re: [linux-usb-devel] Reading the frame number field

2007-04-13 Thread Danny Budik
On Apr 12, 2007, at 9:27 PM, Pete Zaitcev wrote: > On Thu, 12 Apr 2007 17:42:49 -0400, Danny Budik <[EMAIL PROTECTED] > traffic.com> wrote: > >> It looks like I can add a constant say USBDEVFS_FRAMENUM in >> usbdevice_fs.h, add new case to .../drivers/usb/core/devio.c, add a >> function called p

Re: [linux-usb-devel] How should an exit routine wait for release() callbacks?

2007-04-13 Thread Alan Stern
Tejun, it just occurred to me that you would be interested in this email thread. Just to bring you up to speed, here's the original question: > I've got a module which registers a struct device. (It represents a > virtual device, not a real one, but that doesn't matter.) Obviously the > module

Re: [linux-usb-devel] USB Lan device, kaweth failure in Linux

2007-04-13 Thread Oliver Neukum
Am Freitag, 13. April 2007 13:50 schrieb Roger Adair: > A long time ago I did compile ONE test kernel.  This weekend I will try > it again with your suggestions and see what happens … that is if "it > runs at all", with the following changes: > > CONFIG_USB_DEBUG > dmesg buffer size to 128KB > d

Re: [linux-usb-devel] Issue of HUAWEI E220 On Linux

2007-04-13 Thread Phil Dibowitz
linlei 60022748 wrote: > BUS="usb", SYSFS{idVendor}="12d1", SYSFS{idProduct}="1003", > SYSFS{bNumInterfaces}=" 1", RUN+="/usr/local/bin/huaweiAktBbo-i386.out " On second though, I know at least part of what's wrong here. Try: BUS=="usb", SYSFS{idVendor}=="12d1", SYSFS{idProduct}=="1003", SYSFS{bN

Re: [linux-usb-devel] How should an exit routine wait for release() callbacks?

2007-04-13 Thread Cornelia Huck
On Fri, 13 Apr 2007 16:15:18 +0200, "Markus Rechberger" <[EMAIL PROTECTED]> wrote: > most dvb usb drivers call the device node unregistration when a device > gets unplugged (when > At this time the filehandle can still be open, the patch on that site > sets a flag that disallows > any further ac

Re: [linux-usb-devel] How should an exit routine wait for release() callbacks?

2007-04-13 Thread Markus Rechberger
Cornelia Huck wrote: > On Fri, 13 Apr 2007 13:42:04 +0200, > "Markus Rechberger" <[EMAIL PROTECTED]> wrote: > > >> seems like you have the same problem as the dvb framework has/had. >> >> http://mcentral.de/hg/~mrec/v4l-dvb-stable >> >> The last 3 changesets do the trick to not oops, it will del

Re: [linux-usb-devel] How should an exit routine wait for release() callbacks?

2007-04-13 Thread Cornelia Huck
On Fri, 13 Apr 2007 13:42:04 +0200, "Markus Rechberger" <[EMAIL PROTECTED]> wrote: > seems like you have the same problem as the dvb framework has/had. > > http://mcentral.de/hg/~mrec/v4l-dvb-stable > > The last 3 changesets do the trick to not oops, it will delay the > deinitialization of the

[linux-usb-devel] USB Lan device, kaweth failure in Linux

2007-04-13 Thread Roger Adair
After thought! Could I just move the entire kernel 2.6.10 from the old Mepis to the new Mepis and save all this re compile operation ?? Roger - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Tech

[linux-usb-devel] USB Lan device, kaweth failure in Linux

2007-04-13 Thread Roger Adair
Hello Oliver, Hi Pete, Again many thanks. Really I had hoped that you would tell me to: modprobe "xxx.driver" and the OS would recognize the Xircom, ha ha. No such luck. You tell me that I’ll need "major heart surgery". A long time ago I did compile ONE test kernel. This weekend I will try

Re: [linux-usb-devel] How should an exit routine wait for release() callbacks?

2007-04-13 Thread Markus Rechberger
Alan, seems like you have the same problem as the dvb framework has/had. http://mcentral.de/hg/~mrec/v4l-dvb-stable The last 3 changesets do the trick to not oops, it will delay the deinitialization of the device till the last user closed the device node. Markus Cornelia Huck wrote: > On Thu,

Re: [linux-usb-devel] How should an exit routine wait for release() callbacks?

2007-04-13 Thread Cornelia Huck
On Thu, 12 Apr 2007 17:23:18 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> wrote: > Here's a not-so-theoretical question. > > I've got a module which registers a struct device. (It represents a > virtual device, not a real one, but that doesn't matter.) Obviously the > module's exit routine has t

Re: [linux-usb-devel] usbmon status && extended urb information for binary API

2007-04-13 Thread Paolo Abeni
Hello, On Tue, 2007-04-10 at 23:42 -0700, Pete Zaitcev wrote: > > - char flag_setup; > > + char flag_hdr; > > I don't think this is fully compatible. Why ?!? 'flag_hdr' is zero in exactly the same situation of old api. It can assume more values that are interpreted by old code as signal of s