Re: [linux-usb-devel] Re: problem reloading ohci-isp1160
Hi, Guys, the following story is specific to LH7A400 SoC. Yeah, it does. A 1 micro-second delay should do it, right? I've also run into trouble with how picky the chip is. For instance, the chip select and read signal must be deasserted between reads. (see Fig. 31, pg 137 of the ISP1362 manual) If I just don't write, it sometimes leaves chip-select asserted. So, I can write to another chip select in the mean-time to force it to change. Mike, I finally got an opportunity to attach a logic analyzer to the system bus and look at the behavior of CS, OE, and WE signals. I learned the following. 1. The (almost) optimal timing in my board is, when I configure the static memory controller's IDCY field to max (0xf) and add udelay(1) only into HC_ISP1362_WRITE_ADDR. However, with this setting I see that CS indeed remains active for several subsequent reads/writes. An access to another memory range relieves that problem. 2. If there is udelay(1) after every register access then the problem of CS remaining active between register accesses is gone (well, I haven't seen it). 3. The CS and OE signals on LH7A400 behave an unexpected way. Namely, while CS is asserted about 5ns before OE is asserted, the CS is also deasserted about 5ns before OE is deasserted. I.e., these signals remain active for the same amount of time, but just CS makes its cycle 5ns earlier than OE. This phenomenon is independent of the WST1 setting in BCR register. The datasheet of isp1160 says that OE may be deasserted before or together with CS. I have no idea, whether this can affect the behavior of the chip. Perhaps only somebody in Philips knows. The WE signal works as expected. It is asserted together with CS and deasserted 10ns before CS is deasserted. Olav --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] A Problem in USB device driver development
Am Donnerstag, 18. November 2004 04:11 schrieb DMR: Hi, I have a problem in usb device driver development. After USB device was reset by static electricity etc., device pointer from USB core driver is NULL. What? How? A device resetting itself is certainly a problem, but how does the host notice? The device would just take adress 0 and logically vanish from the bus. Regards Oliver --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] iomega usb key problem
Hello, I'm using kernel 2.6.9 I need to remove usbstorage module and sd_mod before plugging my key. If I don't do that, i see in my logs creation of /dev/sda and /dev/sg0 but the kernel does not create /dev/sda1. I give you my logs (with usbstorage debug mode). PS : please answer me directly as I'm not a linux-usb-devel list user Thanks ! Yannick Beynet. blade:/proc/bus/usb# cat devices T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 5 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 2.06 S: Manufacturer=Linux 2.6.9 ehci_hcd S: Product=NEC Corporation USB 2.0 S: SerialNumber=:02:04.2 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 2.06 S: Manufacturer=Linux 2.6.9 uhci_hcd S: Product=Intel Corp. 82801BA/BAM USB (Hub #2) S: SerialNumber=:00:1f.4 C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 93/900 us (10%), #Int= 1, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 2.06 S: Manufacturer=Linux 2.6.9 uhci_hcd S: Product=Intel Corp. 82801BA/BAM USB (Hub #1) S: SerialNumber=:00:1f.2 C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=045e ProdID=0040 Rev= 1.21 S: Manufacturer=Microsoft S: Product=Microsoft Wheel Mouse Optical® C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=10ms T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 14 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=08ec ProdID=0011 Rev= 2.00 S: Manufacturer=I0MEGA S: Product=Minidrive 128 S: SerialNumber=020283163800D225 C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 94mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms syslog.sv Description: Binary data
Re: [linux-usb-devel] Dell Axim x30 doesn't want stay connected..
On Tue, 2004-11-16 at 19:52, Thomas Davis wrote: Yes, I finally figured it out several weeks ago. Good! The USB idents for Dell's Axim x30, x30, and x50 do not match what's in the kernel. I hope you found out how to work around that, otherwise see the HOWTO. Does anyone update the ipaq module anymore? Not really, but only a few days ago I submitted a patch with all USB vendor/product IDs that Microsoft supports in ActiveSync 3.7.1. I will probably also submit other patches in the future... \David thomas David Eriksson wrote: Thomas, I noticed your post in the linux-usb-devel mailing list archive... Load the ipaq serial driver, plug the dell axim x30 in, and you get: [snip] Under 2.6.8.1, it gives an device not accepting address #, error -71 Until you unplug it. This is 2.6.8.1-mm3; I have tried it with a 2.4.2x kernel, same \ sorta thing, it complains; it works fine in Win2k. So what debug options do I need to turn on to figure out what it's doing? The ipaq driver alone is not enough to make use of your PDA, please follow the instructions on this page at the SynCE project's web site: http://synce.sourceforge.net/synce/howto.php -- Regards, -\- David Eriksson -/- SynCE - http://synce.sourceforge.net ScummVM - http://scummvm.sourceforge.net Desquirr - http://desquirr.sourceforge.net --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Re: PATCH: ftdi_sio doesn't re-assert DTR modem control line
On Friday 25 June 2004 21:56, Croy, Nathan wrote:
SUMMARY
===
ftdi_sio never reasserts modem control lines once the baud has been
set to B0.
DESCRIPTION
===
Setting the baud to B0 (hangup) drops DTR. When the baud is raised
again, DTR is not raised. This can cause a modem to ignore any
commands sent to it until the device is closed and reopened. This
renders minicom (and other software) useless, unless you instruct the
modem to ignore DTR.
The following patch is intended to make ftdi_sio act like other
serial devices I have used (i.e. the standard serial ports
(/dev/ttyS*) and stallion ports (/dev/ttyE*)). Upon setting the baud
to something other than B0, it ensures the modem control lines are
set back to the way they were when the port was opened.
Thanks to Ian Abbott for confirming my suspicions:
http://sourceforge.net/mailarchive/forum.php?thread_id=4984710forum_id=12120
Nathan's email suffered from a line-folding bug (blame M$, probably!),
so his patch came out corrupted. I reposted an uncorrupted version a
few days later. It showed up in 2.6.9, but not in 2.4.28, so I'm
resubmitting the patch against 2.4.28.
Please apply to 2.4, thanks.
Signed off by: Ian Abbott [EMAIL PROTECTED]
diff -ur linux-2.4.28/drivers/usb/serial/ftdi_sio.c
linux-2.4.28-ia/drivers/usb/serial/ftdi_sio.c
--- linux-2.4.28/drivers/usb/serial/ftdi_sio.c 2004-08-08 00:26:05.0
+0100
+++ linux-2.4.28-ia/drivers/usb/serial/ftdi_sio.c 2004-11-18 13:37:00.512114760
+
@@ -1857,6 +1857,13 @@
if (change_speed(port)) {
err(%s urb failed to set baurdrate, __FUNCTION__);
}
+ /* Ensure RTS and DTR are raised */
+ else if (set_dtr(port, HIGH) 0){
+ err(%s Error from DTR HIGH urb, __FUNCTION__);
+ }
+ else if (set_rts(port, HIGH) 0){
+ err(%s Error from RTS HIGH urb, __FUNCTION__);
+ }
}
/* Set flow control */
---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] RE: yet more on ohci-isp1362
Hi Lothar, I added a patch to the download area at http://www.karo-electronics.de/support-public.html that reflects my latest changes that hopefully will help you to get things working. Unfortunately I'm working on something completely different now, so that I can't invest much time in this driver right now. :( Thanks for the updated driver. Until now I have made my 116x specific modifications so that they apply on top of your driver without affecting the 1362-specific stuff. Yes, there are quite some #ifdefs there, but still there is far more common code than chip specific stuff. I looked at your new patch and saw that you have removed the isp116x stuff from the ohci-isp1362.h file. Does this mean that you prefer to keep the 1362 driver separate or would you still consider adding the 116x support if I am able to provide it as a cleaned up patch one day? I would of course make the 116x patch apply to your then latest driver version. Olav --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] usb-storage crashes on 2.6.10-rc2 (SMP) in a NEW and INTERESTING way
On Wednesday 17 November 2004 16:04, Christian Iversen wrote: However, the world is not trouble-free yet, as linux still crashes in certain situations on 2.6.10-rc2 with SMP systems. (UP systems are fine). The new bug is http://bugme.osdl.org/show_bug.cgi?id=3761, which I marked as blocking because it's just too easy to bring the whole system down. ... usb 4-2: USB disconnect, address 2 usb 4-2.3: USB disconnect, address 5 target5:0:0: Illegal state transition NULL-cancel Badness in scsi_device_set_state at drivers/scsi/scsi_lib.c:1717 [b0324d16] scsi_device_set_state+0xc6/0x130 ... This one's a SCSI bug, not a USB one, according to previous diagnosis. --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] usb-storage crashes on 2.6.10-rc2 (SMP) in a NEW and INTERESTING way
On Thursday 18 November 2004 16:45, David Brownell wrote: On Wednesday 17 November 2004 16:04, Christian Iversen wrote: However, the world is not trouble-free yet, as linux still crashes in certain situations on 2.6.10-rc2 with SMP systems. (UP systems are fine). The new bug is http://bugme.osdl.org/show_bug.cgi?id=3761, which I marked as blocking because it's just too easy to bring the whole system down. ... usb 4-2: USB disconnect, address 2 usb 4-2.3: USB disconnect, address 5 target5:0:0: Illegal state transition NULL-cancel Badness in scsi_device_set_state at drivers/scsi/scsi_lib.c:1717 [b0324d16] scsi_device_set_state+0xc6/0x130 ... This one's a SCSI bug, not a USB one, according to previous diagnosis. Oops, my bad. Although, it can't be entirely a SCSI bug, can it? The USB subsystem loses the high-speed connection and drops back to 1.1 speed. Or is that perhaps because the SCSI subsystem coughed and died? ..and if it's a SCSI bug, how can I A) Move it to the SCSI-section on bugme.osdl.org? B) Tell the right people? -- Regards, Christian Iversen --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] RE: yet more on ohci-isp1362
Hi Olav, Until now I have made my 116x specific modifications so that they apply on top of your driver without affecting the 1362-specific stuff. Yes, there are quite some #ifdefs there, but still there is far more common code than chip specific stuff. I looked at your new patch and saw that you have removed the isp116x stuff from the ohci-isp1362.h file. I didn't specifically remove it. The version I put on the website is what is currently working for our customer, so it doesn't contain your patches yet. Since I'm working on a different project now, I still didn't have the time to incorporate your patches into the code. :( Does this mean that you prefer to keep the 1362 driver separate or would you still consider adding the 116x support if I am able to provide it as a cleaned up patch one day? I would of course make the 116x patch apply to your then latest driver version. Yes, I'd like to get your patch. I hope to find some time in between projects to merge it with my code. Lothar Wassmann --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] RE: yet more on ohci-isp1362
Does this mean that you prefer to keep the 1362 driver separate or would you still consider adding the 116x support if I am able to provide it as a cleaned up patch one day? I would of course make the 116x patch apply to your then latest driver version. Yes, I'd like to get your patch. I hope to find some time in between projects to merge it with my code. Great. It will take still some time to get the patch ready, but I will let you know. Olav --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
RE: [linux-usb-devel] HC gets too little data from devices
Hi Philipp, your problem does not seem to appear with my setup. In my case I am getting the full 34 bytes of configuration. I am not sure why, but for this particular test run, it skipped the set address (may have been set before starting driver, before resetting the board - ?). I will send you my output log, so you can compare any differences, off the list or to anyone else that wants it. In this case I had my Logitech Optical Mouse M-BJ58 connected. Indeed, from your log file I see that you get these particular 34 bytes completely. But if you look at your log file line 610 then you see that instead of requested 52 bytes you get only 32. Olav --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Linux support for SiLabs CP2102 devices
Hi all, I've been getting a lot of requests lately to see if Linux supports the USB to serial device from Silicon Laboratories called the CP2102 chip. It turns out that the company is claiming Linux support, yet they are only shipping a binary driver for Red Hat Linux 9.0. In talking with the company, they insist that they will not release the source code to this module, and they claim that they are not infringing on any rights by not doing so. I claim that this is not true, as to write a usb to serial driver for Linux you have to use the drivers/usb/serial/usb-serial.h header file which is specifically licensed under the GPL v2. This file contains inline functions and structures that all usb-serial drivers need to use in order to work properly. In short, there's no way you can write a Linux usb-serial driver, that uses the usbserial interface, without it being a derived work of other, GPL only code. So, they are in violation, so what. Well, I can't do much about this (due to my employer's rules about suing companies). But I can do my best to spread the word that the CP2102 device is not supported on Linux, and should be avoided at all costs by anyone considering such a device in a future design. I encourage everyone else to help spread this information too. If people are looking for a good usb to serial chip that is supported on Linux, Windows, and OS-X, there's the PL2303 device from Prolific, and the FTDI-SIO chip, and the MCT-U232 chip. All of these work very well on Linux, and are fully supported by all distros. I think they even might be cheaper than the CP2102 device too :) Oh, and just for fun, attached to this message is the Linux driver that SiLabs is distributing, if anyone wants to poke around in it. The tarball contains 2 binary drivers, one of them a version of the usbserial.c file (which plainly is licensed under the GPL) and a mcci_usb.o binary driver. Have fun with it, but don't blame me for any badness that might happen to your box for running it, no one has any way of knowing exactly what this driver is doing. So, in conclusion, please stay away from Silicon Laboratories devices, if you want to run Linux, as they are obviously not supporting Linux in any way. thanks, greg k-h cardinal-redhat9-V0_81b.tar.gz Description: application/tar-gz
Re: [linux-usb-devel] usb-storage crashes on 2.6.10-rc2 (SMP) in a NEW and INTERESTING way
On Thu, 18 Nov 2004 01:04:48 +0100, Christian Iversen [EMAIL PROTECTED] wrote:
http://bugme.osdl.org/show_bug.cgi?id=3728, which has now been fixed.
However, the world is not trouble-free yet, as linux still crashes in certain
situations on 2.6.10-rc2 with SMP systems. (UP systems are fine).
Ah, 2.6.10-rc2. Thanks for posting the precise version. I am so tired of
people who write latest or current. Please try this patch by Mike Christie:
--- scsi-target-2.6/drivers/scsi/hosts.c2004-10-09 07:56:54.363746835
-0700
+++ scsi-target-2.6.work/drivers/scsi/hosts.c 2004-10-09 07:49:21.287638490
-0700
@@ -55,6 +55,12 @@
return scsi_device_cancel(to_scsi_device(dev), *(int *)data);
}
+static int scsi_target_cancel_cb(struct device *dev, void *data)
+{
+ device_for_each_child(dev, data, scsi_device_cancel_cb);
+ return 0;
+}
+
/**
* scsi_host_cancel - cancel outstanding IO to this host
* @shost: pointer to struct Scsi_Host
@@ -64,7 +70,7 @@
{
set_bit(SHOST_CANCEL, shost-shost_state);
device_for_each_child(shost-shost_gendev, recovery,
- scsi_device_cancel_cb);
+ scsi_target_cancel_cb);
wait_event(shost-host_wait, (!test_bit(SHOST_RECOVERY,
shost-shost_state)));
}
-- Pete
---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Request for confirmation
Almost welcome to our mailinglist(s) ... Someone, hopefully you, has subscribed your email address to the following mailinglists: * adhost list If this is correct, please click this URL to confirm your subscription: http://adhost.gr/list/?p=confirmuid=fb54e9b8e0a23a8adfd09f5447ee64b0 If this is not correct, you do not need to do anything, simply delete this message. Thank you --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Linux support for SiLabs CP2102 devices
On Thursday 18 November 2004 12:39pm, Greg KH wrote: Hi all, I've been getting a lot of requests lately to see if Linux supports the USB to serial device from Silicon Laboratories called the CP2102 chip. It turns out that the company is claiming Linux support, yet they are only shipping a binary driver for Red Hat Linux 9.0. In talking with the company, they insist that they will not release the source code to this module, and they claim that they are not infringing on any rights by not doing so. (... snip ...) So, they are in violation, so what. Well, I can't do much about this (due to my employer's rules about suing companies). But I can do my best to spread the word that the CP2102 device is not supported on Linux, and should be avoided at all costs by anyone considering such a device in a future design. I encourage everyone else to help spread this information too. (... snip ...) So, in conclusion, please stay away from Silicon Laboratories devices, if you want to run Linux, as they are obviously not supporting Linux in any way. If anyone has the USB Vendor/Product IDs (VID/PID) for these errant devices, a negative report (maybe including a link back to Greg's post in the Linux-USB-Devel list archives [http:// marc.theaimsgroup.com/?l=linux-usb-develm=110079963113076w=2]) should be submitted to the USB 'Working Devices' list for RS-232/USB adapters at: http://www.qbik.ch/usb/devices/showdevcat.php?id=12 (I just did a search at that location for 'CP2102' and 'Silicon' and 'SiLabs' and found no entries for any such devices. I don't see any USB VID/PID info about them or their devices in the 'usb.ids' file either.) That might help keep future users away from the devices of a company with such a poorly-thought-out policy. Thank you, Greg, for alerting us to this situation. Bill Marr --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Re: PATCH: ftdi_sio doesn't re-assert DTR modem control line
On Thu, Nov 18, 2004 at 02:04:24PM +, Ian Abbott wrote: Nathan's email suffered from a line-folding bug (blame M$, probably!), so his patch came out corrupted. I reposted an uncorrupted version a few days later. It showed up in 2.6.9, but not in 2.4.28, so I'm resubmitting the patch against 2.4.28. Please apply to 2.4, thanks. The patch had the tabs eaten by your email client :( thanks, greg k-h --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] usb-storage crashes on 2.6.10-rc2 (SMP) in a NEW and INTERESTING way
On Thursday 18 November 2004 20:29, Pete Zaitcev wrote:
On Thu, 18 Nov 2004 01:04:48 +0100, Christian Iversen
[EMAIL PROTECTED] wrote:
http://bugme.osdl.org/show_bug.cgi?id=3728, which has now been fixed.
However, the world is not trouble-free yet, as linux still crashes in
certain situations on 2.6.10-rc2 with SMP systems. (UP systems are fine).
Ah, 2.6.10-rc2. Thanks for posting the precise version. I am so tired of
people who write latest or current.
No problem at all, everybody should do this.. ;-)
Please try this patch by Mike Christie:
--- scsi-target-2.6/drivers/scsi/hosts.c 2004-10-09 07:56:54.363746835
-0700 +++ scsi-target-2.6.work/drivers/scsi/hosts.c 2004-10-09
07:49:21.287638490 -0700 @@ -55,6 +55,12 @@
return scsi_device_cancel(to_scsi_device(dev), *(int *)data);
}
+static int scsi_target_cancel_cb(struct device *dev, void *data)
+{
+ device_for_each_child(dev, data, scsi_device_cancel_cb);
+ return 0;
+}
+
/**
* scsi_host_cancel - cancel outstanding IO to this host
* @shost: pointer to struct Scsi_Host
@@ -64,7 +70,7 @@
{
set_bit(SHOST_CANCEL, shost-shost_state);
device_for_each_child(shost-shost_gendev, recovery,
- scsi_device_cancel_cb);
+ scsi_target_cancel_cb);
wait_event(shost-host_wait, (!test_bit(SHOST_RECOVERY,
shost-shost_state)));
}
For some reason, I had to apply it by hand. Poor patch(1) got confused.
Problem with tab chars?
Anyhow, it works _perfectly_. Thank you so very much :-)
*party time*
If you read the bug-description, you will see some mention of low USB speeds.
This is an unrelated issue, which I'll post to the mailing list shortly.
--
Regards,
Christian Iversen
---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] usb-storage crashes on 2.6.10-rc2 (SMP) in a NEW and INTERESTING way
On Thu, 18 Nov 2004 01:04:48 +0100, Christian Iversen [EMAIL PROTECTED] wrote: The new bug is http://bugme.osdl.org/show_bug.cgi?id=3761, which I marked as blocking because it's just too easy to bring the whole system down. usb 4-2: USB disconnect, address 2 usb 4-2.3: USB disconnect, address 5 target5:0:0: Illegal state transition NULL-cancel Unfortunately, the patch I sent before was not correct. The SCSI folks work on a solution though, see this: http://marc.theaimsgroup.com/?l=linux-scsim=109886580930570w=2 -- Pete --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Re: 2.6.10-rc2-mm2 usb storage still oopses
Fabio Coatti [EMAIL PROTECTED] wrote: Just a reminder: it's possible to cause a kernel oops simply inserting and removing a usb storage (flash pen); using ub driver doesn't improve the situation; noticed in 2.6.9-rc4-mm1 and present in 2.6.10-rc2-mm2. The same device works just fine with 2.6.8.1 (mdk cooker) OK, that's something we'd like to get fixed prior to 2.6.10. I can provide, as previously done, full log for oopses and other details, just let me known. (the behaviour is quite the same as already reported, so I don't want to waste bandwidth) We waste truckloads of bandwidth on far less important things than this ;) Please resend the report, including the oops trace and be sure to cc both linux-kernel and linux-usb-devel, thanks. --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Problem with (at least) ALI USB 2.0 controller on 2.6.10-rc2
No kernel newer than 2.6.5 seems to work for my SMP box these days.. :-/
On Linux 2.6.10-rc2, my ALI USB controller no longer works properly.
Specifically, ehci connection are slow (not usb2.0 high-speed). It seems that
the kernel thinks that my controller has experienced a fatal error. The
following fix to line 858 of ehci-hcd.c gets past that:
change
if (unlikely ((status STS_FATAL) != 0)) {
to
if (0) {
Then, it more or less works, but you get tons of I/O errors when reading:
end_request: I/O error, dev sr0, sector 2712
Buffer I/O error on device sr0, logical block 339
end_request: I/O error, dev sr0, sector 2712
Buffer I/O error on device sr0, logical block 339
end_request: I/O error, dev sr0, sector 2712
Buffer I/O error on device sr0, logical block 339
end_request: I/O error, dev sr0, sector 2712
Buffer I/O error on device sr0, logical block 339
end_request: I/O error, dev sr0, sector 2712
Buffer I/O error on device sr0, logical block 339
end_request: I/O error, dev sr0, sector 2720
Buffer I/O error on device sr0, logical block 340
end_request: I/O error, dev sr0, sector 2720
On reconnecting devices I get strange warnings, like so:
usb 1-4: USB disconnect, address 2
usb 1-4.3: USB disconnect, address 6
usb 1-4.4: USB disconnect, address 5
usb 1-4: new high speed USB device using ehci_hcd and address 7
hub 1-4:1.0: USB hub found
hub 1-4:1.0: 4 ports detected
usb 1-4.3: new full speed USB device using ehci_hcd and address 8
usb 1-4.3: not running at top speed; connect to a high speed hub
scsi7 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 8
usb-storage: waiting for device to settle before scanning
usb 1-4.4: new full speed USB device using ehci_hcd and address 9
usb 1-4.4: not running at top speed; connect to a high speed hub
scsi8 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 9
usb-storage: waiting for device to settle before scanning
Vendor: PLEXTOR Model: DVDR PX-712ARev: 1.05
Type: CD-ROM ANSI SCSI revision: 00
sr0: scsi3-mmc drive: 15x/94x writer cd/rw xa/form2 cdda tray
Attached scsi CD-ROM sr0 at scsi7, channel 0, id 0, lun 0
Attached scsi generic sg11 at scsi7, channel 0, id 0, lun 0, type 5
usb-storage: device scan complete
Vendor: PLEXTOR Model: CD-R PX-W2410A Rev: 1.04
Type: CD-ROM ANSI SCSI revision: 00
sr1: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
Attached scsi CD-ROM sr1 at scsi8, channel 0, id 0, lun 0
Attached scsi generic sg12 at scsi8, channel 0, id 0, lun 0, type 5
usb-storage: device scan complete
cdrom: open failed.
cdrom: open failed.
end_request: I/O error, dev sr0, sector 2512
(on high-speed devices, hubs and controllers)
but no oops'es, crashes or lockups. Just a kernel that doesn't work work :-/
I feel I'm so very close to having solved the last problem with 2.6.10-rc2,
and I would really like to use it. Any suggestions?
-- ver_linux:
Linux boreas.iversen-net.dk 2.6.10-rc2-boreas #9 SMP Thu Nov 18 21:45:48 CET
2004 i686 GNU/Linux
Gnu C 3.3.4
Gnu make 3.80
binutils 2.15
util-linux 2.12
mount 2.12
module-init-tools 3.1-pre6
e2fsprogs 1.35
reiserfsprogs 3.6.19
reiser4progs line
xfsprogs 2.6.20
nfs-utils 1.0.6
Linux C Library2.3.2
Dynamic linker (ldd) 2.3.2
Procps 3.2.2
Net-tools 1.60
Console-tools 0.2.3
Sh-utils 5.2.1
Modules Loaded ns83820 psmouse prism54
--
Regards,
Christian Iversen
---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] usb-storage crashes on 2.6.10-rc2 (SMP) in a NEW and INTERESTING way
On Thursday 18 November 2004 22:01, Pete Zaitcev wrote: On Thu, 18 Nov 2004 01:04:48 +0100, Christian Iversen [EMAIL PROTECTED] wrote: The new bug is http://bugme.osdl.org/show_bug.cgi?id=3761, which I marked as blocking because it's just too easy to bring the whole system down. usb 4-2: USB disconnect, address 2 usb 4-2.3: USB disconnect, address 5 target5:0:0: Illegal state transition NULL-cancel Unfortunately, the patch I sent before was not correct. The SCSI folks work on a solution though, see this: http://marc.theaimsgroup.com/?l=linux-scsim=109886580930570w=2 I'm not sure why it helped then. I just posted to this list about some new and interesting problems I get when using the patch you sent. Could I be experiencing these problems _because_ of the patch, rather than in spite of it? -- Regards, Christian Iversen --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Re: 2.6.10-rc2-mm2 usb storage still oopses
On Thu, 18 Nov 2004 13:35:57 -0800, Andrew Morton [EMAIL PROTECTED] wrote:
Fabio Coatti [EMAIL PROTECTED] wrote:
Just a reminder: it's possible to cause a kernel oops simply inserting and
removing a usb storage (flash pen); using ub driver doesn't improve the
situation; noticed in 2.6.9-rc4-mm1 and present in 2.6.10-rc2-mm2.
The same device works just fine with 2.6.8.1 (mdk cooker)
OK, that's something we'd like to get fixed prior to 2.6.10.
Actually Fabio told me that his oops was fixed by the patch present in
2.6.10-rc2. The problem is that his device needs special handling which
I do not know how to provide, so it does not work in the end. I hope it
will resolve itself eventually, as I get testers.
There was one last oops from Martin Schleminger (Sahara) which I think
I fixed but I need a confirmation before pushing to Greg. Apparently, it
only happens on kernels with preempt enabled. If anyone knows of any other
problems, I'm all ears.
-- Pete
P.S. Current updates:
--- linux-2.6.10-rc2-usb/drivers/block/ub.c 2004-11-16 17:03:02.0
-0800
+++ linux-2.6.10-rc1-ub/drivers/block/ub.c 2004-11-07 19:01:03.0
-0800
@@ -36,7 +36,7 @@
#define DRV_NAME ub
#define DEVFS_NAME DRV_NAME
-#define UB_MAJOR 125 /* Stolen from Experimental range for a week - XXX */
+#define UB_MAJOR 180
/*
* Definitions which have to be scattered once we understand the layout better.
@@ -1535,8 +1535,11 @@
ub_revalidate(sc);
/* This is pretty much a long term P3 */
- printk(KERN_INFO %s: device %u capacity nsec %ld bsize %u\n,
- sc-name, sc-dev-devnum, sc-capacity.nsec, sc-capacity.bsize);
+ if (!atomic_read(sc-poison)) {/* Cover sc-dev */
+ printk(KERN_INFO %s: device %u capacity nsec %ld bsize %u\n,
+ sc-name, sc-dev-devnum,
+ sc-capacity.nsec, sc-capacity.bsize);
+ }
/* XXX Support sector size switching like in sr.c */
blk_queue_hardsect_size(disk-queue, sc-capacity.bsize);
---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Re: 2.6.10-rc2-mm2 usb storage still oopses
Alle 22:58, giovedì 18 novembre 2004, Pete Zaitcev ha scritto: On Thu, 18 Nov 2004 13:35:57 -0800, Andrew Morton [EMAIL PROTECTED] wrote: Fabio Coatti [EMAIL PROTECTED] wrote: Just a reminder: it's possible to cause a kernel oops simply inserting and removing a usb storage (flash pen); using ub driver doesn't improve the situation; noticed in 2.6.9-rc4-mm1 and present in 2.6.10-rc2-mm2. The same device works just fine with 2.6.8.1 (mdk cooker) OK, that's something we'd like to get fixed prior to 2.6.10. Actually Fabio told me that his oops was fixed by the patch present in 2.6.10-rc2. The problem is that his device needs special handling which I do not know how to provide, so it does not work in the end. I hope it will resolve itself eventually, as I get testers. There was one last oops from Martin Schleminger (Sahara) which I think I fixed but I need a confirmation before pushing to Greg. Apparently, it only happens on kernels with preempt enabled. If anyone knows of any other problems, I'm all ears. Well, that's the whole story: in fact using ub driver with your patch applied i can avoid oops (as said in this thread: http://marc.theaimsgroup.com/?l=linux-kernelm=109943374727804w=2) But the behaviour imho is still buggy and not related to ub driver; it sems that something goes wrong before ub; in fact I get almost the same behaviour without ub compiled in, scsi fails in the (quite) the same way, it seems that something is activated twice. Anyway below I've posted the full syslog cutpaste, with some comments. in short: inserting and removing the device causes some errors (maybe timeouts?) for some tries, (first part of logs) then suddenly, after 3/4 tries, the device is identified and then scsi layer gets activated (and confused). this time, the removal of device causes a kernel oops. After, you can also find the behavoiur with ub: no oopses, but the operation is not complete. I've also tried to turn on the box with key inserted, but I'm unable to report because the keyboard/mouse (ps/2) was dead, so maybe something has gone wrong...but i can't tell what. Maybe I can try with serial console to pickup some messages. Anyway, the key is perfectly working on first try with another HW and with 2.6.8.1. I've also attached config.gz. I've checked also config but I can't find something wrong or misconfigured. anyway, if more infos (or test) are needed, just let me know. Many thanks. reports: No UB module compiled: Nov 18 20:30:13 kefk kernel: hub 5-0:1.0: state 5 ports 8 chg ff00 evt 0008 Nov 18 20:30:13 kefk kernel: ehci_hcd :00:1d.7: GetStatus port 3 status 001803 POWER sig=j CSC CONNECT Nov 18 20:30:13 kefk kernel: hub 5-0:1.0: port 3, status 0501, change 0001, 480 Mb/s Nov 18 20:30:13 kefk kernel: hub 5-0:1.0: debounce: port 3: total 100ms stable 100ms status 0x501 Nov 18 20:30:13 kefk kernel: ehci_hcd :00:1d.7: port 3 high speed Nov 18 20:30:13 kefk kernel: ehci_hcd :00:1d.7: GetStatus port 3 status 001005 POWER sig=se0 PE CONNECT Nov 18 20:30:13 kefk kernel: usb 5-3: new high speed USB device using ehci_hcd and address 3 Nov 18 20:30:13 kefk kernel: ehci_hcd :00:1d.7: devpath 3 ep0in 3strikes Nov 18 20:30:13 kefk kernel: ehci_hcd :00:1d.7: port 3 full speed -- companion Nov 18 20:30:13 kefk kernel: ehci_hcd :00:1d.7: GetStatus port 3 status 003801 POWER OWNER sig=j CONNECT Nov 18 20:30:13 kefk kernel: uhci_hcd :00:1d.1: wakeup_hc Nov 18 20:30:13 kefk kernel: hub 2-0:1.0: state 5 ports 2 chg fffc evt 0002 Nov 18 20:30:13 kefk kernel: uhci_hcd :00:1d.1: port 1 portsc 0093,00 Nov 18 20:30:13 kefk kernel: hub 2-0:1.0: port 1, status 0101, change 0001, 12 Mb/s Nov 18 20:30:13 kefk kernel: hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101 Nov 18 20:30:13 kefk kernel: usb 2-1: new full speed USB device using uhci_hcd and address 2 Nov 18 20:30:13 kefk kernel: uhci_hcd :00:1d.1: uhci_result_control: failed with status 44 Nov 18 20:30:13 kefk kernel: [f7a35240] link (37a351b2) element (37a31040) Nov 18 20:30:13 kefk kernel: 0: [f7a31040] link (37a31080) e0 Stalled CRC/Timeo Length=7 MaxLen=7 DT0 EndPt=0 Dev=0, PID=2d(SETUP) (buf=37caa7e0) Nov 18 20:30:13 kefk kernel: 1: [f7a31080] link (37a310c0) e3 SPD Active Length=0 MaxLen=3f DT1 EndPt=0 Dev=0, PID=69(IN) (buf=36b89200) Nov 18 20:30:13 kefk kernel: 2: [f7a310c0] link (0001) e3 IOC Active Length=0 MaxLen=7ff DT1 EndPt=0 Dev=0, PID=e1(OUT) (buf=) Nov 18 20:30:13 kefk kernel: Nov 18 20:30:13 kefk kernel: usb 2-1: device descriptor read/64, error -71 Nov 18 20:30:13 kefk kernel: uhci_hcd :00:1d.1: uhci_result_control: failed with status 44 Nov 18 20:30:13 kefk kernel: [f7a35240] link (37a351b2) element (37a31040) Nov 18 20:30:13 kefk kernel: 0: [f7a31040] link (37a31080) e0 Stalled CRC/Timeo Length=7 MaxLen=7 DT0 EndPt=0 Dev=0, PID=2d(SETUP) (buf=368d9320) Nov 18 20:30:13 kefk kernel: 1: [f7a31080] link
[linux-usb-devel] Re: 2.6.10-rc2-mm2 usb storage still oopses
On Fri, 19 Nov 2004 00:42:40 +0100, Fabio Coatti [EMAIL PROTECTED] wrote:
Nov 18 20:33:05 kefk kernel: sdb: assuming drive cache: write through
Nov 18 20:33:05 kefk kernel: sdb: sdb1
Nov 18 20:33:05 kefk kernel: sdb: sdb1
Nov 18 20:33:05 kefk kernel: kobject_register failed for sdb1 (-17)
This looks as if SCSI falls victim of the general problem which ub addresses
with the following fragment:
--- linux-2.6.10-rc1/drivers/block/ub.c 2004-10-28 09:46:38.0 -0700
+++ linux-2.6.10-rc1-ub/drivers/block/ub.c 2004-11-06 23:59:20.0
-0800
@@ -267,6 +263,7 @@ struct ub_dev {
int changed;/* Media was changed */
int removable;
int readonly;
+ int first_open; /* Kludge. See ub_bd_open. */
char name[8];
struct usb_device *dev;
struct usb_interface *intf;
@@ -1428,6 +1420,26 @@ static int ub_bd_open(struct inode *inod
sc-openc++;
spin_unlock_irqrestore(ub_lock, flags);
+ /*
+* This is a workaround for a specific problem in our block layer.
+* In 2.6.9, register_disk duplicates the code from rescan_partitions.
+* However, if we do add_disk with a device which persistently reports
+* a changed media, add_disk calls register_disk, which does do_open,
+* which will call rescan_paritions for changed media. After that,
+* register_disk attempts to do it all again and causes double kobject
+* registration and a eventually an oops on module removal.
+*
+* The bottom line is, Al Viro says that we should not allow
+* bdev-bd_invalidated to be set when doing add_disk no matter what.
+*/
+ if (sc-first_open) {
+ if (sc-changed) {
+ sc-first_open = 0;
+ rc = -ENOMEDIUM;
+ goto err_open;
+ }
+ }
+
if (sc-removable || sc-readonly)
check_disk_change(inode-i_bdev);
@@ -1467,6 +1479,8 @@ static int ub_bd_release(struct inode *i
spin_lock_irqsave(ub_lock, flags);
--sc-openc;
+ if (sc-openc == 0)
+ sc-first_open = 0;
if (sc-openc == 0 atomic_read(sc-poison))
ub_cleanup(sc);
spin_unlock_irqrestore(ub_lock, flags);
@@ -1919,6 +1932,8 @@ static int ub_probe(struct usb_interface
}
sc-removable = 1; /* XXX Query this from the device */
+ sc-changed = 1;/* ub_revalidate clears only */
+ sc-first_open = 1;
ub_revalidate(sc);
/* This is pretty much a long term P3 */
This feels kludgy, but my excuse is James and Viro made me do it.
I have an IRC log to prove it laying somewhere...
I'm adding the linux-scsi to cc: in case any comments are forthcoming.
-- Pete
---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] oops in usb-storage... scsi_device_cancel
Hi...all I use linux-2.6.10-rc1-bk21 on s3c2440 board. I have a problem with usb-storage... [~]# usb 1-1: new full speed USB device using s3c2410-ohci and address 2 scsi0 : SCSI emulation for USB Mass Storage devices Vendor: ASUS Model: USB Flash DiskRev: 3.0F Type: Direct-Access ANSI SCSI revision: 00 SCSI device sda: 60928 512-byte hdwr sectors (31 MB) sda: Write Protect is off sda: assuming drive cache: write through sda: sda1 Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0 [~]# cd /mnt/ [/mnt]# l drwxr-xr-x2 root root 1024 Nov 9 10:10 kernel drwxr-xr-x2 root root 1024 Nov 9 10:10 rootfs drwxr-xr-x2 root root 1024 Nov 9 10:10 screen drwxr-xr-x2 root root 1024 Nov 3 22:39 usbfs drwxr-xr-x2 root root 1024 Nov 9 10:12 usr1 drwxr-xr-x2 root root 1024 Nov 9 10:10 usr2 drwxr-xr-x2 root root 1024 Nov 9 10:10 usr3 [/mnt]# cat /etc/fstab # /etc/fstab: static file system information. # # file system mount point type options dump pass /dev/nfs/ autodefaults,errors=remount-ro 0 0 proc/proc procdefaults0 0 none/proc/bus/usb usbfs defaults0 0 none/syssysfs defaults0 0 none/dev/ptsdevpts gid=5,mode=620 0 0 /dev/sda1 /mnt/usbfs vfatdefaults0 0 #/dev/mtdblock0 /mnt/kernel jffs2 defaults0 0 #/dev/mtdblock1 /mnt/rootfs jffs2 defaults0 0 /dev/mtdblock2 /mnt/usr1 jffs2 defaults0 0 /dev/mtdblock3 /mnt/usr2 jffs2 defaults0 0 /dev/mtdblock4 /mnt/usr3 jffs2 defaults0 0 /dev/mtdblock5 /mnt/screen jffs2 defaults0 0 [/mnt]# mount usbfs [/mnt]# l usbfs/ -rwxr-xr-x1 root root 5687296 Sep 15 11:45 KCM.mp3 -rwxr-xr-x1 root root 6314027 May 24 00:15 Tei.mp3 -rwxr-xr-x1 root root 552842 Jan 1 2000 ash1 -rwxr-xr-x1 root root 4226056 Jan 1 2000 libsmokeqt.so.1.0.0 [/mnt]# usb 1-1: USB disconnect, address 2 target0:0:0: Illegal state transition NULL-cancel Badness in scsi_device_set_state at drivers/scsi/scsi_lib.c:1713 [c012ec14] (scsi_device_set_state+0x0/0x144) from [c012a318] (scsi_device_cancel+0x2c/0x110) r6 = r5 = C3D7BE0C r4 = C3D8A480 [c012a2ec] (scsi_device_cancel+0x0/0x110) from [c0117938] (device_for_each_child+0x44/0x6c) r8 = C3D7BE5C r7 = C012A414 r6 = r5 = C3D8A604 r4 = C3FE50CC [c01178f4] (device_for_each_child+0x0/0x6c) from [c012a478] (scsi_host_cancel+0x48/0xe4) r8 = C3D80EE0 r7 = C3FE50B0 r6 = C3FE5000 r5 = 0001 r4 = C3FE5000 [c012a430] (scsi_host_cancel+0x0/0xe4) from [c012a534] (scsi_remove_host+0x20/0x68) r7 = C0A737A8 r6 = r5 = 0001 r4 = C3FE5000 [c012a514] (scsi_remove_host+0x0/0x68) from [c01544c4] (storage_disconnect+0xbc/0xd0) r4 = C3D8A400 [c0154408] (storage_disconnect+0x0/0xd0) from [c0141010] (usb_unbind_interface+0x4c/0x78) r6 = C3D8A000 r5 = C0222508 r4 = C3D80820 [c0140fc4] (usb_unbind_interface+0x0/0x78) from [c0118500] (device_release_driver+0x60/0x6c) r5 = C0222528 r4 = C3D80834 [c01184a0] (device_release_driver+0x0/0x6c) from [c0118694] (bus_remove_device+0x88/0xbc) r5 = C0221780 r4 = C3D80834 [c011860c] (bus_remove_device+0x0/0xbc) from [c01178b4] (device_del+0x64/0x84) r7 = C0A737A8 r6 = C3D8A000 r5 = C3D8A0C4 r4 = C3D80834 [c0117850] (device_del+0x0/0x84) from [c0147654] (usb_disable_device+0x84/0xf8) r5 = 0001 r4 = C3D80820 [c01475d0] (usb_disable_device+0x0/0xf8) from [c0142fcc] (usb_disconnect+0xe0/0x170) r6 = r5 = C3D8A040 r4 = C3D8A000 [c0142eec] (usb_disconnect+0x0/0x170) from [c01442cc] (hub_thread+0x2f0/0xa60) r7 = C0A6CA74 r6 = C3D80F0C r5 = 0003 r4 = 0100 [c0143fdc] (hub_thread+0x0/0xa60) from [c003e2a0] (do_exit+0x0/0xab8) Unable to handle kernel paging request at virtual address 000150ae pgd = c0004000 [000150ae] *pgd= Internal error: Oops: 3 [#1] Modules linked in: CPU: 0 PC is at scsi_device_cancel+0x4c/0x110 LR is at 0x1 pc : [c012a338]lr : [0001]Not tainted sp : c3d7be0c ip : 6093 fp : c3d7be34 r10: c0a73600 r9 : c0a73600 r8 : r7 : 6013 r6 : c3d8a49c r5 : c3d7be0c r4 : 00014ff6 r3 : 00015006 r2 : 003a4b76 r1 : e92ddff0 r0 : ffea Flags: nzcv IRQs off FIQs on Mode SVC_32 Segment kernel Control: C000717F Table: 30B88000 DAC: 001D Process khubd (pid: 6, stack limit = 0xc3d7a190) Stack: (0xc3d7be0c to 0xc3d7c000) be00:c3d7be0c c3d7be0c c3fe50cc c3d8a604 be20: c012a414 c3d7be5c c3d7be58 c3d7be38 c0117938 c012a2fc c3fe5000 0001 be40:
[linux-usb-devel] failure notice
Hi. This is the qmail-send program at readyserver.net. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. [EMAIL PROTECTED]: Sorry, no mailbox here by that name. vpopmail (#5.1.1) --- Enclosed are the original headers of the message. ---BeginMessage--- (Body supressed) ---End Message---
[linux-usb-devel] Re: 2.6.10-rc2-mm2 usb storage still oopses
Nov 18 20:35:24 kefk kernel: Unable to handle kernel NULL pointer dereference
at virtual address 0050
Nov 18 20:35:24 kefk kernel: printing eip:
Nov 18 20:35:24 kefk kernel: c0186e32
Nov 18 20:35:24 kefk kernel: *pde =
Nov 18 20:35:24 kefk kernel: Oops: [#1]
Nov 18 20:35:24 kefk kernel: PREEMPT SMP
Nov 18 20:35:24 kefk kernel: Modules linked in: nls_cp850 usb_storage md5
ipv6
rfcomm l2cap bluetooth snd_emu10k1 snd_rawmidi snd_seq_device snd_ac97_codec
snd_pcm snd_timer snd_page_alloc snd_util_mem snd_hwdep snd soundcore
ipt_REJECT iptable_filter ip_tables loop nls_utf8 ide_cd i2c_dev w83781d
i2c_sensor i2c_isa i2c_i801 isofs zlib_inflate e1000 parport_pc ppa parport
ehci_hcd usblp uhci_hcd genrtc
Nov 18 20:35:24 kefk kernel: CPU:0
Nov 18 20:35:24 kefk kernel: EIP:0060:[sysfs_hash_and_remove+174/241]
Not tainted VLI
Nov 18 20:35:24 kefk kernel: EIP:0060:[c0186e32]Not tainted VLI
Nov 18 20:35:24 kefk kernel: EFLAGS: 00010246 (2.6.10-rc2-mm2)
Nov 18 20:35:24 kefk kernel: EIP is at sysfs_remove_dir+0x1d/0x10b
Nov 18 20:35:24 kefk kernel: eax: f6e79988 ebx: f6e79988 ecx: c18ff480
edx: c100
Nov 18 20:35:24 kefk kernel: esi: f78b8b00 edi: ebp: f7bd5d24
esp: c1b7ddd8
Nov 18 20:35:24 kefk kernel: ds: 007b es: 007b ss: 0068
The following patch should avoid the sysfs_remove_dir() oops you are
seeing while device removal. It anyway fixes the obvious error and is
needed. But it will not make any change to the first error you are
seeing while connecting the device.
Andrew, Greg, please include this.
Thanks
Maneesh
o Following patch avoids the sysfs_remove_dir() oops when it is passed
a kobject with NULL dentry.
Signed-off-by: Maneesh Soni [EMAIL PROTECTED]
---
linux-2.6.10-rc2-bk3-maneesh/fs/sysfs/dir.c |3 ++-
1 files changed, 2 insertions(+), 1 deletion(-)
diff -puN fs/sysfs/dir.c~fix-sysfs_remove_dir-oops fs/sysfs/dir.c
--- linux-2.6.10-rc2-bk3/fs/sysfs/dir.c~fix-sysfs_remove_dir-oops
2004-11-18 19:59:51.0 -0600
+++ linux-2.6.10-rc2-bk3-maneesh/fs/sysfs/dir.c 2004-11-18
20:01:11.0 -0600
@@ -268,7 +268,7 @@ void sysfs_remove_subdir(struct dentry *
void sysfs_remove_dir(struct kobject * kobj)
{
struct dentry * dentry = dget(kobj-dentry);
- struct sysfs_dirent * parent_sd = dentry-d_fsdata;
+ struct sysfs_dirent * parent_sd;
struct sysfs_dirent * sd, * tmp;
if (!dentry)
@@ -276,6 +276,7 @@ void sysfs_remove_dir(struct kobject * k
pr_debug(sysfs %s: removing dir\n,dentry-d_name.name);
down(dentry-d_inode-i_sem);
+ parent_sd = dentry-d_fsdata;
list_for_each_entry_safe(sd, tmp, parent_sd-s_children, s_sibling) {
if (!sd-s_element || !(sd-s_type SYSFS_NOT_PINNED))
continue;
_
---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] USER SPACE DRIVER
Olanrewaju O Ayo wrote: i am trying to interface with a spectrometer usb device using the libusb functions. i am having problems with re-reading the idProduct and idVendor so that i do not use the one assigned to it by the system. it keeps giving me invalid reference error when i use the function usb_get_device_descriptor. pls help on how to solve this problem will be appreciated. pls respond by sending e-mail to the ffg. address [EMAIL PROTECTED] I don't understand so that i do not use the one assigned to it by the system. However, you can try the libusb mailing list (see http://sourceforge.net/mail/?group_id=1674 ) or you can post some source code here for comments. This isn't quite enough to go on. -- ~Randy --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] ati_remote Medion RF remote contol
Joop Zonnet wrote:
Hi list,
I'd like to know what to do next. Can anyone tell me what I did wrong,
please? How should I go about suggesting a patch, a change etc. etc?
wkr,
Gerke
Hi,
I can't help you with testing (no such device), but I'm looking
at your file. I have some comments on it, and then I'll try
to help you on how to make a patch file from it.
1. Don't change struct { ... } ati_remote_tbl
to a typedef. In general, Linux doesn't like or use
typedefs for structures. It hides too much.
Leave a struct as a struct.
2. why did you delete the line(s):
set_current_state(TASK_INTERRUPTIBLE);
before calling schedule_timeout() ?
3. I'm not sure about the changes from usb_kill_urb() to
usb_unlink_urb() (since I haven't been keeping up with the
USB kernel API very well). Maybe someone else can comment
on those.
4. The key conversion handling looks reasonable to me.
OK, to make a patch so that you can post it here:
Do this in a current kernel tree (like linux-2.6.10-rc2):
a. in drivers/usb/input, rename (old) ati_remote.c to
ati_remote.c.221
b. copy your ati_remote.c into drivers/usb/input/
c. cd ../../../.. (i.e., to one level above the
kernel tree)
d. (one command line:)
diff -Naurp linux-2.6.10-rc2/drivers/usb/input/ati_remote.c.221
linux-2.6.10-rc2/drivers/usb/input/ati_remote.c
ati_remote_222.patch
e. Send an email to [EMAIL PROTECTED] with Subject:
that contains: [PATCH] ati_remote: add Medion RF remote control
(e.g.)
In the body of the email, put a short description of your
patch, diffstat of it (optional but preferred),
Signed-off-by: your name email address
and the patch file (inline in the email [text/plain attachment
if you must]). Make sure that your email client does not
mangle/destroy whitespace in your patch.
Here are some very useful references that you should check out:
linux-2.6.x/Documentation/SubmittingPatches
linux-2.6.x/Documentation/SubmittingDrivers
linux-2.6.x/Documentation/CodingStyle
http://linux.yyz.us/patch-format.html
http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
Joop Zonnet wrote:
Hi list,
some time ago I got myself a computer. Together with that computer I
got a Medion RF remote control.
With lsusb I found that the USB device was the same as the one that
was supported by the ati_remote kernel module, only the sub-id was
differend and later I found the keymap to be different as well.
I mailed to the man who last worked on the driver according to the
source and worked out that there was someone that created a new key
map for my device but that that person did not integrate that new
key-map with the driver. So I had a go at it. In my version it
determines the keymap to use at plug-in time on a per device base.
I was working with the Kernel that came with my disto (Mandrake).
uname -a gives me:
Linux gerkek2.thuis99.org 2.6.8.1-12mdksmp #1 SMP Fri Oct 1
11:24:45 CEST 2004 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz unknown
GNU/Linux
I'm not sure how to go about creating a patch-file or how to go about
getting others to test my changes. I only have one remote control (The
Menion one ;-) ) and would like others to test my changes. I'd be
happy to send the new version of the ati_remote.c file or any other
format if the requester is kind enought to tell me how to get it (diff
or patch or what ever)
--
~Randy
---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] linux-usb-devel
50-3000
5-15
A10-1513-16%B3-105.86.5%,
123
:6 A1002\2104 :100078
: 010-8767953187679530
:http://www.sszb.org
E_mail:[EMAIL PROTECTED][EMAIL PROTECTED]
:
{}
---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
RE: [linux-usb-devel] HC gets too little data from devices - seems solved
Hi, I think I figured out where the problems came from. First, the too little data: Get configuration (Fails. For some reason, we get only 32 bytes back instead of 34.) MPS=8 FA=2 DIR=0 EP=0 SPD=1 LEN=8 --out- 80 06 00 02 00 00 22 00 MPS=8 FA=2 DIR=2 EP=0 SPD=1 LEN=34 COUNT=32 --in-- 09 02 22 00 01 01 00 a0 32 09 04 00 00 01 03 01 01 00 09 21 10 01 00 01 22 41 00 07 05 81 03 08 00 00 No status transaction follows, as the buffer rounding bit in the TD is clear. (Lothar, I added the buffer rounding bit handling to update_td_status()). Then timeout follows: usb 1-1: unable to read config index 0 descriptor/all usb 1-1: can't read configurations, error -110 What really happens here is the following sequence of packets on the usb bus: sof, about 100us quiescence, in, data1 (1st 8 bytes), ack, in, nack, in, nack, in, nack, in, data0 (2nd 8 bytes), ack, in, nack, in, nack, in, nack, in, data1 (3rd 8 bytes), ack, in, nack, in, nack, in, nack, in, data0 (4th 8 bytes), ack, 150us quiescence, sof and over it is. There was not enough time in the frame to perform more transfers. If I reduced the lsthreshold register's content to 0, I got all the bytes for this transfer. I.e., the last line in the above sequence became in, data0 (4th 8 bytes), ack, in, nack, in, data1 (last 2 bytes), ack, sof but then it failed later in the configuration process, when even more bytes were requested. The HC does not send off case: With one device, I have seen another type of weirdness. The device is Trendnet's TMR-61U2 card reader (which, again, works perfectly if attached to my x86 box). For that device, the failure seems to be that HC just does not send off the IN transaction. Like here: set address (OK) MPS=8 FA=0 DIR=0 EP=0 SPD=0 LEN=8 --out- 00 05 02 00 00 00 00 00 MPS=8 FA=0 DIR=2 EP=0 SPD=0 LEN=0 get device descriptor (Fails, IN transaction not performed) MPS=8 FA=2 DIR=0 EP=0 SPD=0 LEN=8 --out- 80 06 00 01 00 00 08 00 MPS=8 FA=2 DIR=2 EP=0 SPD=0 LEN=8 COUNT=0 The Philips transfer descriptor for this last IN transaction, read back from the device AFTER HC has reported via ATLInt that the buffer is processed and ready, is the following: fc00 0808 0808 0002 where the leftmost nibble f shows that the HC has not even tried to perform the IN transaction. In fact what I saw on the USB bus, was this: sof, in, nack, in, nack, ...pattern repeats..., in, nack, 150us quiet, sof and over it is again. I.e., the device was just not yet ready during that particular millisecond. After getting the above packet sequences from the usb bus with a logic analyzer (I have no usb analyzer, but hand-decoding of the NRZI-encoded stream is not that hard), I re-learned that there is this ACTIVE bit in the PTD header and what it really means. Embarrasing, isn't it. I suspected all the time there's something wrong with our hardware or chip configuration and therefore overlooked the sending process. Olav --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] how to make usb-skeleton work with device
hi all i have compiled usb-skelton.c and inserted in the kernel now how should i make it work with my device . ( i made a node with command mknod name b major minor and mounted it on some directory...but i didn't work) What is the major minor number alloted to that? What is the proper sequence? Thanking u __ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
