Re: serial connections
2008/4/29 Dan Williams <[EMAIL PROTECTED]>: > > On Mon, 2008-04-28 at 22:57 +0400, Vitja Makarov wrote: > > I looked now at cdc-acm and found that some devices define cdc acm > > proto subclass that could be one of: > > > > - V25TER (my phone has this) > > - PCCA101 > > - PCCA101-WAKE > > - GSM > > - 3G > > - CDMA > > > > I think this could be added to hal-info to provide device info. > > But my phone is definitely GSM, I don't know anout .V25ter, > > but it seems to be not only GSM modem. > > > > In case of modem devices that could be possible to use dynamic probing: > > > > my phone says this: > > < AT+GCAP > > > +GCAP: +CGSM,+DS,+W > > > > But in case of all other chips such as cp2101, ftdio_sio, cypress_m5 and > so on, > > that should be bad idea to probe them. I not very familar with mobile > phones, > > but I have a wild guess that they all CDC_ACM modems, and that should be > > very good. > > > > Btw HAL could get some info based on USB info, and if unsure try to > > probe the device. > > Isn't that a good idea? > > Right, there should still probably be .fdi files that specify whether to > probe the port or not. Or, invert the check and probe everything > _except_ what's listed in the .fdi file. But probing devices that we > want to know about is the way to go. > > Dan > I've posted patch to hal and here, that tries to probe CDC modems. It uses callouts mechanism that it should be easy to specify which one to probe right in .fdi. I found one probelem with old discharged ubiq phone. When it boots(PC is charger) it first appear as usb device, and only after few(~1.5) minutes gives replies. vitja. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: serial connections
On Mon, 2008-04-28 at 22:57 +0400, Vitja Makarov wrote: > I looked now at cdc-acm and found that some devices define cdc acm > proto subclass that could be one of: > > - V25TER (my phone has this) > - PCCA101 > - PCCA101-WAKE > - GSM > - 3G > - CDMA > > I think this could be added to hal-info to provide device info. > But my phone is definitely GSM, I don't know anout .V25ter, > but it seems to be not only GSM modem. > > In case of modem devices that could be possible to use dynamic probing: > > my phone says this: > < AT+GCAP > > +GCAP: +CGSM,+DS,+W > > But in case of all other chips such as cp2101, ftdio_sio, cypress_m5 and so > on, > that should be bad idea to probe them. I not very familar with mobile phones, > but I have a wild guess that they all CDC_ACM modems, and that should be > very good. > > Btw HAL could get some info based on USB info, and if unsure try to > probe the device. > Isn't that a good idea? Right, there should still probably be .fdi files that specify whether to probe the port or not. Or, invert the check and probe everything _except_ what's listed in the .fdi file. But probing devices that we want to know about is the way to go. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: serial connections
I looked now at cdc-acm and found that some devices define cdc acm proto subclass that could be one of: - V25TER (my phone has this) - PCCA101 - PCCA101-WAKE - GSM - 3G - CDMA I think this could be added to hal-info to provide device info. But my phone is definitely GSM, I don't know anout .V25ter, but it seems to be not only GSM modem. In case of modem devices that could be possible to use dynamic probing: my phone says this: < AT+GCAP > +GCAP: +CGSM,+DS,+W But in case of all other chips such as cp2101, ftdio_sio, cypress_m5 and so on, that should be bad idea to probe them. I not very familar with mobile phones, but I have a wild guess that they all CDC_ACM modems, and that should be very good. Btw HAL could get some info based on USB info, and if unsure try to probe the device. Isn't that a good idea? vitja. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: serial connections
On Mon, 2008-04-28 at 09:06 +0300, Antti Kaijanmäki wrote: > ma, 2008-04-28 kello 09:52 +0400, Vitja Makarov kirjoitti: > > 2008/4/28 Antti Kaijanmäki <[EMAIL PROTECTED]>: > > > Hi, > > > > > > ma, 2008-04-28 kello 09:16 +0400, Vitja Makarov kirjoitti: > > > > > > > Hi! > > > > > > > > Will it be possible to manually specify serial interface for broadband > > > > connection, as well as its type. > > > > I don't think hal could take care of all the mobile phones. It > > > > couldn't guess what is attached to RS-232 port which could be > > > > still used. That should make bluethooth integration easy. > > > > > > atleast my assistant will have an option to specify an arbitrary path > > > for serial interface. And naturally I want to see NetworkManager > > > supporting this also. > > > > > > > > > > What is the right way to go? > > > > > > IMHO, Bluetooth binding should be left to BlueZ to handle. > > > NetworkManager would pass a binding request over D-BUS to BlueZ and > > > BlueZ would return the path to the correct char device under /dev/.. > > > > > > > I was thinking about using bluez dbus-interface or AF_BLUETOOTH > > sockets that doesn't make sens now. > > May be serial device should be created for all serial interfaces and > > hals modem command set info will be just a hint, not the rule? > > > > Then it will be possible to add nm-bluetooth-device that will create > > nm-serial-device on demand. > > Yes, Bluetooth device might be just floating around without being used > and the binding should be done only when necessary. Right, NM will only ask Bluez to connect to the device when you explicitly tell NM to connect. We can't scan for devices, because that takes too much power and is interrupts other BT communications because it takes so long to scan. > > That should be pretty well to bind profiles to serial device you may > > have two phones with different operators, > > both GSM, also you may only change your SIM-card. > > The way I see it is that Bluetooth devices are identified only using BT > MAC. If user has multiple SIMs he must have a configuration for every > different operator and choose the appropriate configuration for the SIM > that is in the phone. Right; if you have multiple Connections defined for a single phone (identified by the BT MAC) they will show up associated with the phone, and you get to choose one to connect with. If you don't have the right SIM in the phone, the connection should just error out and tell you that the Connection you've tried doesn't match the settings in the device, or something like that. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: serial connections
On Mon, 2008-04-28 at 09:16 +0400, Vitja Makarov wrote: > Hi! > > Will it be possible to manually specify serial interface for broadband > connection, as well as its type. > I don't think hal could take care of all the mobile phones. It > couldn't guess what is attached to RS-232 port which could be > still used. That should make bluethooth integration easy. The right way to go is still to teach HAL about what each of the cards supports. That can be through static tagging like we do now, or inspecting serial ports that come up and issuing AT+GCAP to figure out if (a) anything is on that port, and (b) what capabilities the device supports. Your phone _must_ support AT+GCAP, since that's part of both the IS-707-A and GSM-07.07 standards. Therefore we can dynamically detect them, but that detection should be in _one_ place, and that place is HAL. We certainly don't want all of NM, umtsmon, comgt, and VMC trying to do this, because to talk to the card you need exclusive access, and then everyone just races to get it. So the path forward is to make HAL aware of the capabilities of the devices you've just plugged in. Bluetooth integration will be somewhat different. You'll tell NM about the phones you've got, what their BT MAC is, and the connection details. This will likely be through some sort of Wizard, along the same lines as Antti is working on for mobile broadband. You'll always see the phones you have connections for in the menu, as long as your BT controller is plugged in an turned on. When you select your phone, NM will ask Bluez to connect to the device, then ask Bluez to create the rfcomm port, and then use the rfcomm port to do PPP. You shouldn't ever need to specify the actual serial port to be used. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: serial connections
ma, 2008-04-28 kello 09:52 +0400, Vitja Makarov kirjoitti: > 2008/4/28 Antti Kaijanmäki <[EMAIL PROTECTED]>: > > Hi, > > > > ma, 2008-04-28 kello 09:16 +0400, Vitja Makarov kirjoitti: > > > > > Hi! > > > > > > Will it be possible to manually specify serial interface for broadband > > > connection, as well as its type. > > > I don't think hal could take care of all the mobile phones. It > > > couldn't guess what is attached to RS-232 port which could be > > > still used. That should make bluethooth integration easy. > > > > atleast my assistant will have an option to specify an arbitrary path > > for serial interface. And naturally I want to see NetworkManager > > supporting this also. > > > > > > > What is the right way to go? > > > > IMHO, Bluetooth binding should be left to BlueZ to handle. > > NetworkManager would pass a binding request over D-BUS to BlueZ and > > BlueZ would return the path to the correct char device under /dev/.. > > > > I was thinking about using bluez dbus-interface or AF_BLUETOOTH > sockets that doesn't make sens now. > May be serial device should be created for all serial interfaces and > hals modem command set info will be just a hint, not the rule? > > Then it will be possible to add nm-bluetooth-device that will create > nm-serial-device on demand. Yes, Bluetooth device might be just floating around without being used and the binding should be done only when necessary. > That should be pretty well to bind profiles to serial device you may > have two phones with different operators, > both GSM, also you may only change your SIM-card. The way I see it is that Bluetooth devices are identified only using BT MAC. If user has multiple SIMs he must have a configuration for every different operator and choose the appropriate configuration for the SIM that is in the phone. -- Antti > vitja. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: serial connections
2008/4/28 Antti Kaijanmäki <[EMAIL PROTECTED]>: > Hi, > > ma, 2008-04-28 kello 09:16 +0400, Vitja Makarov kirjoitti: > > > Hi! > > > > Will it be possible to manually specify serial interface for broadband > > connection, as well as its type. > > I don't think hal could take care of all the mobile phones. It > > couldn't guess what is attached to RS-232 port which could be > > still used. That should make bluethooth integration easy. > > atleast my assistant will have an option to specify an arbitrary path > for serial interface. And naturally I want to see NetworkManager > supporting this also. > > > > What is the right way to go? > > IMHO, Bluetooth binding should be left to BlueZ to handle. > NetworkManager would pass a binding request over D-BUS to BlueZ and > BlueZ would return the path to the correct char device under /dev/.. > I was thinking about using bluez dbus-interface or AF_BLUETOOTH sockets that doesn't make sens now. May be serial device should be created for all serial interfaces and hals modem command set info will be just a hint, not the rule? Then it will be possible to add nm-bluetooth-device that will create nm-serial-device on demand. That should be pretty well to bind profiles to serial device you may have two phones with different operators, both GSM, also you may only change your SIM-card. vitja. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: serial connections
Hi, ma, 2008-04-28 kello 09:16 +0400, Vitja Makarov kirjoitti: > Hi! > > Will it be possible to manually specify serial interface for broadband > connection, as well as its type. > I don't think hal could take care of all the mobile phones. It > couldn't guess what is attached to RS-232 port which could be > still used. That should make bluethooth integration easy. atleast my assistant will have an option to specify an arbitrary path for serial interface. And naturally I want to see NetworkManager supporting this also. > What is the right way to go? IMHO, Bluetooth binding should be left to BlueZ to handle. NetworkManager would pass a binding request over D-BUS to BlueZ and BlueZ would return the path to the correct char device under /dev/.. -- Antti > vitja. > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
serial connections
Hi! Will it be possible to manually specify serial interface for broadband connection, as well as its type. I don't think hal could take care of all the mobile phones. It couldn't guess what is attached to RS-232 port which could be still used. That should make bluethooth integration easy. What is the right way to go? vitja. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
