> Using special udev rules for special devices (in conjunction with the > oFono auto-detection rule) make the process of setting up oFono for the > system integrator a lot simpler. No manual configuration file patching > anymore. Just installation of an additional udev rule. > > The open here is the ISI modem detection, but this should be clearly > done via a Phonet plugin. And also the N900 specific case inside > modemconf is just wrong. This needs to be fixed and just auto-detected > via Phonet or maybe just via RTNL directly. What about old style serial port modems? How can we configure them if you remove modemconf?

What about dual mode modems that with two different serial ports? e.g. a modem support both GSM and CDMA, there is a serial port For GSM, and there is a serial another for CDMA. Why not keep both udev and modemconf plug-in. It remains for the user To decide which way to use. I think maybe we can change the compile Scrips, let user to select which plug-in to use.

>> What about dual mode modems that with two different serial ports? >> e.g. a modem support both GSM and CDMA, there is a serial port >> For GSM, and there is a serial another for CDMA. >> >> >> Why not keep both udev and modemconf plug-in. It remains for the user >> To decide which way to use. I think maybe we can change the compile >> Scrips, let user to select which plug-in to use. > >I don't even see a problem with this at all. Every serial port is >present in udev, so you can write proper udev rules for it. A modem with >a serial port for GSM and another one CDMA will be just presented as two >modems inside oFono. So no problem at all. > >So modemconf plugin will be removed since it is not needed at all. The >only component that needs it is the phonesim plugin. And that will get >its own configuration file. Can we just add some code in phonesim to make it look like a pseudo serial device which can be managed by udev? That is, if we start the phonesim, it will simulate some tty ports under /dev and udevd will inform the oFono there is a new device (We need some rule for phonesim). And the device disappears if phonesim meets an end. Maybe this is possible if we can send message to udevd the same way as kernel via netlink.

> a gentle reminder that this mailing list doesn't allow top > posting, please follow the netiquette for open source mailing lists. > > > What about dual mode modems that with two different serial ports? > > e.g. a modem support both GSM and CDMA, there is a serial port For > > GSM, and there is a serial another for CDMA. > > > > > > Why not keep both udev and modemconf plug-in. It remains > for the user > > To decide which way to use. I think maybe we can change the compile > > Scrips, let user to select which plug-in to use. > > I don't even see a problem with this at all. Every serial > port is present in udev, so you can write proper udev rules > for it. A modem with a serial port for GSM and another one > CDMA will be just presented as two modems inside oFono. So no > problem at all. > Udev really can work, but in many embedded devices,udev service is being forbidden because of boot-up speed issue. In addtion, on these devices, device nodes are often explictly defined.

> The open here is the ISI modem detection, but this should be clearly > done via a Phonet plugin. And also the N900 specific case inside > modemconf is just wrong. This needs to be fixed and just auto-detected > via Phonet or maybe just via RTNL directly. Once we get proper n900modem driver tested and integrated, the isimodem stuff can be removed, too.