On Fri, 25 Jun 2010 14:03:59 +0200 "Dr. Michael Lauer" <mic...@vanille-media.de> wrote:
> Hi Antonio, > > thanks for this patch – excellent work! > still a long way to go, but thanks! > > 1. sending +EPOM to power on the modem on gen2 device: I am now doing this > > in the lowlevel plugin because I was not able to do that in modem at > > INITIALIZING time, when using a script like this: > > > > http://git.ao2.it/fso-scripts.git/?a=blob;f=fso-auth.py;h=0fc26f98f7f31a414c46dbfc8e6d27ba3e3f8a77 > > what happened was that +CPIN? was issued before +EPOM completion and so > > +CPIN? was returning an error. > > Are there any time constraints wrt. opening the MUX nodes and sending +EPOM? > If not, +EPOM should be sent as modem initialization command; I have to > investigate > why it collides with channel init commands, that should not happen. > There are no such constraints TTBOMK, the only problem i can see here is that init commands can overlap with other ones, take this sequence: usage_iface.RequestResource("GSM") gsm_sim_iface.GetAuthStatus() the +CPIN from the second command can be sent before the init sequence is complete. All this is relevant for gen2 phones only tho, as +EPOM is not needed on gen1. > > 2. putting mux nodes names in config files instead of hardcoding them, for > > both modem and lowlevel plugin. How can I do that for multiple nodes? > > Hardcoding it not that much of a problem for device-specific plugins. If you > want though, > you can use the advanced SmartKeyFile functions for gathering a list of > key/value pairs > (if you want to map it to multiple entries) or just a list of values (if you > want to map > it to x=a,b,c,d,e). > I will try using the config file as you suggested, if we decide to experiment with other mux drivers (there is going to be one in 2.6.35 from Alan Cox) having device nodes names in a config file is a little handier. > > 3. the use of modem_data.simHasReadySignal = true; I copied it from > > modem_ti_calipso, but I still don't understand it fully, should we use that > > for modem_freescale_neptune? > > Many modems read the SIM contents (elementary files) to internal DRAM to > cache the _very_ slow SIM access (just a couple of bits per second). If you > do any SIM access before this happens, you will get +CME errors. Some modems > have an URC to notify when the initial caching process has been done, so you > can start accessing the SIM. I don't recall if EZX has such an URC or not. > Thanks for the explanation, I am leaving this out for now, as I don't know if such a mechanism exists on EZX either. > > I hope someone will be able to actually test these patches and send some > > feedback > > On brief look, the changes look ok apart from some styling and one or two > questionable > things. I will comment in detail; however I first want to see the current > status > on my own phone. > I am waiting for the detailed remarks. > I'll get back to you on #openezx so we can walk me through the update ;) > > Thanks again, very impressive stuff, i'm glad you worked on that! > > :M: > For the audio part in cornucopia I am counting on your _heavy_ collaboration :) Thanks, Antonio -- Antonio Ospite http://ao2.it PGP public key ID: 0x4553B001 A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
pgp3lFr7j0nat.pgp
Description: PGP signature
_______________________________________________ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
