Hi! > > My notes say: > > > > /dev/motmdm1 -- basic support, calls, on/off > > > > /dev/motmdm3 -- send sms interface > > > > /dev/motmdm9 -- receive sms interface > > > > > > (and gsmtty numbering is same) > > Yes I have not had a chance to look at these for several months now, > but have the latest set in droid4-pending-v5.10 branch in my github > tree. > > The gnss device is at /dev/gsmtty6, see the current droid4-agps tool > to upload the almanac also on github. That's has turned out to be a > pretty good gsm serdev test too :)
Thanks a lot for the info! Is it this one? https://github.com/tmlind/droid4-agps . GPS worked for me even w/o AGPS support, but I broke even that, so I need to fix that first. > > For now I converted gnss driver to use serdev interface, and n_gsm to > > provide it... Not yet finished but I believe I'm walking in the right > > direction. > > Great, sounds good to me if you got things working with just serdev > calls :) I'll try to take a look at this stuff again after I have > the other pending droid4 issues out of the way like v5.12 charger > and keyboard stuff. Just ask for latest code :-). I still believe I'm going right direction, but now I understand why you did it the way you did. Sound code needs to listen on gsmtty1, with the data still being provided for userspace. Best regards, Pavel -- http://www.livejournal.com/~pavelmachek
signature.asc
Description: PGP signature
