Antti Kaijanmäki: Your comments do make sense. I'd been thinking in terms of distinguishing GSM/CDMA devices from generic serial devices, rather than considering that some GSM/CDMA devices, while supported by option/airprime/etc, might not be capable of GPRS/EDGE/HSDPA Internet access.
In that context it does seem right to identify specific devices in HAL. There will need to be a howto for users, though, probably in the form of a URL to the community wiki in the help pages. I do think there will be issues with some laptop vendors (Dell, for example) that rebrand all their hardware. Still, with some decent user documentation so users know how to find out their device IDs and submit them it should be alright. By the way, I had a go at modifying option.c to accept a user-supplied USB vendor/product ID. It's not at all difficult; just leave an extra empty entry in the module table before the terminator, check the module arguments, and populate it if they're set, just like the generic serial driver does. However, it requires the option driver to ask to see every attached USB device rather than letting the kernel select automatically based on the exported module table. I doubt the kernel folks would be too enthusiastic about every USB serial module having to be poked for every USB device insert ... just on the off chance it's an as-yet- unknown device the user has told one of the modules about. So, rather than adding vendor= and product= parameters to every driver, I now think it's better to make sure that NetworkManager works properly with the generic USB serial device. That way the user can just drop a HAL .fdi file (edited from a template on, say, the community wiki) into /etc/hal/fdi to tell HAL their device is a modem. To get the kernel to recognise it they'd add something to /etc/modprobe.d like: install 3g modprobe usbserial vendor=0x413c product=0x8138 Slightly more cumbersome than just loading option.c with vendor and product args, but that'd only really be easier if NM could assume that all devices using the option driver were modems. It can't, so we still need the FDI file, and we might as well use the generic USB serial driver until the next kernel update is released with the new device IDs. Sound sensible? BTW - testing probe branch now. -- MASTER Network Manager should probe for GSM and CDMA command sets. It doesnt detect 3g modems with serial capability only in hal https://bugs.launchpad.net/bugs/268095 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
