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

Re: Preparing discussion with gsmd developers.

Hi Antonio If we (read _not_me_ :)) manage to make it work well, we can think to use its non-muxed mode for gsmd for the time being, so to start doing b. (see previous messages). This will prevent us to have gps on a780, so it is not ideal. When gsmd will support muxed devices we

Re: [patch] gsmd mux

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Rayner wrote: Hi This patch adds 27.010 mux support to gsmd svn diff compared to revision 3304 openmoko svn This code needs to be used with a mux line discipline, based on openezx code, to be sent next Hi Jim, Does your code

Re: Preparing discussion with gsmd developers.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Rayner wrote: Note you will still need to use the ezx ldisc rather than the one I have posted to OM since I've stripped out the Moto extensions. I will try to fix the oops that Antonio reported is happening on your driver, and replace our