On Wed, 2002-08-14 at 21:17, Greg KH wrote: > /sbin/hotplug gets run when the device is plugged in. But the minor > number isn't being passed to it (yet...for 2.5 we're working on it...)
Yes, /sbin/hotplug is called with the id but not the minor number. So I do not know how can I make a program open the new serial port on 2.4. > If you're using 2.5 you can look in the /proc/tty/driver/usb-serial file > to get the minor number for your device. Or you can parse the kernel > log entries (not exactly the nicest way, I know...) Using 2.4:( Parsing the kernel log entries seems possible for 2.4 as well. /sbin/hotplug knows the following info: DEVICE=/proc/bus/usb/001/005 PRODUCT=f94/1/200 dmesg shows me: hub.c: USB new device connect on bus1/1, assigned device number 5 usbserial.c: FTDI 8U232AM converter detected usbserial.c: FTDI 8U232AM converter now attached to ttyUSB1 (or usb/tts/1 for devfs) So I will know that the new device number 5 is ttyUSB1 and open that. Right? > And are you sure that your modem will work with the ftdi_sio driver? I can send AT commands and get the response and I can use minicom. I do not have a dialup account at the moment so I cannot test that, but I guess that if AT commands work, the modem works, right? Thanks Trevor ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
