[linux-usb-devel] question for add multi-serial port to usb serial driver
hello Now I am working on add multiple usb serial port support to gserial.c, I had refer that qualcomm 3G phone that support 3 usb port on windows pc. On enumeration stage , with ONLY ONE usb reset, the host start four 80 06 00 01 00 00 12 00 each for a different virtual usb device, Host start first get_device_descriptor for device 17, the client answer it has three interface,then following the get_configuration, set_configuration procedure. Then host send the next three get_device req, answer by this three interface(that is device 20,21,22), each answer it has one configuration, one interface. I see qualcomm's inf file that has this %xxx% = QportInstall6k, SB\VID_1234PID_MI_01 %xxx% = QportInstallNMEA, USB\VID_1234PID_MI_02 xxx% = QportInstalltest, USB\VID_1234PID_MI_00 all this three has same VIDPID, diff only on MI.what does MI means? It seems that host locate driver not only throught vidpid, what is the rule, i can't find it in specification. what is the reason that windows pc send four get_device_descriptor to devices with only the first request precede a usb reset ? Is it because that the first device descriptor set bDeviceClass to 0 and the inf has three entry with same vid,pid , only diff on MI? I also wonder by using this method to create a usb device with multiple interface, each interface play independly works, that first interface work as mass-storage, second works as net device, Is that possible? thank (17) USB Composite Device (20) Proprietary USB Modem (21) NMEA Device (COM10) (22) Diagnostics Interface(COM9) _ 与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ 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] drivers/usb/host/isp116x-hcd.c: Removed unused variable
Greg, please apply.
Olav
-
From: Daniel Marjamäki [EMAIL PROTECTED]
Removed unused variable
Signed-off-by: Daniel Marjamäki [EMAIL PROTECTED]
Signed-off-by: Olav Kongas [EMAIL PROTECTED]
--- a/drivers/usb/host/isp116x-hcd.c2005-12-05 06:57:47.0 +0100
+++ b/drivers/usb/host/isp116x-hcd.c2005-12-13 09:52:31.0 +0100
@@ -164,13 +164,11 @@ static void pack_fifo(struct isp116x *is
struct ptd *ptd;
int buflen = isp116x-atl_last_dir == PTD_DIR_IN
? isp116x-atl_bufshrt : isp116x-atl_buflen;
- int ptd_count = 0;
isp116x_write_reg16(isp116x, HCuPINT, HCuPINT_AIIEOT);
isp116x_write_reg16(isp116x, HCXFERCTR, buflen);
isp116x_write_addr(isp116x, HCATLPORT | ISP116x_WRITE_OFFSET);
for (ep = isp116x-atl_active; ep; ep = ep-active) {
- ++ptd_count;
ptd = ep-ptd;
dump_ptd(ptd);
dump_ptd_out_data(ptd, ep-data);
Re: [linux-usb-devel] 2nd device node not created with dual joypad adapter
On Tue, 13 Dec 2005, Michael Alladin wrote: After doing some digging with regards to my original problem (PSX Dual Pad adapter not functioning) I have noticed a couple of things. 1. Even though it's a DUAL Adapter, only ONE device node, /dev/input/js0 is created. No matter how many joysticks I plug in i.e. 0, 1 or 2. 2. After turning on the usb debugging, I found that upon plugging in the adapter, two report_id's are registered (0 and 1), however when running cat /dev/input/js0 I get lots of the messages like this: Dec 6 08:29:04 crypt kernel: drivers/usb/input/hid-core.c: report (size 7) (numbered) Dec 6 08:29:04 crypt kernel: drivers/usb/input/hid-core.c: report 64 (size 6) = 02 08 02 40 20 84 Dec 6 08:29:04 crypt kernel: drivers/usb/input/hid-core.c: undefined report_id 64 received Oh, and there's the initial descriptor read error -32 upon pluggin in the device. Any ideas/suggestions? Can't help with the input device and report problems. The descriptor read error -32 indicates that the PSX adapter doesn't support string descriptors, which means you won't see its vendor or product name in places like /proc/bus/usb/devices. It's not an important error. Alan Stern --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ 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] Logging file transfers
Hello, I want to be able to log file transfers from a PC to USB storage devices? Can this be achieved in user space or will I have to patch the kernel usb storage driver to achieve this. I was thinking the latter would be the obvious choice. Any ideas on this would be appreciated. Thanks, Garyc --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ 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] question for add multi-serial port to usb serial driver
On Tue, 13 Dec 2005, tong changda wrote: hello Now I am working on add multiple usb serial port support to gserial.c, I had refer that qualcomm 3G phone that support 3 usb port on windows pc. On enumeration stage , with ONLY ONE usb reset, the host start four 80 06 00 01 00 00 12 00 each for a different virtual usb device, Host start first get_device_descriptor for device 17, the client answer it has three interface,then following the get_configuration, set_configuration procedure. Then host send the next three get_device req, answer by this three interface(that is device 20,21,22), each answer it has one configuration, one interface. That doesn't make sense for a composite device. First, the device descriptor does not contain the number of interfaces. Second, get-device requests are sent to a device, not to a particular interface. Maybe you're talking about a compound device instead? With a compound device, the host would first enumerate the internal hub and then it would enumerate all the other internal sub-devices. I see qualcomm's inf file that has this %xxx% = QportInstall6k, SB\VID_1234PID_MI_01 %xxx% = QportInstallNMEA, USB\VID_1234PID_MI_02 xxx% = QportInstalltest, USB\VID_1234PID_MI_00 all this three has same VIDPID, diff only on MI.what does MI means? It seems that host locate driver not only throught vidpid, what is the rule, i can't find it in specification. What specification? what is the reason that windows pc send four get_device_descriptor to devices with only the first request precede a usb reset ? Is it because that the first device descriptor set bDeviceClass to 0 and the inf has three entry with same vid,pid , only diff on MI? I don't know why Windows does much of anything, and probably most of the other people on this mailing list don't know too much about Windows either. I also wonder by using this method to create a usb device with multiple interface, each interface play independly works, that first interface work as mass-storage, second works as net device, Is that possible? Yes it is. It would be a composite device, not a compound device. Alan Stern --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ 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] usbcore: fix local variable clash
Greg: This patch (as621) fixes a local variable conflict I accidently introduced into usb_set_configuration. Alan Stern Signed-off-by: Alan Stern [EMAIL PROTECTED] --- Index: usb-2.6/drivers/usb/core/message.c === --- usb-2.6.orig/drivers/usb/core/message.c +++ usb-2.6/drivers/usb/core/message.c @@ -1387,11 +1387,11 @@ free_interfaces: if (dev-state != USB_STATE_ADDRESS) usb_disable_device (dev, 1);// Skip ep0 - n = dev-bus_mA - cp-desc.bMaxPower * 2; - if (n 0) + i = dev-bus_mA - cp-desc.bMaxPower * 2; + if (i 0) dev_warn(dev-dev, new config #%d exceeds power limit by %dmA\n, - configuration, -n); + configuration, -i); if ((ret = usb_control_msg(dev, usb_sndctrlpipe(dev, 0), USB_REQ_SET_CONFIGURATION, 0, configuration, 0, --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ 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] Re: 2.6.15-rc5-mm1
On Tue, 13 Dec 2005, J.A. Magallon wrote: Bingo! This corrected the problem. I applied it to rc5-mm2 and booted nicely. One less bug. A side question. Are this messages dangerous ? hub 4-0:1.0: USB hub found hub 4-0:1.0: 2 ports detected ACPI: PCI Interrupt :00:1d.7[D] - GSI 23 (level, low) - IRQ 19 PCI: Setting latency timer of device :00:1d.7 to 64 ehci_hcd :00:1d.7: EHCI Host Controller PCI: cache line size of 128 is not supported by device :00:1d.7 I don't think that matters. It's more informational than a warning. ehci_hcd :00:1d.7: new USB bus registered, assigned bus number 5 ehci_hcd :00:1d.7: irq 19, io mem 0xed20 ehci_hcd :00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb 1-1: unable to read config index 0 descriptor/all ^ usb 1-1: can't read configurations, error -71 ^ These messages indicate a real problem. The device plugged into your first USB port didn't respond to a request. It might not matter though, because the system will retry. If the device works then you don't need to worry about it. Alan Stern --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ 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] Logging file transfers
On Tue, 13 Dec 2005, gary clark wrote: Hello, I want to be able to log file transfers from a PC to USB storage devices? Can this be achieved in user space or will I have to patch the kernel usb storage driver to achieve this. I was thinking the latter would be the obvious choice. Any ideas on this would be appreciated. There's no way to do this from within the kernel. The kernel can't tell the difference between a file transfer and any other I/O operation. And usb-storage can't tell whether a particular I/O operation involves file data. A simple userspace approach would be to set up a shell alias for the cp command. Have it add a line to the log file in addition to doing the copy. Of course, that won't catch all file transfers. Alan Stern --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ 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 2.6.14-rc5] ftdi_sio: new IDs for Teratronik devices
From: Ian Abbott [EMAIL PROTECTED]
Hi Greg,
This patch adds vendor and product IDs to the ftdi_sio driver's device
ID table for two devices from teratronik.de. The device IDs were
submitted by O. Wölfelschneider of Teratronik Elektronische Systeme GmbH.
The charset of the patch is latin-1, same as the original files.
Please apply, thanks! (I've tried to avoid a clash with Andrew Morton's
patch to add support for Posiflex PP-7700 printer to the same driver.)
Signed-off-by: Ian Abbott [EMAIL PROTECTED]
diff -ur a/drivers/usb/serial/ftdi_sio.c b/drivers/usb/serial/ftdi_sio.c
--- a/drivers/usb/serial/ftdi_sio.c 2005-12-13 15:43:50.0 +
+++ b/drivers/usb/serial/ftdi_sio.c 2005-12-13 15:56:49.0 +
@@ -471,6 +471,8 @@
{ USB_DEVICE(FTDI_VID, FTDI_ACTIVE_ROBOTS_PID) },
{ USB_DEVICE(FTDI_VID, FTDI_MHAM_Y6_PID) },
{ USB_DEVICE(FTDI_VID, FTDI_MHAM_Y8_PID) },
+ { USB_DEVICE(FTDI_VID, FTDI_TERATRONIK_VCP_PID) },
+ { USB_DEVICE(FTDI_VID, FTDI_TERATRONIK_D2XX_PID) },
{ USB_DEVICE(EVOLUTION_VID, EVOLUTION_ER1_PID) },
{ USB_DEVICE(FTDI_VID, FTDI_ARTEMIS_PID) },
{ USB_DEVICE(FTDI_VID, FTDI_ATIK_ATK16_PID) },
diff -ur a/drivers/usb/serial/ftdi_sio.h b/drivers/usb/serial/ftdi_sio.h
--- a/drivers/usb/serial/ftdi_sio.h 2005-12-13 15:43:50.0 +
+++ b/drivers/usb/serial/ftdi_sio.h 2005-12-13 15:54:06.0 +
@@ -343,6 +343,13 @@
#define XSENS_CONVERTER_7_PID 0xD38F
/*
+ * Teratronik product ids.
+ * Submitted by O. Wölfelschneider.
+ */
+#define FTDI_TERATRONIK_VCP_PID 0xEC88 /* Teratronik device (preferring VCP driver on windows) */
+#define FTDI_TERATRONIK_D2XX_PID 0xEC89 /* Teratronik device (preferring D2XX driver on windows) */
+
+/*
* Evolution Robotics products (http://www.evolution.com/).
* Submitted by Shawn M. Lavelle.
*/
Re: [linux-usb-devel] Re: 2.6.15-rc5-mm1
On Tuesday 13 December 2005 7:35 am, Alan Stern wrote: On Tue, 13 Dec 2005, J.A. Magallon wrote: PCI: cache line size of 128 is not supported by device :00:1d.7 I don't think that matters. It's more informational than a warning. I don't even know why the PCI layer thinks we need to know about it. Probably that came out as a side effect of noticing that the PCI Memory-Write-Invalidate (MWI) cycle support can't be enabled; it's an optional performance optimization, not widely supported for USB. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ 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] Re: question for add multi-serial port to usb serial driver
On 13/12/05 09:35, tong changda wrote: I see qualcomm's inf file that has this %xxx% = QportInstall6k, SB\VID_1234PID_MI_01 %xxx% = QportInstallNMEA, USB\VID_1234PID_MI_02 xxx% = QportInstalltest, USB\VID_1234PID_MI_00 all this three has same VIDPID, diff only on MI.what does MI means? It seems that host locate driver not only throught vidpid, what is the rule, i can't find it in specification. Some info on Windows USB identifiers for the curious: http://www.osronline.com/ddkx/install/idstrings_01d3.htm The MI_xx part matches against the bInterfaceNumber of the interface descriptor for a composite device. It allows Windows to perform a separate hardware device installation for each interface of the composite device. -- -=( Ian Abbott @ MEV Ltd.E-mail: [EMAIL PROTECTED])=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=- --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ 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] Logging file transfers
Am Dienstag, 13. Dezember 2005 16:28 schrieb gary clark: Hello, I want to be able to log file transfers from a PC to USB storage devices? Can this be achieved in user space or will I have to patch the kernel usb storage That calls for ptrace. At the storage driver's level all knowledge of files is lost. It deals in blocks only. Monitoring there is a bad idea. Regards Oliver --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ 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] Strange USB2 hub behavior
I wouldn't have thought much of this and attributed it to a hub dying, but I've had _two_ USB2 hubs stop working on me in the last week. One was at work, and one at home. I booted into Windows and at least the one at home seems to be fine. The same issue appears with another plain USB2 disk that I have. The symptoms are that the devices behind the hub stop functioning, the hub which has a power light blinks fast, and I get a bunch of new device messages in dmesg, like this: usb 4-4: device descriptor read/64, error -71 usb 4-4: new high speed USB device using ehci_hcd and address 59 usb 4-4: new high speed USB device using ehci_hcd and address 60 usb 4-4: new high speed USB device using ehci_hcd and address 68 usb 4-4: new high speed USB device using ehci_hcd and address 69 usb 4-4: new high speed USB device using ehci_hcd and address 75 usb 4-4: device descriptor read/64, error -71 usb 4-4: new high speed USB device using ehci_hcd and address 77 usb 4-4: new high speed USB device using ehci_hcd and address 81 usb 4-4: new high speed USB device using ehci_hcd and address 83 usb 4-4: new high speed USB device using ehci_hcd and address 93 usb 4-4: new high speed USB device using ehci_hcd and address 98 usb 4-4: new high speed USB device using ehci_hcd and address 102 usb 4-4: new high speed USB device using ehci_hcd and address 103 usb 4-4: new high speed USB device using ehci_hcd and address 105 usb 4-4: new high speed USB device using ehci_hcd and address 106 usb 4-4: new high speed USB device using ehci_hcd and address 112 Although I'm running a two-day-old git snapshot, it isn't a recent kernel issue, because I've booted as far back as 2.6.12.5 and see the same behavior. I did recently get a new (refurbished) Thinkpad to replace a broken one, so I am willing to blame a crappy Thinkpad. But, the fact that it works in Windows makes me wonder if it is a Linux bug. The hub also seems to work fine if I plug it in behind an old USB 1 hub that I have. Any ideas? -- Dave --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ 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] Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes
On Tuesday, 13 December 2005 07:52, David Brownell wrote:
if ((status STS_PCD) device_may_wakeup(hcd-self.root_hub-dev)) {
What happens if you make that line read
if ((status STS_PCD) != 0) {
and ignore the root hub thing?
So far, so good. It works and hasn't triggered the oops yet. I'll report if
there's
anything wrong with it.
Greetings,
Rafael
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
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] Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes
On Tuesday 13 December 2005 2:10 pm, Rafael J. Wysocki wrote:
On Tuesday, 13 December 2005 07:52, David Brownell wrote:
if ((status STS_PCD) device_may_wakeup(hcd-self.root_hub-dev)) {
What happens if you make that line read
if ((status STS_PCD) != 0) {
and ignore the root hub thing?
So far, so good. It works and hasn't triggered the oops yet. I'll report if
there's
anything wrong with it.
I suspect that should be safe to merge for 2.6.15, and it might be
worth considering that. You were using kexec() right?
- Dave
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
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] Re: [-mm patch] drivers/usb/ip/: make functions static
On Mon, Dec 05, 2005 at 10:55:44PM +0100, Adrian Bunk wrote: This patch makes three needlessly global functions static. Applied, thanks. greg k-h --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ 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] usb storage errors 2.6.15-rc4
I've an USB storage key that gives these errors on my x86_64 system: usb 2-2: new full speed USB device using ohci_hcd and address 8 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS usb 2-2: default language 0x0409 usb 2-2: new device strings: Mfr=1, Product=2, SerialNumber=3 usb 2-2: Product: USB Flash Memory usb 2-2: SerialNumber: 08012A4001910630 usb 2-2: hotplug usb 2-2: adding 2-2:1.0 (config #1, interface 0) usb 2-2:1.0: hotplug usb-storage 2-2:1.0: usb_probe_interface usb-storage 2-2:1.0: usb_probe_interface - got id scsi2 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 8 usb-storage: waiting for device to settle before scanning drivers/usb/core/inode.c: creating file '008' hub 2-0:1.0: state 5 ports 3 chg evt 0004 Vendor: Model: USB Flash Memory Rev: 1.00 Type: Direct-Access ANSI SCSI revision: 00 SCSI device sda: 246272 512-byte hdwr sectors (126 MB) ohci_hcd :01:00.1: urb 810048c12240 path 2 ep1in 9312 cc 9 -- status -121 sda: Write Protect is off sda: Mode Sense: 23 00 00 00 sda: assuming drive cache: write through SCSI device sda: 246272 512-byte hdwr sectors (126 MB) ohci_hcd :01:00.1: urb 810048c12240 path 2 ep1in 9212 cc 9 -- status -121 sda: Write Protect is off sda: Mode Sense: 23 00 00 00 sda: assuming drive cache: write through sda: sda1 sd 2:0:0:0: Attached scsi removable disk sda sd 2:0:0:0: Attached scsi generic sg0 type 0 usb-storage: device scan complete ohci_hcd :01:00.1: urb 810022377d40 path 2 ep2out 5fce cc 5 -- status -110 hub 2-0:1.0: state 5 ports 3 chg evt 0004 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS usb 2-2: reset full speed USB device using ohci_hcd and address 8 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS ohci_hcd :01:00.1: urb 810022377d40 path 2 ep2out 5fce cc 5 -- status -110 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS usb 2-2: reset full speed USB device using ohci_hcd and address 8 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS ohci_hcd :01:00.1: urb 810022377d40 path 2 ep2out 5fce cc 5 -- status -110 hub 2-0:1.0: state 5 ports 3 chg evt 0004 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS usb 2-2: reset full speed USB device using ohci_hcd and address 8 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS hub 2-0:1.0: state 5 ports 3 chg evt 0004 ohci_hcd :01:00.1: urb 810022377d40 path 2 ep2out 5fce cc 5 -- status -110 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS hub 2-0:1.0: state 5 ports 3 chg evt 0004 usb 2-2: reset full speed USB device using ohci_hcd and address 8 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS ohci_hcd :01:00.1: urb 810022377d40 path 2 ep2out 5fce cc 5 -- status -110 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS usb 2-2: reset full speed USB device using ohci_hcd and address 8 hub 2-0:1.0: state 5 ports 3 chg evt 0004 [..] ohci_hcd :01:00.1: urb 81005467a080 path 2 ep2out 5fce cc 5 -- status -110 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS usb 2-2: reset full speed USB device using ohci_hcd and address 8 hub 2-0:1.0: state 5 ports 3 chg evt 0004 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS ohci_hcd :01:00.1: urb 81005467a080 path 2 ep2out 5fce cc 5 -- status -110 hub 2-0:1.0: state 5 ports 3 chg evt 0004 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS usb 2-2: reset full speed USB device using ohci_hcd and address 8 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS hub 2-0:1.0: state 5 ports 3 chg evt 0004 ohci_hcd :01:00.1: urb 81005467a080 path 2 ep2out 5fce cc 5 -- status -110 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS usb 2-2: reset full speed USB device using ohci_hcd and address 8 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS ohci_hcd :01:00.1: urb 81005467a080 path 2 ep2out 5fce cc 5 -- status -110 hub 2-0:1.0: state 5 ports 3 chg evt 0004 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS usb 2-2: reset full speed USB device using ohci_hcd and address 8 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS hub 2-0:1.0: state 5 ports 3 chg evt 0004 ohci_hcd :01:00.1: urb 81005467a080 path 2 ep2out 5fce cc 5 -- status -110 ohci_hcd :01:00.1: GetStatus
Re: [linux-usb-devel] Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes
On Tuesday, 13 December 2005 23:22, David Brownell wrote:
On Tuesday 13 December 2005 2:10 pm, Rafael J. Wysocki wrote:
On Tuesday, 13 December 2005 07:52, David Brownell wrote:
if ((status STS_PCD)
device_may_wakeup(hcd-self.root_hub-dev)) {
What happens if you make that line read
if ((status STS_PCD) != 0) {
and ignore the root hub thing?
So far, so good. It works and hasn't triggered the oops yet. I'll report
if there's
anything wrong with it.
I suspect that should be safe to merge for 2.6.15, and it might be
worth considering that. You were using kexec() right?
No, I was not. Why would that be important?
Rafael
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
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] usb storage errors 2.6.15-rc4
On Tue, 13 Dec 2005 23:34:37 +0100, Andrea Arcangeli [EMAIL PROTECTED] wrote: ohci_hcd :01:00.1: urb 810022377d40 path 2 ep2out 5fce cc 5 -- status -110 hub 2-0:1.0: state 5 ports 3 chg evt 0004 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS usb 2-2: reset full speed USB device using ohci_hcd and address 8 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS The device times out transfers and the SCSI EH asks usb-storage to abort the stuck command. In such case, usb-storage resets the device. I do not see anything extraordinary here, execept that we seem to have a verbosity creep in the USB stack again. Why would anyone want to print results of every GetStatus? Cheesh. -- Pete --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ 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] usb storage errors 2.6.15-rc4
On Tue, Dec 13, 2005 at 03:02:15PM -0800, Pete Zaitcev wrote: On Tue, 13 Dec 2005 23:34:37 +0100, Andrea Arcangeli [EMAIL PROTECTED] wrote: ohci_hcd :01:00.1: urb 810022377d40 path 2 ep2out 5fce cc 5 -- status -110 hub 2-0:1.0: state 5 ports 3 chg evt 0004 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS usb 2-2: reset full speed USB device using ohci_hcd and address 8 ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS The device times out transfers and the SCSI EH asks usb-storage to abort the stuck command. In such case, usb-storage resets the device. I do not see anything extraordinary here, execept that we seem to have a verbosity So you think it's an hardware problem. creep in the USB stack again. Why would anyone want to print results of every GetStatus? Cheesh. I compiled with CONFIG_USB_DEBUG=y if that matters. Thanks. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ 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] Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes
if ((status STS_PCD)
device_may_wakeup(hcd-self.root_hub-dev)) {
What happens if you make that line read
if ((status STS_PCD) != 0) {
and ignore the root hub thing?
So far, so good. It works and hasn't triggered the oops yet. I'll
report if there's
anything wrong with it.
I suspect that should be safe to merge for 2.6.15, and it might be
worth considering that. You were using kexec() right?
No, I was not. Why would that be important?
Just trying to keep the symptoms straight, that's all.
- Dave
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
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] /sys/module/g_ether/parameters oops
David Brownell wrote:
On Monday 12 December 2005 10:48 pm, Aras Vaichas wrote:
Hi,
I was poking around /sys and I noticed that g_ether gave an oops if I tried to
look at its parameters. g_serial seems to work OK, as do most of the other
modules that I checked.
Does anyone else have this problem?
Either the parameters should be given mode 0 so they don't show
up in the filesystem (preferable fix!) or else they shouldn't be
getting marked as __init ... please submit a patch if you have time!
I wanted to be able to see some of this information in /sys so I've chosen the
remove __initdata option.
This patch also includes adding the serial number parameter to the module.
The one drawback with this driver is that the dev_addr and host_addr don't show
up in /sys if they weren't specified, even though they are randomly chosen by
the driver itself.
regards,
Aras Vaichas
--- linux/drivers/usb/gadget/ether.c.orig 2005-11-29 14:15:04.0
+1100
+++ linux/drivers/usb/gadget/ether.c2005-12-14 11:19:43.0 +1100
@@ -182,33 +182,37 @@ struct eth_dev {
* parameters are in UTF-8 (superset of ASCII's 7 bit characters).
*/
-static ushort __initdata idVendor;
+static ushort idVendor;
module_param(idVendor, ushort, S_IRUGO);
MODULE_PARM_DESC(idVendor, USB Vendor ID);
-static ushort __initdata idProduct;
+static ushort idProduct;
module_param(idProduct, ushort, S_IRUGO);
MODULE_PARM_DESC(idProduct, USB Product ID);
-static ushort __initdata bcdDevice;
+static ushort bcdDevice;
module_param(bcdDevice, ushort, S_IRUGO);
MODULE_PARM_DESC(bcdDevice, USB Device version (BCD));
-static char *__initdata iManufacturer;
+static char *iManufacturer;
module_param(iManufacturer, charp, S_IRUGO);
MODULE_PARM_DESC(iManufacturer, USB Manufacturer string);
-static char *__initdata iProduct;
+static char *iProduct;
module_param(iProduct, charp, S_IRUGO);
MODULE_PARM_DESC(iProduct, USB Product string);
+static char *iSerialNumber;
+module_param(iSerialNumber, charp, S_IRUGO);
+MODULE_PARM_DESC(iSerialNumber, SerialNumber);
+
/* initial value, changed by ifconfig usb0 hw ether xx:xx:xx:xx:xx:xx */
-static char *__initdata dev_addr;
+static char *dev_addr;
module_param(dev_addr, charp, S_IRUGO);
MODULE_PARM_DESC(dev_addr, Device Ethernet Address);
/* this address is invisible to ifconfig */
-static char *__initdata host_addr;
+static char *host_addr;
module_param(host_addr, charp, S_IRUGO);
MODULE_PARM_DESC(host_addr, Host Ethernet Address);
@@ -395,6 +399,7 @@ static inline int BITRATE(struct usb_gad
#define STRING_CDC 7
#define STRING_SUBSET 8
#define STRING_RNDIS 9
+#define STRING_SERIALNUMBER10
/* holds our biggest descriptor (or RNDIS response) */
#define USB_BUFSIZ 256
@@ -428,6 +433,7 @@ device_desc = {
.idProduct =__constant_cpu_to_le16 (CDC_PRODUCT_NUM),
.iManufacturer =STRING_MANUFACTURER,
.iProduct = STRING_PRODUCT,
+ .iSerialNumber =STRING_SERIALNUMBER,
.bNumConfigurations = 1,
};
@@ -862,6 +868,7 @@ static inline void __init hs_subset_desc
static charmanufacturer [50];
static charproduct_desc [40] = DRIVER_DESC;
+static charserial_number [13];
#ifdef DEV_CONFIG_CDC
/* address that the host will use ... usually assigned at random */
@@ -873,6 +880,7 @@ static struct usb_stringstrings [] = {
{ STRING_MANUFACTURER, manufacturer, },
{ STRING_PRODUCT, product_desc, },
{ STRING_DATA, Ethernet Data, },
+ { STRING_SERIALNUMBER, serial_number, },
#ifdef DEV_CONFIG_CDC
{ STRING_CDC, CDC Ethernet, },
{ STRING_ETHADDR, ethaddr, },
@@ -2268,6 +2276,8 @@ eth_bind (struct usb_gadget *gadget)
strlcpy (manufacturer, iManufacturer, sizeof manufacturer);
if (iProduct)
strlcpy (product_desc, iProduct, sizeof product_desc);
+ if (iSerialNumber)
+ strlcpy (serial_number, iSerialNumber, sizeof serial_number);
/* all we really need is bulk IN/OUT */
usb_ep_autoconfig_reset (gadget);
[linux-usb-devel] ~surprise remove problem~
Dear all: I am doing porting task for our company wireless NIC driver from 2.4.x to 2.6.x. I got a problem about the surprise remove after loading driver successfully. The system was crashed and halted, when plug out the NIC without typing rmmod xxx. However, if plugging out NIC after typing rmmod xxx . It was ok. On the hand, I also tried to mark the code of interrupt endpoint to submit interrupt urb. The problem disappeared and I saw the system tried to call disconnect function in our driver. Therefore, I doubt the USB core doesn't support surprise remove for interrupt endpoint. Can any one give me any suggestion or advice to solve this problem? Best regards, Wei-Shun Liao ===The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email irrelevant to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond. ===If your computer is unable to decode Chinese font, please ignore the following message.It essentially repeats the statement in English given above.¥»«H¥ó¤º©Ò§tµØ¨¹¹q¤lªº°]²£©Ê¾÷±K©Ê¸ê°T, ¶È±ÂÅvìµo«H¤H«ü©w¤§¦¬«H¤H¨ú¾\\¤§¥Î. °²¨Ï±z¨Ã«D³Q«ü©w¤§¦¬«H¤H©Î¦]¥ô¦óì¦]¦b¥¼¸g±ÂÅvªº±¡§Î¤§¤U¦¬¨ì¥»«H¥ó, ½Ð±z§iª¾ìµo«H¤H¨Ã¥ß§Y±N«H¥ó±q¹q¸£»Pºô¸ô¦øªA¾¹¤¤¤©¥H®ø°£. ¹ï©ó±zªº¦X§@, §ÚÌ¥ý¦¹PÁÂ. ¯S¦¹´£¿ô, ¥ô¦ó¥¼¸g±ÂÅv¾Õ¦Û¨Ï¥ÎµØ¨¹¹q¤lªº¾÷±K¸ê°Tªº¦æ¬°¬O³QÄY®æ¸T¤îªº. «H¥ó»PµØ¨¹¹q¤lÀç·~µLÃö¤§¤º®e,¤£±oµø¬°µØ¨¹¹q¤l¤§¥ß³õ©Î·N¨£. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37alloc_id865op=click ___ 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] usblp suspend failure with 2.6.15-rc5
Alan, I'm starting to get some complaints about this issue (almost no
usb drivers have a suspend/resume function, nor should they be required
to.)
Mind if I add the patch below to the tree?
thanks,
greg k-h
On Wed, Dec 07, 2005 at 11:30:48AM -0500, Alan Stern wrote:
Darn it. There were two problem pathways in that code and the patch
changed the wrong one. Okay, this patch changes both.
Bear in mind that this is just a temporary band-aid. The real problem is
that the usblp driver doesn't have any suspend/resume support. That still
needs to be fixed.
If you don't feel like using the patch below, you can simply rmmod usblp
before suspending and modprobe usblp after resuming. That's actually a
safer approach.
Alan Stern
Index: linux-2.6.15-rc3/drivers/usb/core/usb.c
===
--- linux-2.6.15-rc3.orig/drivers/usb/core/usb.c
+++ linux-2.6.15-rc3/drivers/usb/core/usb.c
@@ -1414,8 +1414,10 @@ static int usb_generic_suspend(struct de
}
if ((dev-driver == NULL) ||
- (dev-driver_data == usb_generic_driver_data))
+ (dev-driver_data == usb_generic_driver_data)) {
+ dev-power.power_state.event = PM_EVENT_FREEZE;
return 0;
+ }
intf = to_usb_interface(dev);
driver = to_usb_driver(dev-driver);
@@ -1433,6 +1435,7 @@ static int usb_generic_suspend(struct de
} else {
// FIXME else if there's no suspend method, disconnect...
dev_warn(dev, no %s?\n, suspend);
+ mark_quiesced(intf);
status = 0;
}
return status;
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
--
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
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] usblp suspend failure with 2.6.15-rc5
On Wednesday 14 December 2005 01:10, Greg KH wrote: Alan, I'm starting to get some complaints about this issue (almost no usb drivers have a suspend/resume function, nor should they be required to.) Greg, Will you object to adding suspend/resume support to individual USB drivers? Relying on disconnect/rediscovery at resume does not work well for input devices... Now if X could dynamically add input devices we would not care, but unfortunately we need to keep the same device node if possible. -- Dmitry --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ 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] usblp suspend failure with 2.6.15-rc5
On Wed, Dec 14, 2005 at 02:10:22AM -0500, Dmitry Torokhov wrote: On Wednesday 14 December 2005 01:10, Greg KH wrote: Alan, I'm starting to get some complaints about this issue (almost no usb drivers have a suspend/resume function, nor should they be required to.) Greg, Will you object to adding suspend/resume support to individual USB drivers? No, not at all, some of them will need it. I just object to stopping the whole suspend cycle if one USB driver that is bound to a device doesn't have a suspend function. That's not nice, and is causing my inbox to fill up :) thanks, greg k-h --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
