Re: [linux-usb-devel] Stoneridge Optac Download Tool
Hi! Am Montag, 7. August 2006 08:43 schrieb Klaus Muth: I'm trying to read from an Stoneridge Optac Download tool (vend/prod 0x557/0x2008) for this European digital tachograph thing (see e.g. www.digitaltachograph.gov.uk/). The Optac tool is recognized correctly by the kernel as mass storage and usb-storage is loaded. Then all goes wrong: I retry, since Adam Stern told me to try again on 2.6. Additionally, I recompiled 2.6.16 with CONFIG_USB_DEBUG=y The dmesg output is now _very_ verbose, but hopefully somebody can help me. Plugin OPTAC Tool - usb 1-1: new full speed USB device using uhci_hcd and address 2 usb 1-1: configuration #1 chosen from 1 choice Initializing USB Mass Storage driver... usb-storage: USB Mass Storage device detected usb-storage: -- associate_dev usb-storage: Vendor: 0x, Product: 0x, Revision: 0x0100 usb-storage: Interface Subclass: 0x06, Protocol: 0x50 usb-storage: Transport: Bulk usb-storage: Protocol: Transparent SCSI usb-storage: *** thread sleeping. scsi0 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 2 usb-storage: waiting for device to settle before scanning usbcore: registered new driver usb-storage USB Mass Storage support registered. usb-storage: usb_stor_control_msg: rq=fe rqtype=a1 value= index=00 len=1 usb-storage: GetMaxLUN command result is 1, data is 0 usb-storage: queuecommand called usb-storage: *** thread awakened. usb-storage: Command INQUIRY (6 bytes) usb-storage: 12 00 00 00 24 00 usb-storage: Bulk Command S 0x43425355 T 0x1 L 36 F 128 Trg 0 LUN 0 CL 6 usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes usb-storage: Status code 0; transferred 31/31 usb-storage: -- transfer complete usb-storage: Bulk command transfer result=0 usb-storage: usb_stor_bulk_transfer_sglist: xfer 36 bytes, 1 entries usb-storage: Status code 0; transferred 36/36 usb-storage: -- transfer complete usb-storage: Bulk data transfer result 0x0 usb-storage: Attempting to get CSW... usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes usb-storage: Status code 0; transferred 13/13 usb-storage: -- transfer complete usb-storage: Bulk status result = 0 usb-storage: Bulk Status S 0x53425355 T 0x1 R 0 Stat 0x0 usb-storage: scsi cmd done, result=0x0 usb-storage: *** thread sleeping. Vendor: SRE Model: OPTAC ToolRev: 1.00 Type: Direct-Access ANSI SCSI revision: 00 usb-storage: queuecommand called usb-storage: *** thread awakened. usb-storage: Command TEST_UNIT_READY (6 bytes) usb-storage: 00 00 00 00 00 00 usb-storage: Bulk Command S 0x43425355 T 0x2 L 0 F 0 Trg 0 LUN 0 CL 6 usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes usb-storage: Status code 0; transferred 31/31 usb-storage: -- transfer complete usb-storage: Bulk command transfer result=0 usb-storage: Attempting to get CSW... usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes usb-storage: Status code 0; transferred 13/13 usb-storage: -- transfer complete usb-storage: Bulk status result = 0 usb-storage: Bulk Status S 0x53425355 T 0x2 R 0 Stat 0x0 usb-storage: scsi cmd done, result=0x0 usb-storage: *** thread sleeping. usb-storage: queuecommand called usb-storage: *** thread awakened. usb-storage: Command READ_CAPACITY (10 bytes) usb-storage: 25 00 00 00 00 00 00 00 00 00 usb-storage: Bulk Command S 0x43425355 T 0x3 L 8 F 128 Trg 0 LUN 0 CL 10 usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes usb-storage: Status code 0; transferred 31/31 usb-storage: -- transfer complete usb-storage: Bulk command transfer result=0 usb-storage: usb_stor_bulk_transfer_sglist: xfer 8 bytes, 1 entries usb-storage: Status code 0; transferred 8/8 usb-storage: -- transfer complete usb-storage: Bulk data transfer result 0x0 usb-storage: Attempting to get CSW... usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes usb-storage: Status code 0; transferred 13/13 usb-storage: -- transfer complete usb-storage: Bulk status result = 0 usb-storage: Bulk Status S 0x53425355 T 0x3 R 0 Stat 0x0 usb-storage: scsi cmd done, result=0x0 usb-storage: *** thread sleeping. SCSI device sda: 31744 512-byte hdwr sectors (16 MB) usb-storage: queuecommand called usb-storage: *** thread awakened. usb-storage: Command MODE_SENSE (6 bytes) usb-storage: 1a 00 3f 00 c0 00 usb-storage: Bulk Command S 0x43425355 T 0x4 L 192 F 128 Trg 0 LUN 0 CL 6 usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes usb-storage: Status code 0; transferred 31/31 usb-storage: -- transfer complete usb-storage: Bulk command transfer result=0 usb-storage: usb_stor_bulk_transfer_sglist: xfer 192 bytes, 1 entries usb-storage: Status code -121; transferred 4/192 usb-storage: -- short read transfer usb-storage: Bulk data transfer result 0x1 usb-storage: Attempting to get CSW... usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes usb-storage: Status code 0; transferred 13/13 usb-storage: -- transfer complete usb-storage: Bulk status result = 0 usb-storage: Bulk Status S 0x53425355 T 0x4 R 0 Stat
Re: [linux-usb-devel] [PATCH] add poll to gadgetfs's endpoint zero
On Monday 26 June 2006 3:53 am, Milan Svoboda wrote:
+static unsigned int
+ep0_poll (struct file *fd, poll_table *wait)
+{
+ struct dev_data *dev = fd-private_data;
+ int mask = 0;
+
+ spin_lock_irq (dev-lock);
It'd probably be better to call poll_wait() to add this to
the waitqueue _before_ grabbing the spinlock ... even if
that's safe, it looks dubious and other drivers avoid doing
such waitqueue updates while irqs are disabled.
OK.
+ /* report fd mode change before acting on it */
+ if (dev-setup_abort) {
+ dev-setup_abort = 0;
+ mask = POLLNVAL;
Man page says POLLNVAL means invalid, fd not open; so it
does not apply here ... POLLHUP makes more sense as a way
to indicate that the previous SETUP request was aborted,
or even POLLERR.
OK, I use POLLHUP.
Thank you for review, there is updated version:
Signed-off-by: Milan Svoboda [EMAIL PROTECTED]
---
diff -uprN -X ../../le/2.6/orig.bak.never.touch/Documentation/dontdiff
../../le/2.6/orig.bak.never.touch/drivers/usb/gadget/inode.c
test/drivers/usb/gadget/inode.c
--- ../../le/2.6/orig.bak.never.touch/drivers/usb/gadget/inode.c
2006-06-19 14:48:25.0 +
+++ test/drivers/usb/gadget/inode.c 2006-06-28 13:19:14.0
+
@@ -32,6 +32,7 @@
#include linux/compiler.h
#include asm/uaccess.h
#include linux/slab.h
+#include linux/poll.h
#include linux/device.h
#include linux/moduleparam.h
@@ -1230,6 +1237,35 @@ dev_release (struct inode *inode, struct
return 0;
}
+static unsigned int
+ep0_poll (struct file *fd, poll_table *wait)
+{
+ struct dev_data *dev = fd-private_data;
+ int mask = 0;
+
+ poll_wait(fd, dev-wait, wait);
+
+ spin_lock_irq (dev-lock);
+
+ /* report fd mode change before acting on it */
+ if (dev-setup_abort) {
+ dev-setup_abort = 0;
+ mask = POLLHUP;
+ goto out;
+ }
+
+ if (dev-state == STATE_SETUP) {
+ if (dev-setup_in || dev-setup_can_stall)
+ mask = POLLOUT;
+ } else {
+ if (dev-ev_next != 0)
+ mask = POLLIN;
+ }
+out:
+ spin_unlock_irq(dev-lock);
+ return mask;
+}
+
static int dev_ioctl (struct inode *inode, struct file *fd,
unsigned code, unsigned long value)
{
@@ -1249,7 +1285,7 @@ static struct file_operations ep0_io_ope
.read = ep0_read,
.write =ep0_write,
.fasync = ep0_fasync,
- // .poll = ep0_poll,
+ .poll = ep0_poll,
.ioctl =dev_ioctl,
.release = dev_release,
};
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] [PATCH] usb gadget: gadgetfs_dont_try_to_lock_before_free
cid:part1.08010705.09060809@ra.rockwell.comHello, I spotted this during my tests with -rt on arm. The -rt patch contains some better tools to diagnose problems with locks and some other things... Original code tries to take semaphore in BUG_ON and then free the memory with this semaphore. Patch is against 2.6.17. Signed-off-by: Milan Svoboda [EMAIL PROTECTED] --- diff -uprN -X rt/Documentation/dontdiff ../../le/2.6/orig.bak/drivers/usb/gadget/inode.c rt/drivers/usb/gadget/inode.c --- ../../le/2.6/orig.bak/drivers/usb/gadget/inode.c2006-06-19 14:50:48.0 + +++ rt/drivers/usb/gadget/inode.c 2006-06-29 14:53:07.0 + @@ -222,7 +223,6 @@ static void put_ep (struct ep_data *data /* needs no more cleanup */ BUG_ON (!list_empty (data-epfiles)); BUG_ON (waitqueue_active (data-wait)); - BUG_ON (down_trylock (data-lock) != 0); kfree (data); } - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] [PATCH] usb gadget: gadgetfs_add_resume_event.patch
This patch adds resume event into gadgetfs.
Patch is against 2.6.17.
Feedback and comments are highly appreciated.
Signed-off-by: Milan Svoboda [EMAIL PROTECTED]
---
diff -uprN -X orig.bak.never.touch/Documentation/dontdiff
orig.bak.never.touch/drivers/usb/gadget/inode.c
new_gadget/drivers/usb/gadget/inode.c
--- orig.bak.never.touch/drivers/usb/gadget/inode.c 2006-06-19
14:48:25.0 +
+++ new_gadget/drivers/usb/gadget/inode.c 2006-06-23 15:03:31.0
+
@@ -1114,6 +1168,7 @@ next_event (struct dev_data *dev, enum u
break;
case GADGETFS_SETUP:/* previous request timed out */
case GADGETFS_SUSPEND: /* same effect */
+ case GADGETFS_RESUME: /* same effect */
/* these events can't be repeated */
for (i = 0; i != dev-ev_next; i++) {
if (dev-event [i].type != type)
@@ -1728,6 +1817,26 @@ gadgetfs_suspend (struct usb_gadget *gad
spin_unlock (dev-lock);
}
+static void
+gadgetfs_resume (struct usb_gadget *gadget)
+{
+ struct dev_data *dev = get_gadget_data (gadget);
+
+ INFO (dev, resumed from state %d\n, dev-state);
+ spin_lock (dev-lock);
+ switch (dev-state) {
+ case STATE_SETUP: // VERY odd... host died??
+ case STATE_CONNECTED:
+ case STATE_UNCONNECTED:
+ next_event (dev, GADGETFS_RESUME);
+ ep0_readable (dev);
+ /* FALLTHROUGH */
+ default:
+ break;
+ }
+ spin_unlock (dev-lock);
+}
+
static struct usb_gadget_driver gadgetfs_driver = {
#ifdef CONFIG_USB_GADGET_DUALSPEED
.speed = USB_SPEED_HIGH,
@@ -1740,6 +1849,7 @@ static struct usb_gadget_driver gadgetfs
.setup = gadgetfs_setup,
.disconnect = gadgetfs_disconnect,
.suspend= gadgetfs_suspend,
+ .resume = gadgetfs_resume,
.driver = {
.name = (char *) shortname,
--- orig.bak/include/linux/usb_gadgetfs.h 2005-03-02 07:38:10.0
+
+++ new_gadget.newest/include/linux/usb_gadgetfs.h 2006-06-15
13:55:35.0 +
@@ -33,6 +33,7 @@ enum usb_gadgetfs_event_type {
GADGETFS_DISCONNECT,
GADGETFS_SETUP,
GADGETFS_SUSPEND,
+ GADGETFS_RESUME,
// and likely more !
};
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] dummy_hcd usage guidelines.
Hi I am trying understand the way USB host communicates with the devices. I do not have any UDC hardware for the gadget side drivers (say, ex. g_zero), but I infer from the description of the dummy_hcd driver, that this can be emulated. I'd be grateful if someone could point out good documents for setting it up. (if at all, it is possible the way I think it is). Any other reference is also welcome, (consider the fact that I'm a newbie). Thanks -- cheers ~coolant - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] [PATCH] Support for gzipped usb.ids files
On Sun, 2006-08-06 at 14:10 -0700, Randy.Dunlap wrote: It was just posted to the linux-pci m-l on Aug-04 and has not been acted on. I'm a bit worried that just storing a gzipped file as usb.ids will confuse users. Storing it as usb.ids.gz would make it more clear that it is a compressed file, but would require usbutils to probe for both usb.ids and usb.ids.gz. What is the stance pciutils takes on that issue? Tom - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] [Linux-usb-users] Is the HP 5-port USB 2.0 PCI controller card supported?
Hi, I just bought a HP branded USB 2.0 PCI controller card (5 port), which closely resembles the lspci output at http://www.qbik.ch/usb/devices/showctrl.php?id=61 Here's mine: 01:0a.0 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 [OHCI]) Subsystem: Unknown device 1631:0035 Flags: bus master, medium devsel, latency 64, IRQ 10 Memory at ff8f5000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 01:0a.1 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 [OHCI]) Subsystem: Unknown device 1631:0035 Flags: bus master, medium devsel, latency 64, IRQ 9 Memory at ff8f6000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 01:0a.2 USB Controller: NEC Corporation USB 2.0 (rev 04) (prog-if 20 [EHCI]) Subsystem: Unknown device 1631:1600 Flags: medium devsel, IRQ 11 Memory at ff8f7c00 (32-bit, non-prefetchable) [size=256] Capabilities: [40] Power Management version 2 01:0a.0 0c03: 1033:0035 (rev 43) 01:0a.1 0c03: 1033:0035 (rev 43) 01:0a.2 0c03: 1033:00e0 (rev 04) And here's the relevant dmesg output during boot: :01:0a.2 EHCI: unrecognized capability 00 ACPI: PCI Interrupt :01:0a.2[C] - Link [LNKA] - GSI 11 (level, low) - IRQ 11 ehci_hcd :01:0a.2: EHCI Host Controller ehci_hcd :01:0a.2: new USB bus registered, assigned bus number 1 ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) ehci_hcd :01:0a.2: irq 11, io mem 0xff8f7c00 ehci_hcd :01:0a.2: startup error -19 ehci_hcd :01:0a.2: USB bus 1 deregistered ACPI: PCI interrupt for device :01:0a.2 disabled ehci_hcd :01:0a.2: init :01:0a.2 fail, -19 ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10 PCI: setting IRQ 10 as level-triggered ACPI: PCI Interrupt :01:0a.0[A] - Link [LNKC] - GSI 10 (level, low) - IRQ 10 ohci_hcd :01:0a.0: OHCI Host Controller ohci_hcd :01:0a.0: new USB bus registered, assigned bus number 1 ohci_hcd :01:0a.0: irq 10, io mem 0xff8f5000 ACPI: PCI Interrupt :01:0a.1[B] - Link [LNKD] - GSI 9 (level, low) - IRQ9 ohci_hcd :01:0a.1: OHCI Host Controller ohci_hcd :01:0a.1: new USB bus registered, assigned bus number 2 ohci_hcd :01:0a.1: irq 9, io mem 0xff8f6000 This is on a system running 2.6.17.7 regards Andrew - 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 surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Claim Interface before snd_usb_audio does
Somewhere underneath all that sarcasm, I believe that you're saying that the device is violating the size of the isochronous packets. From my point of view this means that the packets are too small as I am interested in getting the device to work, not in fixing its, possibly broken, USB interface. However without a complete understanding of the USB stack, I cannot determine if a) The host informs the device of the sizes and offsets of the packets to use, according to the submitted URB, and then the device is supposed to follow them and if it doesn't you get the -EOVERFLOW? Or b) The URB merely informs the host what size packets to expect and the device sends what it has been configured to send and if they dont match then the -EOVERFLOW occurs? Jared Alan Stern wrote: Please send your messages to the mailing list as well as to me. On Wed, 2 Aug 2006, Jared Holzman wrote: Another quick question, what does the status -EOVERFLOW mean for individual isochronous packets? All the normal USB error codes are explained in Documentation/usb/error-codes.txt. -EOVERFLOW status means the received data packet was larger than expected. Alan Stern Could you be a bit more specific. Does that mean: 1) The individual isochronous packets were too small? No, it means they were too big. That's what "larger than expected" means. Something that is too small is not "larger than expected". 2) There weren't enough isochronous packets No, it doesn't mean there weren't enough of them. It means some of them (the ones that got the -EOVERFLOW status) were larger than expected. In other words, the actual packet size was larger than the value in urb-iso_frame_desc[n].length, where n is the index corresponding to the packet that got the -EOVERFLOW status. 3) The transfer buffer was too small No, if the transfer buffer were too small then usb_submit_urb() would have returned an error immediately. However you could argue that the value in urb-iso_frame_desc[n].length was too small. That's a matter of your point of view: Either the value of the length field was too small or the packet size was too big (or possibly both). All you have told us is that the requirement (the length field) = (the packet size) was violated. Without more information I can't say whether the fault lies on the left side or the right side of the inequality. 4) Something else... I think by now we have belabored the point sufficiently. Alan Stern - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] another error with ipod [ub(1.4): resid 0 len 32768 act 32256]
I hit another error with my video ipod (Bus 001 Device 004: ID 05ac:1209 Apple Computer, Inc.). It happens randonly when I tried to transfer ipod file. Aug 7 06:04:49 kafai-desk FAT: utf8 is not a recommended IO charset for FAT fil esystems, filesystem will be case sensitive! Aug 7 06:06:43 kafai-desk ub(1.4): resid 0 len 32768 act 32256 Aug 7 06:06:43 kafai-desk ub(1.4): dir w len/act 32768/32256 [sense 0 00 00] re try 1 Aug 7 06:06:43 kafai-desk usb 1-1: reset high speed USB device using ehci_hcd a nd address 4 Aug 7 06:06:46 kafai-desk ub(1.4): dir w len/act 32768/0 [sense 0 00 00] retry 2 Aug 7 06:06:47 kafai-desk end_request: I/O error, dev uba, sector 2692440 Aug 7 06:06:51 kafai-desk ub(1.4): dir w len/act 32768/0 [sense 0 00 00] retry 3 Aug 7 06:06:51 kafai-desk usb 1-1: reset high speed USB device using ehci_hcd a nd address 4 Aug 7 06:06:56 kafai-desk end_request: I/O error, dev uba, sector 2692376 Aug 7 06:06:56 kafai-desk end_request: I/O error, dev uba, sector 163143 Aug 7 06:06:56 kafai-desk FAT: FAT read failed (blocknr 2493) Aug 7 06:06:56 kafai-desk end_request: I/O error, dev uba, sector 2728392 Aug 7 06:06:56 kafai-desk end_request: I/O error, dev uba, sector 2728456 Aug 7 06:06:56 kafai-desk end_request: I/O error, dev uba, sector 2728520 Aug 7 06:06:56 kafai-desk end_request: I/O error, dev uba, sector 2728584 Aug 7 06:06:56 kafai-desk end_request: I/O error, dev uba, sector 2728648 Aug 7 06:06:56 kafai-desk end_request: I/O error, dev uba, sector 2728712 Aug 7 06:06:56 kafai-desk end_request: I/O error, dev uba, sector 2728776 --Martin - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Support for clearing Hub-TT buffers
On Mon, 7 Aug 2006, rakesh kn wrote: In function rh_call_control , there is no support for HUB_CLEAR_TT_BUFFER hub request. No. This is because rh_call_control handles only requests that are common to all root hubs. Since most root hubs don't support HUB_CLEAR_TT_BUFFER, neither does rh_call_control. Suppose if we are connecting low/full speed devices to a USB 2.0 EHCI , host controller., through a HUB , which has a transaction translator . Then the following function usb_hub_tt_clear_buffer will be called from the function qtd_copy_status in the file ehci-q.c .. in case of errors in CSPILT transaction . But since this is a hub-transaction request... the function rh_call_control , is not implementing the request type HUB_CLEAR_TT_BUFFER. Please explain why is this. Is the hub requests for external hubs handled elsewhere. Of course it is. It is sent to the external hub and handled there. Also why is that the TT hub contents not cleared if the EHCI controller has an embedded Transcation translator ,, as is evident from the following code in the function qtd_copy_status. I don't know. You should ask the person who developed the embedded TT support for EHCI. Alan Stern - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] [Linux-usb-users] Linux-usb-users
On Tue, 8 Aug 2006, Dave Higton wrote: -Original Message- From: Alan Stern [mailto:[EMAIL PROTECTED] Sent: 2006-Aug-07 15:57 To: Dave Higton Cc: USB development list Subject: Re: [Linux-usb-users] Linux-usb-users [Moved to linux-usb-devel because it seemed more appropriate] On Mon, 7 Aug 2006, Dave Higton wrote: I'm writing driver functions for a system that I'm working on (see below for details). The device in question has two interrupt mode endpoints: one in, one out. I'm having an unexpected problem: read from the input endpoint is unreliable. If I call usb_interrupt_read() with a timeout of 1, on average about half of the reads simply fail to return any data, i.e. the returned value is -110 despite the device having sent one or more messages. I can increase the duration of timeouts, but this is clearly a highly undesirable waste of time for the calling programme, and in any case, afaics, this will only reduce the probability of missing data, but not to zero. Do you understand that the timeout value is in milliseconds? Yes. So when you give a timeout of 1, that means you have allowed no more than 1 USB frame to get the data. You probably should make the timeout be at least 2 or 3 times the endpoint's period, to allow for missed messages and retries. I want to check repeatedly /whether/ any data have come in since the last call to usb_interrupt_read(). Normally, none will. I don't want to waste any time waiting for stuff that won't arrive. The calling task has other things to do! It sounds like you really do want to use an asynchronous request. Alternatively, you could use pthreads and set up a separate thread of your program devoted to waiting for those interrupt messages. Are you certain that the device sent one or more messages? Given that the timeout was one frame, how could it have possibly sent more than one message? Not one or more messages: zero or one message. Messages are only sent when there is a change in state of any of the switches. That one or more was a direct quote from your previous message. Bear in mind also that there's a difference between the device generating a message (queuing it to be sent) and actually sending the message. Messages are generated whenever the switches change state, but they can't be sent over USB until the host polls for them. I have tried calling usb_detach_kernal_driver_np(); the call succeeded (returned value 0), but there was no change to the symptoms. So: 1) How can I make the read 100% reliable, Give it a longer timeout. 2) How can I call non-blocking, buffered reads? Use asynchronous requests (now supported in the newest versions of libusb). This sounds like exactly what I need. Is it documented somewhere? The docs I've read still say that asynchronous operation is some time in the future. Have you installed the most recent version of libusb? I don't know in which release async support was added and I haven't looked at it in years, but I've heard that it's there now. Alan Stern - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] [Linux-usb-users] Linux-usb-users
-Original Message- From: Alan Stern [mailto:[EMAIL PROTECTED] Sent: 2006-Aug-08 15:30 To: Dave Higton Cc: USB development list Subject: RE: [Linux-usb-users] Linux-usb-users Have you installed the most recent version of libusb? I don't know in which release async support was added and I haven't looked at it in years, but I've heard that it's there now. The latest one I can see is 0.1.12, but the docs that come with it still talk about asynchronous in the future tense. Do you know of a later version? Do you know of asynchronous support having been added but the docs not updated? Dave - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Stoneridge Optac Download Tool
On Tue, 8 Aug 2006, Klaus Muth wrote: Hi! Am Montag, 7. August 2006 08:43 schrieb Klaus Muth: I'm trying to read from an Stoneridge Optac Download tool (vend/prod 0x557/0x2008) for this European digital tachograph thing (see e.g. www.digitaltachograph.gov.uk/). The Optac tool is recognized correctly by the kernel as mass storage and usb-storage is loaded. Then all goes wrong: I retry, since Adam Stern told me to try again on 2.6. Additionally, I recompiled 2.6.16 with CONFIG_USB_DEBUG=y The dmesg output is now _very_ verbose, but hopefully somebody can help me. Yes, unforunately usb-storage produces a _lot_ of debugging output. I think in this case it will help. I've skipped the unimportant sections of your log. Plugin OPTAC Tool - usb 1-1: new full speed USB device using uhci_hcd and address 2 usb 1-1: configuration #1 chosen from 1 choice Initializing USB Mass Storage driver... usb-storage: USB Mass Storage device detected usb-storage: -- associate_dev usb-storage: Vendor: 0x, Product: 0x, Revision: 0x0100 usb-storage: Interface Subclass: 0x06, Protocol: 0x50 usb-storage: Transport: Bulk usb-storage: Protocol: Transparent SCSI Interesting. You said above that the vendor and product IDs are 0x557 and 0x2008. How come they show up here as 0x and 0x? usb-storage: Command TEST_UNIT_READY (6 bytes) usb-storage: 00 00 00 00 00 00 usb-storage: Bulk Command S 0x43425355 T 0x5 L 0 F 0 Trg 0 LUN 0 CL 6 usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes usb-storage: Status code 0; transferred 31/31 usb-storage: -- transfer complete usb-storage: Bulk command transfer result=0 usb-storage: Attempting to get CSW... usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes usb-storage: Status code 0; transferred 13/13 usb-storage: -- transfer complete usb-storage: Bulk status result = 0 usb-storage: Bulk Status S 0x53425355 T 0x5 R 0 Stat 0x0 usb-storage: scsi cmd done, result=0x0 usb-storage: *** thread sleeping. usb-storage: queuecommand called usb-storage: *** thread awakened. The TEST UNIT READY command succeeded. By definition, that means the device is capable of reading data. usb-storage: Command ALLOW_MEDIUM_REMOVAL (6 bytes) usb-storage: 1e 00 00 00 01 00 usb-storage: Bulk Command S 0x43425355 T 0x6 L 0 F 0 Trg 0 LUN 0 CL 6 usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes usb-storage: Status code 0; transferred 31/31 usb-storage: -- transfer complete usb-storage: Bulk command transfer result=0 usb-storage: Attempting to get CSW... usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes usb-storage: Status code 0; transferred 13/13 usb-storage: -- transfer complete usb-storage: Bulk status result = 0 usb-storage: Bulk Status S 0x53425355 T 0x6 R 0 Stat 0x1 usb-storage: -- transport indicates command failure usb-storage: Issuing auto-REQUEST_SENSE usb-storage: Bulk Command S 0x43425355 T 0x7 L 18 F 128 Trg 0 LUN 0 CL 6 usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes usb-storage: Status code 0; transferred 31/31 usb-storage: -- transfer complete usb-storage: Bulk command transfer result=0 usb-storage: usb_stor_bulk_transfer_buf: xfer 18 bytes usb-storage: Status code 0; transferred 18/18 usb-storage: -- transfer complete usb-storage: Bulk data transfer result 0x0 usb-storage: Attempting to get CSW... usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes usb-storage: Status code 0; transferred 13/13 usb-storage: -- transfer complete usb-storage: Bulk status result = 0 usb-storage: Bulk Status S 0x53425355 T 0x7 R 0 Stat 0x0 usb-storage: -- Result from auto-sense is 0 usb-storage: -- code: 0x70, key: 0x6, ASC: 0x3a, ASCQ: 0x0 usb-storage: (Unknown Key): (unknown ASC/ASCQ) usb-storage: scsi cmd done, result=0x2 usb-storage: *** thread sleeping. PREVENT-ALLOW MEDIUM REMOVAL failed, and the sense info says: key = 6 (Unit Attention), ASC=0x3a (Medium Not Present). This response contains three errors: First, the sense key is wrong. Unit Attention should be used to report changes in the device's state. The key probably should have been 5 (Illegal Request). Second, the ASC code is wrong. If the device doesn't understand the command then it should set ASC=0x24 (Invalid Field in CDB). Third, the information is inconsistent with the success of the preceding TEST UNIT READY. How can the device be ready to read if no medium is present? The debug output of the mount command does not fit into the kernel ring buffer, but there are several blocks of this form: - SCSI device sda: 31744 512-byte hdwr sectors (16 MB) usb-storage: queuecommand called usb-storage: *** thread awakened. usb-storage: Command MODE_SENSE (6 bytes) usb-storage: 1a 00 3f 00 c0 00 usb-storage: Bulk Command S 0x43425355 T 0x2b L 192 F 128 Trg 0 LUN 0 CL 6 usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes usb-storage: Status code 0; transferred 31/31 usb-storage: --
Re: [linux-usb-devel] dummy_hcd usage guidelines.
On Tue, 8 Aug 2006, coolant wrote: Hi I am trying understand the way USB host communicates with the devices. Have you looked through the USB 2.0 specification? It's freely available at www.usb.org. I do not have any UDC hardware for the gadget side drivers (say, ex. g_zero), but I infer from the description of the dummy_hcd driver, that this can be emulated. Yes. I'd be grateful if someone could point out good documents for setting it up. (if at all, it is possible the way I think it is). Any other reference is also welcome, (consider the fact that I'm a newbie). I'm not aware of any documentation outside the kernel source except for the web page at http://www.linux-usb.org/gadget/ However, using dummy-hcd is very easy. You do this: modprobe dummy-hcd followed by modprobe g-zero (or whichever gadget driver you want to try out). Alan Stern - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] [Linux-usb-users] Linux-usb-users
-Original Message- From: Alan Stern [mailto:[EMAIL PROTECTED] Sent: 2006-Aug-08 15:30 To: Dave Higton Cc: USB development list Subject: RE: [Linux-usb-users] Linux-usb-users On Tue, 8 Aug 2006, Dave Higton wrote: If I call usb_interrupt_read() with a timeout of 1, on average about half of the reads simply fail to return any data, i.e. the returned value is -110 despite the device having sent one or more messages. [snip] Are you certain that the device sent one or more messages? Given that the timeout was one frame, how could it have possibly sent more than one message? Not one or more messages: zero or one message. Messages are only sent when there is a change in state of any of the switches. That one or more was a direct quote from your previous message. I agree, but I think the context is a little different. My one or more meant that the host misses messages apparently randomly, and sometimes misses two or more consecutive messages. Such missed messages are a minimum of some tens of milliseconds apart. My zero or one was in the context of the number of messages that can be sent in a frame, or in the time between calling usb_interrupt_read and the timeout. (Just by way of a clarification of what I meant; I'm not picking an argument with you!) Dave - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] [PATCH] Support for gzipped usb.ids files
On Tue, 08 Aug 2006 14:22:24 +0200 Thomas Sailer wrote: On Sun, 2006-08-06 at 14:10 -0700, Randy.Dunlap wrote: It was just posted to the linux-pci m-l on Aug-04 and has not been acted on. I'm a bit worried that just storing a gzipped file as usb.ids will confuse users. Storing it as usb.ids.gz would make it more clear that it is a compressed file, but would require usbutils to probe for both usb.ids and usb.ids.gz. What is the stance pciutils takes on that issue? Hi Tom, The proposed pciutils code looks for pci.ids.gz for the gzipped file. I agree, if gzipped, it should be .gz. --- ~Randy - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] [PATCH] Support for gzipped usb.ids files
On Tue, Aug 08, 2006 at 02:22:24PM +0200, Thomas Sailer wrote: On Sun, 2006-08-06 at 14:10 -0700, Randy.Dunlap wrote: It was just posted to the linux-pci m-l on Aug-04 and has not been acted on. I'm a bit worried that just storing a gzipped file as usb.ids will confuse users. Storing it as usb.ids.gz would make it more clear that it is a compressed file, but would require usbutils to probe for both usb.ids and usb.ids.gz. What is the stance pciutils takes on that issue? I have just check the patch for pciutils, it uses pci.ids.gz, but only probes for pci.ids.gz (and not pci.ids) when gzip support is activated. I will redo my patch to support both usb.ids and usb.ids.gz when gzip support is activated. Please expect a few days for that, it will depends if I am able to easily get an Internet connection in the next few days. Bye, Aurelien -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] This device (0e21, 0520, 0100 S 06 P 50) has an unneeded Protocol entry in unusual_devs.h
usb 5-5: new high speed USB device using ehci_hcd and address 4 usb 5-5: device descriptor read/64, error -71 usb 5-5: device descriptor read/64, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 5 usb 5-5: device descriptor read/all, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 6 usb 5-5: device descriptor read/all, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 7 usb 5-5: device descriptor read/all, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 8 usb 5-5: device descriptor read/64, error -71 usb 5-5: device descriptor read/64, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 9 usb 5-5: device descriptor read/all, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 10 usb 5-5: device descriptor read/8, error -71 usb 5-5: device descriptor read/8, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 11 usb 5-5: device descriptor read/8, error -71 usb 5-5: device descriptor read/8, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 12 usb 5-5: device descriptor read/64, error -71 usb 5-5: device descriptor read/64, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 13 usb 5-5: device descriptor read/64, error -71 usb 5-5: device descriptor read/64, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 14 usb 5-5: device descriptor read/8, error -71 usb 5-5: device descriptor read/8, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 15 usb 5-5: device descriptor read/8, error -71 usb 5-5: device descriptor read/8, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 16 usb 5-5: device descriptor read/64, error -71 usb 5-5: unable to read config index 0 descriptor/start usb 5-5: can't read configurations, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 17 usb 5-5: device descriptor read/64, error -71 usb 5-5: device descriptor read/64, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 18 usb 5-5: device descriptor read/8, error -71 usb 5-5: device descriptor read/8, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 19 usb 5-5: device descriptor read/8, error -71 usb 5-5: device descriptor read/8, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 20 usb 5-5: device descriptor read/64, error -71 usb 5-5: device descriptor read/64, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 21 usb 5-5: device descriptor read/all, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 22 usb 5-5: device descriptor read/8, error -71 usb 5-5: device descriptor read/8, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 23 usb 5-5: device descriptor read/8, error -71 usb 5-5: device descriptor read/8, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 24 usb 5-5: device descriptor read/64, error -71 usb 5-5: device descriptor read/64, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 25 usb 5-5: device descriptor read/64, error -71 usb 5-5: device descriptor read/64, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 26 usb 5-5: device descriptor read/8, error -71 usb 5-5: device descriptor read/8, error -71 usb 5-5: new high speed USB device using ehci_hcd and address 27 usb 5-5: device descriptor read/8, error -71 usb 5-5: unable to read config index 0 descriptor/start usb 5-5: can't read configurations, error -71 ehci_hcd :00:1d.7: remove, state 1 usb usb5: USB disconnect, address 1 ehci_hcd :00:1d.7: USB bus 5 deregistered ACPI: PCI interrupt for device :00:1d.7 disabled usb 3-1: new full speed USB device using uhci_hcd and address 2 usb 3-1: configuration #2 chosen from 1 choice usb-storage: This device (0e21,0520,0100 S 06 P 50) has an unneeded Protocol entry in unusual_devs.h Please send a copy of this message to linux-usb-devel@lists.sourceforge.net scsi3 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 2 usb-storage: waiting for device to settle before scanning Vendor: TOSHIBA Model: MK2006GAL Rev: BY30 Type: Direct-Access ANSI SCSI revision: 00 SCSI device sdb: 39063024 512-byte hdwr sectors (2 MB) sdb: Write Protect is off sdb: Mode Sense: 00 4a 00 00 sdb: assuming drive cache: write through SCSI device sdb: 39063024 512-byte hdwr sectors (2 MB) sdb: Write Protect is off sdb: Mode Sense: 00 4a 00 00 sdb: assuming drive cache: write through sdb: sdb1 sd 3:0:0:0: Attached scsi disk sdb usb-storage: device scan complete - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM
[linux-usb-devel] [PATCH] Add ADU support for Ontrak ADU devices.
Hi guys, John Homppi has created a patch which I have fixed up to work with kernel 2.6.17.7 and similar and I'd like to put it here for consideration into the main kernel. It adds support for Ontrak ADU relay I/O interfaces. URL: http://www.ontrak.net/products.htm - Table 5 6 The patch is available at: http://www.crc.id.au/files/adutux-0.0.13.patch.bz2 or http://www.crc.id.au/files/adutux-0.0.13.patch for those that like raw text. I didn't include it in this email as it's ~34Kb uncompressed. -- Steven Haigh Email: [EMAIL PROTECTED] Web: http://www.crc.id.au Phone: (03) 9017 0597 - 0412 935 897 - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] [Linux-usb-users] Linux-usb-users
On Tue, 8 Aug 2006, Dave Higton wrote: -Original Message- From: Alan Stern [mailto:[EMAIL PROTECTED] Sent: 2006-Aug-08 15:30 To: Dave Higton Cc: USB development list Subject: RE: [Linux-usb-users] Linux-usb-users Have you installed the most recent version of libusb? I don't know in which release async support was added and I haven't looked at it in years, but I've heard that it's there now. The latest one I can see is 0.1.12, but the docs that come with it still talk about asynchronous in the future tense. Do you know of a later version? Do you know of asynchronous support having been added but the docs not updated? That does look like the latest version available at sourceforge, and indeed it does not support asynchronous submissions. In fact, development on libusb appears to have slowed to a halt. Maybe someone else on the mailing list knows where a more advanced version is available. For now, this leaves you with two choices for async I/O. One possibility is what I mentioned earlier: create a second thread in your program and devote it to managing synchronous requests. The other option is to use the lower-level usbfs API. Alan Stern - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] [PATCH] Add ADU support for Ontrak ADU devices.
On Wed, Aug 09, 2006 at 03:26:59AM +1000, Steven Haigh wrote: Hi guys, John Homppi has created a patch which I have fixed up to work with kernel 2.6.17.7 and similar and I'd like to put it here for consideration into the main kernel. It adds support for Ontrak ADU relay I/O interfaces. URL: http://www.ontrak.net/products.htm - Table 5 6 The patch is available at: http://www.crc.id.au/files/adutux-0.0.13.patch.bz2 or http://www.crc.id.au/files/adutux-0.0.13.patch for those that like raw text. I didn't include it in this email as it's ~34Kb uncompressed. That's fine, you need to include it in the email, in the format described in the Documentation/SubmittingPatches file in order for us to be able to properly review it. thanks, greg k-h - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] [PATCH] Add ADU support for Ontrak ADU devices. (corrected)
This patch adds support for Ontrak ADU USB devices.
Patch is against 2.6.17.7
Feedback and comments are highly appreciated.
Signed-off-by: Steven Haigh [EMAIL PROTECTED]
---
diff -uprN -X linux-2.6.17.7-vanilla/Documentation/dontdiff
linux-2.6.17.7-vanilla/drivers/usb/input/hid-core.c linux-2.6.17.7/
drivers/usb/input/hid-core.c
--- linux-2.6.17.7-vanilla/drivers/usb/input/hid-core.c 2006-07-25
13:36:01.0 +1000
+++ linux-2.6.17.7/drivers/usb/input/hid-core.c 2006-08-07
15:27:11.0 +1000
@@ -1617,7 +1617,11 @@ static const struct hid_blacklist {
{ USB_VENDOR_ID_MGE, USB_DEVICE_ID_MGE_UPS, HID_QUIRK_IGNORE },
{ USB_VENDOR_ID_MGE, USB_DEVICE_ID_MGE_UPS1, HID_QUIRK_IGNORE },
{ USB_VENDOR_ID_ONTRAK, USB_DEVICE_ID_ONTRAK_ADU100,
HID_QUIRK_IGNORE },
+ { USB_VENDOR_ID_ONTRAK, USB_DEVICE_ID_ONTRAK_ADU100 + 20,
HID_QUIRK_IGNORE },
+ { USB_VENDOR_ID_ONTRAK, USB_DEVICE_ID_ONTRAK_ADU100 + 30,
HID_QUIRK_IGNORE },
{ USB_VENDOR_ID_ONTRAK, USB_DEVICE_ID_ONTRAK_ADU100 + 100,
HID_QUIRK_IGNORE },
+ { USB_VENDOR_ID_ONTRAK, USB_DEVICE_ID_ONTRAK_ADU100 + 108,
HID_QUIRK_IGNORE },
+ { USB_VENDOR_ID_ONTRAK, USB_DEVICE_ID_ONTRAK_ADU100 + 118,
HID_QUIRK_IGNORE },
{ USB_VENDOR_ID_ONTRAK, USB_DEVICE_ID_ONTRAK_ADU100 + 200,
HID_QUIRK_IGNORE },
{ USB_VENDOR_ID_ONTRAK, USB_DEVICE_ID_ONTRAK_ADU100 + 300,
HID_QUIRK_IGNORE },
{ USB_VENDOR_ID_ONTRAK, USB_DEVICE_ID_ONTRAK_ADU100 + 400,
HID_QUIRK_IGNORE },
diff -uprN -X linux-2.6.17.7-vanilla/Documentation/dontdiff
linux-2.6.17.7-vanilla/drivers/usb/Makefile linux-2.6.17.7/drivers/
usb/Makefile
--- linux-2.6.17.7-vanilla/drivers/usb/Makefile 2006-07-25
13:36:01.0 +1000
+++ linux-2.6.17.7/drivers/usb/Makefile 2006-08-07 15:27:11.0
+1000
@@ -61,6 +61,7 @@ obj-$(CONFIG_USB_TEST)+= misc/
obj-$(CONFIG_USB_USS720) += misc/
obj-$(CONFIG_USB_PHIDGETSERVO)+= misc/
obj-$(CONFIG_USB_SISUSBVGA) += misc/
+obj-$(CONFIG_USB_ADUTUX) += misc/
obj-$(CONFIG_USB_ATM) += atm/
obj-$(CONFIG_USB_SPEEDTOUCH) += atm/
diff -uprN -X linux-2.6.17.7-vanilla/Documentation/dontdiff
linux-2.6.17.7-vanilla/drivers/usb/misc/adutux.c linux-2.6.17.7/
drivers/usb/misc/adutux.c
--- linux-2.6.17.7-vanilla/drivers/usb/misc/adutux.c1970-01-01
10:00:00.0 +1000
+++ linux-2.6.17.7/drivers/usb/misc/adutux.c2006-08-09
07:32:33.0 +1000
@@ -0,0 +1,1051 @@
+/*
+ * adutux - driver for ADU devices from Ontrak Control Systems
+ * This is an experimental driver. Use at your own risk.
+ * This driver is not supported by Ontrak Control Systems.
+ *
+ * Copyright (c) 2003 John Homppi (SCO, leave this notice here)
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License as
+ * published by the Free Software Foundation; either version 2 of
+ * the License, or (at your option) any later version.
+ *
+ * derived from the Lego USB Tower driver 0.56:
+ * Copyright (c) 2003 David Glance davidgsf at sourceforge.net
+ * 2001 Juergen Stuber stuber at loria.fr
+ * that was derived from USB Skeleton driver - 0.5
+ * Copyright (c) 2001 Greg Kroah-Hartman (greg at kroah.com)
+ *
+ * History:
+ *
+ * 2006-08-07 - 0.0.13 - shaigh
+ * - fixed various errors to compile on kernel 2.6.17.7
+ * 2006-02-19 - 0.0.12 - jhomppi
+ * - remove the mode parameter from the usb_class_driver structure
+ * (for kernel version 2.6.15)
+ * 2006-02-03 - 0.0.11 jhomppi
+ * - remove the serial number retrieval short-cut
+ * 2006-01-16 - 0.0.10 jhomppi
+ * - use vendor/product table in adu_probe
+ * - check LINUX_VERSION_CODE for version of linux kernel
+ * and utilize appropriate termination of transfer
+ * 2005-12-02 - 0.0.9 jhomppi
+ * - pre-stage an input read URB to catch first read operation
+ * 2005-11-21 - 0.0.8 jhomppi
+ * - add ADU120,ADU130,ADU208,ADU218 to supported device list
+ * 2005-11-20 - 0.0.7 jhomppi
+ * - remove references to URB_ASYNC_UNLINK
+ * - add MODULE_LICENSE macro to identify our license to kernel
+ * 2005-09-20 - 0.0.6 jhomppi
+ * - replace deprecated usb_unlink_urb with usb_kill_urb
+ * 2003-12-23 - 0.0.5 jhomppi
+ * - urb after each read and write
+ * 2003-12-02 - 0.0.4 jhomppi
+ * - replace urb_submitted with urb status==-EINPROGRESS to stay
+ * in synch with real urb state
+ * - allow multiple open handles to the same device (now that
+ * urb_submitted problem has been removed)
+ * 2003-11-28 - 0.0.3 jhomppi
+ * - applied more changes suggested by Oliver Neukum
+ * - pre-start read if a buffer is available
+ * - correct the location of spin_unlock at end of a read
+ * - added hack to return serial number to caller if read buffer
+ * starts with an 's' (allows serial# retrieval without ioctl)
+ * - check that udev was not nuked by an early disconnect
+ *
Re: [linux-usb-devel] [PATCH] Add ADU support for Ontrak ADU devices. (corrected)
On Wed, Aug 09, 2006 at 07:42:06AM +1000, Steven Haigh wrote: This patch adds support for Ontrak ADU USB devices. Patch is against 2.6.17.7 Feedback and comments are highly appreciated. Signed-off-by: Steven Haigh [EMAIL PROTECTED] --- diff -uprN -X linux-2.6.17.7-vanilla/Documentation/dontdiff linux-2.6.17.7-vanilla/drivers/usb/input/hid-core.c linux-2.6.17.7/ drivers/usb/input/hid-core.c --- linux-2.6.17.7-vanilla/drivers/usb/input/hid-core.c 2006-07-25 13:36:01.0 +1000 +++ linux-2.6.17.7/drivers/usb/input/hid-core.c 2006-08-07 15:27:11.0 +1000 Ick, your email client line wrapped the patch. Care to try it again after fixing this? thanks, greg k-h - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] [PATCH] Add ADU support for Ontrak ADU devices.
This patch adds support for Ontrak ADU USB devices.
Patch is against 2.6.17.7
Feedback and comments are highly appreciated. Tried sending via mutt this
time, so hopefully line wrap won't be an issue.
Signed-off-by: Steven Haigh [EMAIL PROTECTED]
---
diff -uprN -X linux-2.6.17.7-vanilla/Documentation/dontdiff
linux-2.6.17.7-vanilla/drivers/usb/input/hid-core.c
linux-2.6.17.7/drivers/usb/input/hid-core.c
--- linux-2.6.17.7-vanilla/drivers/usb/input/hid-core.c 2006-07-25
13:36:01.0 +1000
+++ linux-2.6.17.7/drivers/usb/input/hid-core.c 2006-08-07 15:27:11.0
+1000
@@ -1617,7 +1617,11 @@ static const struct hid_blacklist {
{ USB_VENDOR_ID_MGE, USB_DEVICE_ID_MGE_UPS, HID_QUIRK_IGNORE },
{ USB_VENDOR_ID_MGE, USB_DEVICE_ID_MGE_UPS1, HID_QUIRK_IGNORE },
{ USB_VENDOR_ID_ONTRAK, USB_DEVICE_ID_ONTRAK_ADU100, HID_QUIRK_IGNORE },
+ { USB_VENDOR_ID_ONTRAK, USB_DEVICE_ID_ONTRAK_ADU100 + 20,
HID_QUIRK_IGNORE },
+ { USB_VENDOR_ID_ONTRAK, USB_DEVICE_ID_ONTRAK_ADU100 + 30,
HID_QUIRK_IGNORE },
{ USB_VENDOR_ID_ONTRAK, USB_DEVICE_ID_ONTRAK_ADU100 + 100,
HID_QUIRK_IGNORE },
+ { USB_VENDOR_ID_ONTRAK, USB_DEVICE_ID_ONTRAK_ADU100 + 108,
HID_QUIRK_IGNORE },
+ { USB_VENDOR_ID_ONTRAK, USB_DEVICE_ID_ONTRAK_ADU100 + 118,
HID_QUIRK_IGNORE },
{ USB_VENDOR_ID_ONTRAK, USB_DEVICE_ID_ONTRAK_ADU100 + 200,
HID_QUIRK_IGNORE },
{ USB_VENDOR_ID_ONTRAK, USB_DEVICE_ID_ONTRAK_ADU100 + 300,
HID_QUIRK_IGNORE },
{ USB_VENDOR_ID_ONTRAK, USB_DEVICE_ID_ONTRAK_ADU100 + 400,
HID_QUIRK_IGNORE },
diff -uprN -X linux-2.6.17.7-vanilla/Documentation/dontdiff
linux-2.6.17.7-vanilla/drivers/usb/Makefile linux-2.6.17.7/drivers/usb/Makefile
--- linux-2.6.17.7-vanilla/drivers/usb/Makefile 2006-07-25 13:36:01.0
+1000
+++ linux-2.6.17.7/drivers/usb/Makefile 2006-08-07 15:27:11.0 +1000
@@ -61,6 +61,7 @@ obj-$(CONFIG_USB_TEST)+= misc/
obj-$(CONFIG_USB_USS720) += misc/
obj-$(CONFIG_USB_PHIDGETSERVO) += misc/
obj-$(CONFIG_USB_SISUSBVGA)+= misc/
+obj-$(CONFIG_USB_ADUTUX) += misc/
obj-$(CONFIG_USB_ATM) += atm/
obj-$(CONFIG_USB_SPEEDTOUCH) += atm/
diff -uprN -X linux-2.6.17.7-vanilla/Documentation/dontdiff
linux-2.6.17.7-vanilla/drivers/usb/misc/adutux.c
linux-2.6.17.7/drivers/usb/misc/adutux.c
--- linux-2.6.17.7-vanilla/drivers/usb/misc/adutux.c1970-01-01
10:00:00.0 +1000
+++ linux-2.6.17.7/drivers/usb/misc/adutux.c2006-08-09 07:32:33.0
+1000
@@ -0,0 +1,1051 @@
+/*
+ * adutux - driver for ADU devices from Ontrak Control Systems
+ * This is an experimental driver. Use at your own risk.
+ * This driver is not supported by Ontrak Control Systems.
+ *
+ * Copyright (c) 2003 John Homppi (SCO, leave this notice here)
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License as
+ * published by the Free Software Foundation; either version 2 of
+ * the License, or (at your option) any later version.
+ *
+ * derived from the Lego USB Tower driver 0.56:
+ * Copyright (c) 2003 David Glance davidgsf at sourceforge.net
+ * 2001 Juergen Stuber stuber at loria.fr
+ * that was derived from USB Skeleton driver - 0.5
+ * Copyright (c) 2001 Greg Kroah-Hartman (greg at kroah.com)
+ *
+ * History:
+ *
+ * 2006-08-07 - 0.0.13 - shaigh
+ * - fixed various errors to compile on kernel 2.6.17.7
+ * 2006-02-19 - 0.0.12 - jhomppi
+ * - remove the mode parameter from the usb_class_driver structure
+ * (for kernel version 2.6.15)
+ * 2006-02-03 - 0.0.11 jhomppi
+ * - remove the serial number retrieval short-cut
+ * 2006-01-16 - 0.0.10 jhomppi
+ * - use vendor/product table in adu_probe
+ * - check LINUX_VERSION_CODE for version of linux kernel
+ * and utilize appropriate termination of transfer
+ * 2005-12-02 - 0.0.9 jhomppi
+ * - pre-stage an input read URB to catch first read operation
+ * 2005-11-21 - 0.0.8 jhomppi
+ * - add ADU120,ADU130,ADU208,ADU218 to supported device list
+ * 2005-11-20 - 0.0.7 jhomppi
+ * - remove references to URB_ASYNC_UNLINK
+ * - add MODULE_LICENSE macro to identify our license to kernel
+ * 2005-09-20 - 0.0.6 jhomppi
+ * - replace deprecated usb_unlink_urb with usb_kill_urb
+ * 2003-12-23 - 0.0.5 jhomppi
+ * - urb after each read and write
+ * 2003-12-02 - 0.0.4 jhomppi
+ * - replace urb_submitted with urb status==-EINPROGRESS to stay
+ * in synch with real urb state
+ * - allow multiple open handles to the same device (now that
+ * urb_submitted problem has been removed)
+ * 2003-11-28 - 0.0.3 jhomppi
+ * - applied more changes suggested by Oliver Neukum
+ * - pre-start read if a buffer is available
+ * - correct the location of spin_unlock at end of a read
+ * - added hack to return serial number to caller if read buffer
+ * starts with an 's' (allows serial# retrieval without ioctl)
+ * - check that udev
Re: [linux-usb-devel] another error with ipod [ub(1.4): resid 0 len 32768 act 32256]
Does it have any data I can gather to help debugging? turning on debug message? --Martin - Original Message From: Martin (KaFai), Lau [EMAIL PROTECTED] To: linux-usb-devel@lists.sourceforge.net Sent: Tuesday, August 8, 2006 6:15:14 AM Subject: another error with ipod [ub(1.4): resid 0 len 32768 act 32256] I hit another error with my video ipod (Bus 001 Device 004: ID 05ac:1209 Apple Computer, Inc.). It happens randonly when I tried to transfer ipod file. Aug 7 06:04:49 kafai-desk FAT: utf8 is not a recommended IO charset for FAT fil esystems, filesystem will be case sensitive! Aug 7 06:06:43 kafai-desk ub(1.4): resid 0 len 32768 act 32256 Aug 7 06:06:43 kafai-desk ub(1.4): dir w len/act 32768/32256 [sense 0 00 00] re try 1 Aug 7 06:06:43 kafai-desk usb 1-1: reset high speed USB device using ehci_hcd a nd address 4 Aug 7 06:06:46 kafai-desk ub(1.4): dir w len/act 32768/0 [sense 0 00 00] retry 2 Aug 7 06:06:47 kafai-desk end_request: I/O error, dev uba, sector 2692440 Aug 7 06:06:51 kafai-desk ub(1.4): dir w len/act 32768/0 [sense 0 00 00] retry 3 Aug 7 06:06:51 kafai-desk usb 1-1: reset high speed USB device using ehci_hcd a nd address 4 Aug 7 06:06:56 kafai-desk end_request: I/O error, dev uba, sector 2692376 Aug 7 06:06:56 kafai-desk end_request: I/O error, dev uba, sector 163143 Aug 7 06:06:56 kafai-desk FAT: FAT read failed (blocknr 2493) Aug 7 06:06:56 kafai-desk end_request: I/O error, dev uba, sector 2728392 Aug 7 06:06:56 kafai-desk end_request: I/O error, dev uba, sector 2728456 Aug 7 06:06:56 kafai-desk end_request: I/O error, dev uba, sector 2728520 Aug 7 06:06:56 kafai-desk end_request: I/O error, dev uba, sector 2728584 Aug 7 06:06:56 kafai-desk end_request: I/O error, dev uba, sector 2728648 Aug 7 06:06:56 kafai-desk end_request: I/O error, dev uba, sector 2728712 Aug 7 06:06:56 kafai-desk end_request: I/O error, dev uba, sector 2728776 --Martin - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] another error with ipod [ub(1.4): resid 0 len 32768 act 32256]
On Tue, 8 Aug 2006 06:15:14 -0700 (PDT), Martin (KaFai), Lau [EMAIL PROTECTED] wrote: Aug 7 06:06:43 kafai-desk ub(1.4): resid 0 len 32768 act 32256 Aug 7 06:06:43 kafai-desk ub(1.4): dir w len/act 32768/32256 [sense 0 00 00] retry 1 Aug 7 06:06:43 kafai-desk usb 1-1: reset high speed USB device using ehci_hcd and address 4 Aug 7 06:06:46 kafai-desk ub(1.4): dir w len/act 32768/0 [sense 0 00 00] retry 2 Aug 7 06:06:47 kafai-desk end_request: I/O error, dev uba, sector 2692440 Well, if that happens, try to reproduce with usb-storage. Only then someone other than I would be interested. I suspect that something is not right with the hardware somewhere. -- Pete - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
