pHilipp Zabel philipp.zabel at gmail.com
Thu Aug 16 12:42:23 CEST 2007

On 8/15/07, Harald Welte <laforge at openmoko.org> wrote:
> On Mon, Aug 13, 2007 at 01:40:05AM -0300, Daniel Ribeiro wrote:
> > Im planning on writing an ezx plugin to gsmd, and need some advice...
> >
> > On ezx, we have a lot of extended AT commands that are not GSM
> > related, commands to power on/off the bluetooth chip; to get the
> > BDADDR; set wake-up events (to turn the phone on at a specified time);
> > to properly turn off the device; to inform usb cable state; and even
> > key press events.
> Some of them I know, some others are new to me (usb cable state).
> I think those should be implemented
> > Also, our baseband is connected via usb, and our( your ;) ) driver
> > provides 5 char devices which responds to different sets of AT
> > commands.
> different, as in different devices, yes.  Different AT command set
> between those devices?  That's the first time I hear about this.
> Also, I still have the goal to have one unified GSM multiplexer driver
> in the kernel, supporting the various dialects (07.10 basic/advanced,
> motorolas strange version of it, etc.) and the various physical
> interfaces (real serial port, motorolas usb interface, ...).  However,
> that will probably hve to wait for quite some time...
> > Does gsmd support (or can be extended to) meet these requirements? Or
> > should i write a separate daemon for the system stuff and let gsmd
> > care only about gsm?
> I think much of this would actually be implemented in a client process
> to gsmd.  You can use the passthrough mechanism to do things that are
> completely unrelated to a normal gsm mode, such as obtaining the
> bluatooth address, set clock/timer/...

I'd be interested in this, too - although for my phone it's only
AT+CVOL to control the voice call volume for now.


More information about the gsmd-devel mailing list