Re: [linux-usb-devel] [PATCH] Support for gzipped usb.ids files
On Sat, Aug 05, 2006 at 04:02:39PM -0700, David Brownell wrote:
There seems to be a missing install gzipped usb.ids file step
for make install ...
Oops, you are right. Please find attached a new version of the patch.
Are pciutils going to install compressed pci.ids?
Actually the idea of the compressed usb.ids has been given to me by the
Debian maintainer of pciutils. The current version of pciutils in Debian
already deals with compressed pci.ids, but I don't know if the patch has
been merged upstream yet.
Bye,
Aurelien
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' [EMAIL PROTECTED] | [EMAIL PROTECTED]
`-people.debian.org/~aurel32 | www.aurel32.net
--- usbutils-0.72.orig/configure.in
+++ usbutils-0.72/configure.in
@@ -34,6 +34,25 @@
AC_CHECK_LIB(usb, usb_get_string_simple, ,
[AC_MSG_ERROR(get libusb 0.1.8 or newer)])
+
+dnl zlib on enabled by default (if found)
+USE_ZLIB=yes
+AC_ARG_ENABLE(zlib,
+ AC_HELP_STRING([--disable-zlib],
+ [disable support for zlib]),
+ [
+if eval test x$enable_zlib = xno; then
+ USE_ZLIB=
+fi
+ ])
+if test $USE_ZLIB = yes ; then
+ AC_CHECK_LIB(z, inflateEnd)
+ if test ${ac_cv_lib_z_inflateEnd} = yes ; then
+HAVE_ZLIB=yes
+ fi
+fi
+AM_CONDITIONAL(HAVE_ZLIB, test x$HAVE_ZLIB = xyes)
+
#AC_ARG_ENABLE(usbmodules,
# [ --enable-usbmodules build usbmodules (for Linux 2.4)],
# [ case ${enableval} in
--- usbutils-0.72.orig/Makefile.am
+++ usbutils-0.72/Makefile.am
@@ -11,10 +11,16 @@
devtree.c devtree.h list.h \
usbmisc.c usbmisc.h
-data_DATA = usb.ids
-
man_MANS = lsusb.8
+install-data-local:
+ $(mkinstalldirs) $(DESTDIR)$(datadir)
+if HAVE_ZLIB
+ gzip -c -n -9 $(srcdir)/usb.ids $(DESTDIR)$(datadir)/usb.ids
+else
+ $(INSTALL_DATA) $(srcdir)/usb.ids $(DESTDIR)$(datadir)/usb.ids
+endif
+
# usbmodules is needed only with 2.4 based hotplugging, and is OBSOLETE
# EXTRA_PROGRAMS = usbmodules
@@ -27,4 +33,4 @@
#man_MANS += usbmodules.8
#endif
-EXTRA_DIST = $(man_MANS) $(data_DATA) update-usbids.sh
+EXTRA_DIST = $(man_MANS) usb.ids update-usbids.sh
--- usbutils-0.72.orig/names.c
+++ usbutils-0.72/names.c
@@ -38,6 +38,19 @@
#include config.h
#endif
+#ifdef HAVE_LIBZ
+#include zlib.h
+#definemy_file gzFile
+#definemy_fopen(path, mode)gzopen(path, mode)
+#definemy_fgets(s, size, stream) gzgets(stream, s, size)
+#definemy_close(f) gzclose(f)
+#else
+#definemy_file FILE*
+#definemy_fopen(path, mode)fopen(path, mode)
+#definemy_fgets(s, size, stream) fgets(s, size, stream)
+#definemy_close(f) fclose(f)
+#endif
+
#include names.h
@@ -454,14 +467,14 @@
#define DBG(x)
-static void parse(FILE *f)
+static void parse(my_file f)
{
char buf[512], *cp;
unsigned int linectr = 0;
int lastvendor = -1, lastclass = -1, lastsubclass = -1, lasthut=-1,
lastlang=-1;
unsigned int u;
- while (fgets(buf, sizeof(buf), f)) {
+ while (my_fgets(buf, sizeof(buf), f)) {
linectr++;
/* remove line ends */
if ((cp = strchr(buf, 13)))
@@ -785,12 +798,12 @@
int names_init(char *n)
{
- FILE *f;
+ my_file f;
- if (!(f = fopen(n, r))) {
+ if (!(f = my_fopen(n, r))) {
return errno;
}
parse(f);
- fclose(f);
+ my_close(f);
return 0;
}
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
linux-usb-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] cannot eject ipod. more data with usb-storage debug msg
On Sat, 5 Aug 2006, Pete Zaitcev wrote: On Sat, 5 Aug 2006 22:47:02 -0400 (EDT), Alan Stern [EMAIL PROTECTED] wrote: I looked into it a bit more closely. Here's the complete story. [...] What do you think about giving all iPods US_FL_NON_LOCKABLE flag? I considered such a patch for bug 154955, but didn't push it for two reasons: - An ulterior motive: adding an unusual_devs.h entry removes the device from ub, and I wanted my own iPod to stay accessible to ub. Then I'd be motivated to push that huge patch which adds an extra argument to the UNUSUAL_DEV. It's a can of worms. - Since Apple bumps product IDs, we have to chase them all the time. Other than that, seems like a winner... I don't know. It doesn't solve the real problem, which is that the eject program doesn't send an Eject command immediately after unlocking the medium. Fix that and then all the iPods should work with no trouble under both ub and usb-storage. Alan Stern - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Unlock Your Mind's Hidden Power, Today...
www.HumanDataTransfer.com great information. --- MAF Anti-Spam ID: 20060801082756H1v3CkI2 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] [PATCH] Support for gzipped usb.ids files
On Sun, 6 Aug 2006 17:08:34 +0200 Aurelien Jarno wrote: On Sat, Aug 05, 2006 at 04:02:39PM -0700, David Brownell wrote: There seems to be a missing install gzipped usb.ids file step for make install ... Oops, you are right. Please find attached a new version of the patch. Are pciutils going to install compressed pci.ids? Actually the idea of the compressed usb.ids has been given to me by the Debian maintainer of pciutils. The current version of pciutils in Debian already deals with compressed pci.ids, but I don't know if the patch has been merged upstream yet. It was just posted to the linux-pci m-l on Aug-04 and has not been acted on. --- ~Randy - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Prolific 2305 parport stalls / usblp write timeout
Hi,
out of a sudden (ok, I had updated the notebook from Debian stable to Debian
testing) my usb-Parport adapter stopped working and still does not send data to
the printer, even on other stable installations, even using another adapter,
even using a different printer.
During the research I found that CUPS is not to blame, usblp gets the data via
the usb backend and then nothing really useful happens.
I'm of course interested in finding a solution for the problem but while
looking into the sources I found some time I doubt whether they are the way
they should be.
The kernel is 2.6.17.6 and was so before the upgrade, so this is a should not
happen for me.
The adapter is identified by lsusb as follows:
| Bus 001 Device 005: ID 067b:2305 Prolific Technology, Inc. PL2305 Parallel
Port
A sample usbmon output, the command for that was a
cat print.data /dev/usb/lp0:
| c366dd40 3767889620 S Bi:005:02 -115 8192
| c3a567a0 3767897983 S Bo:005:01 -115 4096 = 1b451b26 6c36441b 266b3132
481b266c 304f1b26 6c323641 1b266c37 30501b26
| c366d260 3787895733 S Ci:005:00 s a1 01 0001 1
| c366d260 3787896664 C Ci:005:00 0 1 = 18
| c366dda0 3807896961 S Ci:005:00 s a1 01 0001 1
| c366dda0 3807898424 C Ci:005:00 0 1 = 18
The last two lines repeat every twenty seconds corresponding to
USBLP_WRITE_TIMEOUT (see below on timeout times). With DEBUG enabled these
control packets are also in the kernel log file:
| kernel: drivers/usb/class/usblp.c: usblp_control_msg: rq: 0x01 dir: 1 recip:
1 value: 0 idx: 0 len: 0x1 result: 1
This means the adapter isn't entirely dead but somehow it could not deal with
the bulk transfer. All further enquiries e.g. using CUPS's
/usr/lib/cups/backend-available/usb return errors like in
| open(/dev/usb/lp0, O_RDWR|O_EXCL) = 3
| ioctl(3, SNDCTL_DSP_SYNC, 0xbff088b0) = -1 EIO (Input/output error)
To reset the adapter I need to unplug it on the usb side.
Adding the device to the quirk_printers table didn't help. I've also reduced
USBLP_BUF_SIZE to 1024 and even 512 but no avail.
Now finally I'm out of ideas what to do next. Any suggestions?
Looking into the kernel sources: The first thing that confuses me the
write timeout handling in usblp_write l.642
| if (!usblp-wcomplete) {
| barrier();
(...)
| timeout = USBLP_WRITE_TIMEOUT;
|
| rv = wait_event_interruptible_timeout(usblp-wait,
usblp-wcomplete || !usblp-present , timeout);
| if (rv 0)
| return writecount ? writecount : -EINTR;
| }
which means: If the already submitted urb is not yet processed, wait for the
timeout, and unless the operation was interrupted, proceed as if the operation
is completed. In other words, in my situation the main loop is never left. Is
this by intention?
Personally I'd insert a check against timeout, something like:
| if (rv == 0) {
| err(usblp%d: timeout writing to printer,
usblp-minor);
| return -EFAULT;
| }
to put an end to that. Perhaps with some other actions like device reset.
Regarding the TIMEOUT value:
The timeout definition is obviously in milliseconds:
| #define USBLP_WRITE_TIMEOUT (5000) /* 5 seconds */
while the usage of wait_event_interruptible_timeout at l.652
| timeout = USBLP_WRITE_TIMEOUT;
| rv = wait_event_interruptible_timeout( (...) , timeout);
is jiffies according to include/linux/wait.h. This causes different timeout
values depending on HZ which is probably not intended.
Easy Solution:
+ timeout = USBLP_WRITE_TIMEOUT * HZ/1000;
Christoph
(off-list Cc: welcome)
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
linux-usb-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] Problem: irq 217: nobody cared + backtrace
On Fri, 2006-08-04 at 13:11 -0400, Alan Stern wrote: On Fri, 4 Aug 2006, Sergio Monteiro Basto wrote: I also got : uhci_hcd :00:10.1: host controller process error, something bad happened! uhci_hcd :00:10.1: host controller halted, very bad! uhci_hcd :00:10.1: HC died; cleaning up usb 3-2: USB disconnect, address 2 In case it happens again, here's how you can get more information. Turn on CONFIG_USB_DEBUG and CONFIG_DEBUG_FS, and mount a debugfs filesystem somewhere (say /sys/kernel/debug). Then after the problem occurs, save a copy of /sys/kernel/debug/uhci/:00:1d.1 can you explain to me how I mount debugfs filesystem ? please You don't need debugfs to solve the problem shown above. What version of the kernel are you using? Alan Stern http://bugme.osdl.org/show_bug.cgi?id=6419#c16 http://bugme.osdl.org/show_bug.cgi?id=6419#c19 all the time, with 2.6.18-rc3 Here is a patch which should fix the host controller process error problem: http://marc.theaimsgroup.com/?l=linux-usb-develm=115435540308759w=2 yes! I am testing 2.6.18-rc3-git7.bz2 which have your patch, with CONFIG_USB_DEBUG and CONFIG_DEBUG_FS on and I can googling :), it is working. I have done a stress test with azureus and still working! Tomorrow I will test the irq 201, 209 or 217 nobody care. Many thanks Alan, -- Sérgio M. B. smime.p7s Description: S/MIME cryptographic signature - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Error with testusb
Hi all, I have a problem when using testusb, please help me to solve this. Here is log: [EMAIL PROTECTED] misc]# cat /proc/bus/usb/devices T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 3 Spd=480 MxC h= 0 D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=067b ProdID=2517 Rev= 0.01 S: Manufacturer=USB 2.0 Flash Disk S: Product=USB Mass Storage Device C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=05 Prot=50 Driver =usb-storage E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms [EMAIL PROTECTED] misc]# insmod usbtest.ko vendor=0x067b product=0x2517 [EMAIL PROTECTED] misc]# lsmod |grep usb usbtest24844 0 usb_storage 104592 1 scsi_mod 131980 2 sd_mod,usb_storage [EMAIL PROTECTED] misc]# [EMAIL PROTECTED] misc]# ./usbtree /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/8p, 480M |__ Port 7: Dev 2, If 0, Class=hub, Driver=hub/1p, 480M |__ Port 1: Dev 3, If 0, Class=stor., Driver=usb-storage, 480M [EMAIL PROTECTED] misc]# testusb -D /proc/bus/usb/001/003 testusb: /proc/bus/usb/001/003 may see only control tests /proc/bus/usb/001/003 test 0 -- 25 (error 25) /proc/bus/usb/001/003 test 1 -- 25 (error 25) /proc/bus/usb/001/003 test 2 -- 25 (error 25) /proc/bus/usb/001/003 test 3 -- 25 (error 25) /proc/bus/usb/001/003 test 4 -- 25 (error 25) /proc/bus/usb/001/003 test 5 -- 25 (error 25) /proc/bus/usb/001/003 test 6 -- 25 (error 25) /proc/bus/usb/001/003 test 7 -- 25 (error 25) /proc/bus/usb/001/003 test 8 -- 25 (error 25) /proc/bus/usb/001/003 test 9 -- 25 (error 25) /proc/bus/usb/001/003 test 10 -- 25 (error 25) /proc/bus/usb/001/003 test 11 -- 25 (error 25) /proc/bus/usb/001/003 test 12 -- 25 (error 25) /proc/bus/usb/001/003 test 13 -- 25 (error 25) /proc/bus/usb/001/003 test 14 -- 25 (error 25) /proc/bus/usb/001/003 test 15 -- 25 (error 25) /proc/bus/usb/001/003 test 16 -- 25 (error 25) /proc/bus/usb/001/003 test 17 -- 25 (error 25) /proc/bus/usb/001/003 test 18 -- 25 (error 25) /proc/bus/usb/001/003 test 19 -- 25 (error 25) /proc/bus/usb/001/003 test 20 -- 25 (error 25) /proc/bus/usb/001/003 test 21 -- 25 (error 25) /proc/bus/usb/001/003 test 22 -- 25 (error 25) /proc/bus/usb/001/003 test 23 -- 25 (error 25) /proc/bus/usb/001/003 test 24 -- 25 (error 25) /proc/bus/usb/001/003 test 25 -- 25 (error 25) /proc/bus/usb/001/003 test 26 -- 25 (error 25) /proc/bus/usb/001/003 test 27 -- 25 (error 25) /proc/bus/usb/001/003 test 28 -- 25 (error 25) /proc/bus/usb/001/003 test 29 -- 25 (error 25) [EMAIL PROTECTED] misc]# testusb -D /proc/bus/usb/001/002 testusb: /proc/bus/usb/001/002 may see only control tests /proc/bus/usb/001/002 test 0 -- 38 (error 38) /proc/bus/usb/001/002 test 1 -- 38 (error 38) /proc/bus/usb/001/002 test 2 -- 38 (error 38) /proc/bus/usb/001/002 test 3 -- 38 (error 38) /proc/bus/usb/001/002 test 4 -- 38 (error 38) /proc/bus/usb/001/002 test 5 -- 38 (error 38) /proc/bus/usb/001/002 test 6 -- 38 (error 38) /proc/bus/usb/001/002 test 7 -- 38 (error 38) /proc/bus/usb/001/002 test 8 -- 38 (error 38) /proc/bus/usb/001/002 test 9 -- 38 (error 38) /proc/bus/usb/001/002 test 10 -- 38 (error 38) /proc/bus/usb/001/002 test 11 -- 38 (error 38) /proc/bus/usb/001/002 test 12 -- 38 (error 38) /proc/bus/usb/001/002 test 13 -- 38 (error 38) /proc/bus/usb/001/002 test 14 -- 38 (error 38) /proc/bus/usb/001/002 test 15 -- 38 (error 38) /proc/bus/usb/001/002 test 16 -- 38 (error 38) /proc/bus/usb/001/002 test 17 -- 38 (error 38) /proc/bus/usb/001/002 test 18 -- 38 (error 38) /proc/bus/usb/001/002 test 19 -- 38 (error 38) /proc/bus/usb/001/002 test 20 -- 38 (error 38) /proc/bus/usb/001/002 test 21 -- 38 (error 38) /proc/bus/usb/001/002 test 22 -- 38 (error 38) /proc/bus/usb/001/002 test 23 -- 38 (error 38) /proc/bus/usb/001/002 test 24 -- 38 (error 38) /proc/bus/usb/001/002 test 25 -- 38 (error 38) /proc/bus/usb/001/002 test 26 -- 38 (error 38) /proc/bus/usb/001/002 test 27 -- 38 (error 38) /proc/bus/usb/001/002 test 28 -- 38 (error 38) /proc/bus/usb/001/002 test 29 -- 38 (error 38) Thanks -- This message was sent on behalf of [EMAIL PROTECTED] at openSubscriber.com http://www.opensubscriber.com/message/linux-usb-devel@lists.sourceforge.net/3652159.html - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ linux-usb-devel@lists.sourceforge.net To unsubscribe,
[linux-usb-devel] Error with testusb
Hi all, I have a problem when using testusb, please help me to solve this. Here is log: [EMAIL PROTECTED] misc]# cat /proc/bus/usb/devices T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 3 Spd=480 MxC h= 0 D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=067b ProdID=2517 Rev= 0.01 S: Manufacturer=USB 2.0 Flash Disk S: Product=USB Mass Storage Device C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=05 Prot=50 Driver =usb-storage E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms [EMAIL PROTECTED] misc]# insmod usbtest.ko vendor=0x067b product=0x2517 [EMAIL PROTECTED] misc]# lsmod |grep usb usbtest24844 0 usb_storage 104592 1 scsi_mod 131980 2 sd_mod,usb_storage [EMAIL PROTECTED] misc]# [EMAIL PROTECTED] misc]# ./usbtree /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/8p, 480M |__ Port 7: Dev 2, If 0, Class=hub, Driver=hub/1p, 480M |__ Port 1: Dev 3, If 0, Class=stor., Driver=usb-storage, 480M [EMAIL PROTECTED] misc]# testusb -D /proc/bus/usb/001/003 testusb: /proc/bus/usb/001/003 may see only control tests /proc/bus/usb/001/003 test 0 -- 25 (error 25) /proc/bus/usb/001/003 test 1 -- 25 (error 25) /proc/bus/usb/001/003 test 2 -- 25 (error 25) /proc/bus/usb/001/003 test 3 -- 25 (error 25) /proc/bus/usb/001/003 test 4 -- 25 (error 25) /proc/bus/usb/001/003 test 5 -- 25 (error 25) /proc/bus/usb/001/003 test 6 -- 25 (error 25) /proc/bus/usb/001/003 test 7 -- 25 (error 25) /proc/bus/usb/001/003 test 8 -- 25 (error 25) /proc/bus/usb/001/003 test 9 -- 25 (error 25) /proc/bus/usb/001/003 test 10 -- 25 (error 25) /proc/bus/usb/001/003 test 11 -- 25 (error 25) /proc/bus/usb/001/003 test 12 -- 25 (error 25) /proc/bus/usb/001/003 test 13 -- 25 (error 25) /proc/bus/usb/001/003 test 14 -- 25 (error 25) /proc/bus/usb/001/003 test 15 -- 25 (error 25) /proc/bus/usb/001/003 test 16 -- 25 (error 25) /proc/bus/usb/001/003 test 17 -- 25 (error 25) /proc/bus/usb/001/003 test 18 -- 25 (error 25) /proc/bus/usb/001/003 test 19 -- 25 (error 25) /proc/bus/usb/001/003 test 20 -- 25 (error 25) /proc/bus/usb/001/003 test 21 -- 25 (error 25) /proc/bus/usb/001/003 test 22 -- 25 (error 25) /proc/bus/usb/001/003 test 23 -- 25 (error 25) /proc/bus/usb/001/003 test 24 -- 25 (error 25) /proc/bus/usb/001/003 test 25 -- 25 (error 25) /proc/bus/usb/001/003 test 26 -- 25 (error 25) /proc/bus/usb/001/003 test 27 -- 25 (error 25) /proc/bus/usb/001/003 test 28 -- 25 (error 25) /proc/bus/usb/001/003 test 29 -- 25 (error 25) [EMAIL PROTECTED] misc]# testusb -D /proc/bus/usb/001/002 testusb: /proc/bus/usb/001/002 may see only control tests /proc/bus/usb/001/002 test 0 -- 38 (error 38) /proc/bus/usb/001/002 test 1 -- 38 (error 38) /proc/bus/usb/001/002 test 2 -- 38 (error 38) /proc/bus/usb/001/002 test 3 -- 38 (error 38) /proc/bus/usb/001/002 test 4 -- 38 (error 38) /proc/bus/usb/001/002 test 5 -- 38 (error 38) /proc/bus/usb/001/002 test 6 -- 38 (error 38) /proc/bus/usb/001/002 test 7 -- 38 (error 38) /proc/bus/usb/001/002 test 8 -- 38 (error 38) /proc/bus/usb/001/002 test 9 -- 38 (error 38) /proc/bus/usb/001/002 test 10 -- 38 (error 38) /proc/bus/usb/001/002 test 11 -- 38 (error 38) /proc/bus/usb/001/002 test 12 -- 38 (error 38) /proc/bus/usb/001/002 test 13 -- 38 (error 38) /proc/bus/usb/001/002 test 14 -- 38 (error 38) /proc/bus/usb/001/002 test 15 -- 38 (error 38) /proc/bus/usb/001/002 test 16 -- 38 (error 38) /proc/bus/usb/001/002 test 17 -- 38 (error 38) /proc/bus/usb/001/002 test 18 -- 38 (error 38) /proc/bus/usb/001/002 test 19 -- 38 (error 38) /proc/bus/usb/001/002 test 20 -- 38 (error 38) /proc/bus/usb/001/002 test 21 -- 38 (error 38) /proc/bus/usb/001/002 test 22 -- 38 (error 38) /proc/bus/usb/001/002 test 23 -- 38 (error 38) /proc/bus/usb/001/002 test 24 -- 38 (error 38) /proc/bus/usb/001/002 test 25 -- 38 (error 38) /proc/bus/usb/001/002 test 26 -- 38 (error 38) /proc/bus/usb/001/002 test 27 -- 38 (error 38) /proc/bus/usb/001/002 test 28 -- 38 (error 38) /proc/bus/usb/001/002 test 29 -- 38 (error 38) Thanks -- This message was sent on behalf of [EMAIL PROTECTED] at openSubscriber.com http://www.opensubscriber.com/message/linux-usb-devel@lists.sourceforge.net/3652159.html - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ linux-usb-devel@lists.sourceforge.net To unsubscribe,
Re: [linux-usb-devel] Error with testusb
On Mon, Aug 07, 2006 at 12:58:36PM +0800, [EMAIL PROTECTED] wrote: Hi all, I have a problem when using testusb, please help me to solve this. Here is log: [EMAIL PROTECTED] misc]# cat /proc/bus/usb/devices T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 3 Spd=480 MxC h= 0 D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=067b ProdID=2517 Rev= 0.01 S: Manufacturer=USB 2.0 Flash Disk S: Product=USB Mass Storage Device C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=05 Prot=50 Driver =usb-storage E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms [EMAIL PROTECTED] misc]# insmod usbtest.ko vendor=0x067b product=0x2517 [EMAIL PROTECTED] misc]# lsmod |grep usb usbtest24844 0 usb_storage 104592 1 scsi_mod 131980 2 sd_mod,usb_storage Why are you trying to run usbtest on a usb storage device that is already bound to the usb-storage driver? That doesn't bode well... Try using the proper type of device for this. good luck, greg k-h - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
