Hi! And thanks for a quick replies.
> >There's qmi and "normal" (but very buggy) AT interface on
> >them. Unfortunately that uses USB and uses too much power (which is a
> >problem on phone).
> >
> >Plus there's /dev/motmdm1, motmdm3 and motmdm9, multiplexed over
> >serial line.
>
> Kernel 27.010 multiplexer or something else entirely?
Kernel 27.010 multiplexer, AFAICT. Some of the endpoints are handled
in kernel (gps, audio mixer control).
> >Other major difference is that commands need to be sent to the right
> >device. It seems motmdm1 is for status and call control, and motmdm9
> >is for incoming sms.
> >
> >I guess that right way to do this is to introduce
> >drivers/motorolamodem (or can we just have drivers/motorola?).
>
> For some weird historic reason we called the atom drivers and thus the
> subdirectory housing the relevant sources with the 'modem' suffix. So I
> guess we should stick to that just to be consistent.
Ok.
One more question: I guess I'll need to implement this... Is there
another example of driver doing AT commands but on multiple file
descriptors? I could really use something to look at as a template..
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
signature.asc
Description: Digital signature
_______________________________________________ ofono mailing list [email protected] https://lists.ofono.org/mailman/listinfo/ofono
