Re: ezxd changes.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: Koen Kooi wrote: gsmd sadly expects a character device, how can we hook ezxd up to gsmd? And does it fake ATZ already? See http://blogs.gnome.org/thos/2007/10/30/turning-the-neo1973-into-an-expensive-external-gsm-modem/

Re: ezxd changes.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Koen Kooi wrote: gsmd sadly expects a character device, how can we hook ezxd up to gsmd? And does it fake ATZ already? See http://blogs.gnome.org/thos/2007/10/30/turning-the-neo1973-into-an-expensive-external-gsm-modem/ Thanks to o-hand/OpenMoko!

Re: ezxd changes.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: Hi. Targeting quick integration with gsmd, i changed ezxd to act as an AT command proxy and hijacker. Here is an example ezxd session with the last revision: [snip] gsmd sadly expects a character device, how can

Re: ezxd changes.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Koen Kooi wrote: gsmd sadly expects a character device, how can we hook ezxd up to gsmd? In an ideal world, we would ask gsmd developers about a clean way of doing the integration, or even better, our needs would be included in a gsmd plugin

ezxd changes.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. Targeting quick integration with gsmd, i changed ezxd to act as an AT command proxy and hijacker. Here is an example ezxd session with the last revision: [EMAIL PROTECTED]:~/openezx/ezxd$ nc ezx 7100 AT OK AT+EBTP=0 OK AT+EBTP? +EBTP: 0