I finally tried moving to test4 (from about halfway between test3 and
test4) last night.  I had to drop back, though, because I was unable
to get my acm modem to work.

/proc/devices had the '166 ttyACM' entry in the char section, the
devices existed in /dev as 'c 166 x' for each x in [0..255], but
attempts to open the specials gave Invalid argument errors -- the
same error you get when nothing is connected to that acm special.

Dmesg shows:

##############
drivers/usb/class/cdc-acm.c: need inactive config #2
drivers/usb/class/cdc-acm.c: need inactive config #2
###############

That corresponds to this change in cdc-acm.c:

##############
--- a/drivers/usb/class/cdc-acm.c  2003-08-11 00:41:48 -0400
+++ b/drivers/usb/class/cdc-acm.c  2003-08-30 04:30:57 -0400
@@ -596 +596,8 @@
-                       usb_set_configuration(dev, cfacm->desc.bConfigurationValue);
+                       /* FIXME don't scan every config. it's either correct
+                        * when we probe(), or some other task must fix this.
+                        */
+                       if (dev->actconfig != cfacm) {
+                               err("need inactive config #%d",
+                                       cfacm->desc.bConfigurationValue);
+                               return -ENODEV;
+                       }
##############

That is part of:

http://linux.bkbits.net:8080/linux-2.5/[EMAIL PROTECTED]


I cannot tell whether the latest patch to cdc-acm.c in the
linuxusb.bkbits.net/usb-2.5 tree is relevant (file revision
1.65 in that tree, 'Another bad audit in drivers/usb/*').
It is the only change since David's change above was made.

I will try reversing that for now; is there a more correct solution?

-JimC



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to