From: morphis@gravedo.de
To: ofono@ofono.org
Subject: Re: Palm Pre modem plugin
Date: Sun, 22 Nov 2009 21:47:44 +0100 [thread overview]
Message-ID: <20091122204744.GA4141@nirvana> (raw)
In-Reply-To: <1258899687.8454.19.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1856 bytes --]
On Sun, Nov 22, 2009 at 03:21:27PM +0100, Marcel Holtmann wrote:
> Hi Andrzej,
>
> > > I am currently working on the implementation of
> > > the basics I found out about the protocol. I split the whole code into
> > > two projects: msmcommd and libmsmcomm. msmcommd is a daemon which does
> > > all the link layer protocol handling which is required to speak probably
> > > with the modem. The library libmsmcomm is an easy utilitiy to format
> > > the different messages type and decode them on receive.
> > >
> > > The link layer part is nearly done. Establishment of a link should work
> > > and on the handling of sending and receiving data I am currently
> > > working.
> > >
> > > When libmsmcomm and msmcommd are done I have the plan to open from
> > > fsogsmd a network channel to msmcommd and send all my telephony commands
> > > to msmcommd whichs put them into link layer frames and sends them to the
> > > modem.
> >
> > I like the idea of libmsmcomm as a library, this means it may be easy
> > in the future to make an oFono plugin linked against the library. I
> > don't think having a separate daemon and another communication channel
> > between what is eventually a dialer or sms app, and the modem is such
> > a good idea (with the D-Bus socket, D-Bus daemon, FSO and serial
> > driver already there)
>
> I do think that a native integration directly into the oFono source code
> as msmmodem might be better. However the second daemon solution is
> stupid and causes too much overhead.
>
> Also I did look into the QMI stuff a little bit and I think we might
> have to actually create a QMI subsystem in the Linux kernel like we have
> for Phonet since with USB the network interface and the management
> interface do share endpoints as far as I can tell so far.
Whats QMI? Never heard about it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-11-22 20:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 11:45 Palm Pre modem plugin morphis
2009-11-20 13:17 ` andrzej zaborowski
2009-11-21 10:14 ` morphis
2009-11-21 19:29 ` andrzej zaborowski
2009-11-22 14:21 ` Marcel Holtmann
2009-11-22 20:47 ` morphis [this message]
2009-11-22 22:56 ` Marcel Holtmann
2009-11-20 13:28 ` Marcel Holtmann
2009-11-21 10:17 ` morphis
2009-11-21 10:33 ` Marcel Holtmann
2009-11-21 11:05 ` morphis
2009-11-21 18:12 ` Marcel Holtmann
2009-11-21 19:47 ` Nicola Mfb
2009-11-20 13:08 ` Denis Kenzior
2009-11-22 14:24 ` Marcel Holtmann
2009-11-22 14:38 ` Nicola Mfb
2009-11-23 8:14 ` Marcel Holtmann
2009-11-23 10:40 ` Denis Kenzior
2009-11-23 11:02 ` oFono running on new Freerunner distribution (was: Palm Pre modem plugin) DJDAS
2009-11-23 11:11 ` Denis Kenzior
2009-11-23 11:23 ` oFono running on new Freerunner distribution DJDAS
2009-11-23 11:37 ` Denis Kenzior
2009-11-23 11:43 ` DJDAS
2009-11-23 15:20 ` DJDAS
2009-11-23 21:05 ` Denis Kenzior
2009-11-24 1:58 ` Denis Kenzior
2009-11-26 10:15 ` DJDAS
2009-11-26 13:44 ` Denis Kenzior
2009-11-27 16:33 ` DJDAS
2009-11-26 14:16 ` Denis Kenzior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091122204744.GA4141@nirvana \
--to=morphis@gravedo.de \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox