[PATCH] hayes-ril: rename LOGD/E macros to ALOGD/E
contact at paulk.fr
Sat Apr 12 18:08:35 UTC 2014
Le samedi 12 avril 2014 à 19:43 +0200, Dr. H. Nikolaus Schaller a
> Am 12.04.2014 um 17:23 schrieb Paul Kocialkowski:
> > I understand the necessity for this, though I want master to work on any
> > Replicant version, so this won't do.
> > I think the best way to do it is what I did on Samsung-RIL:
> > https://gitorious.org/replicant/hardware_ril_samsung-ril/commit/c8408cd2c116b0b99a399282032b6607a1318b84
> > Note that I'm not going to work on Hayes-RIL for some time, because I
> > want to focus on other things first. Hayes-RIL perhaps needs some rework
> > and is far from complete to this day. I'm basically working on rewriting
> > Samsung-RIL (since a few months already) and I'll probably use some of
> > the new concepts introduced there in Hayes-RIL.
> > In the future, I'll need Hayes-RIL to work for many different devices:
> > * GTA04
> > * Allwinner tablets, that also have option modems apparently
> > * XMM626 that uses AT (every XMM626 except the ones on Samsung devices)
> maybe we should add Neo900 and Pyra handheld. They will use the
> Gemalto/Cinterion PHS8 modules. But generally the command set of the
> GTM601 and PHS8 are quite similar. Details differ in command and
> paramter naming and format of the responses.
Is this for the generic AT commands too or only the extensions?
Normally, all the small differences will be handled with flags declared
for each device. I'm not sure it's already in place in the current
Hayes-RIL (I've rewritten it from scratch like 2 or 3 times), but it'll
be when I'll be back working on it.
> The main difference in Linux is that there is a HSO driver for the
> OPTION modules which already does multiplexing of the multiple tty
> channels and presents the PPP port as a normal network interface. For
> the PHS8 we have to do that separately and run a PPP daemon.
Good to know.
> BTW: I had asked a while ago about a RIL for the OPTION modem - they
> said it exists but we can buy a binary blob at a four to five digit
> amount. I.e. that is not likely that we want it.
Indeed, that seems quite ridiculous for implementing a protocol that's
publicly documented. I was however quite surprised to see that there was
no quality AT RIL implementation. Every free RIL was basically a quick
hack over the reference Android RIL, which handles AT in the worst
possible way and gives no flexibility at all.
Paul Kocialkowski, Replicant developer
Replicant is a fully free Android distribution
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: This is a digitally signed message part
More information about the Replicant