Re: Preparing discussion with gsmd developers.
Hi Antonio If we (read _not_me_ :)) manage to make it work well, we can think to use its non-muxed mode for gsmd for the time being, so to start doing b. (see previous messages). This will prevent us to have gps on a780, so it is not ideal. When gsmd will support muxed devices we will use also gps, still clumsy? As part of some current work I plan to submit some patches to gsmd, one of them being addition of mux support. Oh well a bit little bit later than planned. I've finally been able to focus a few days on the patches and I've just submitted my gsmd mux patch to openmoko Note you will still need to use the ezx ldisc rather than the one I have posted to OM since I've stripped out the Moto extensions. Best regards, Jim
Re: Preparing discussion with gsmd developers.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Rayner wrote: Note you will still need to use the ezx ldisc rather than the one I have posted to OM since I've stripped out the Moto extensions. I will try to fix the oops that Antonio reported is happening on your driver, and replace our version with your code. Unfortunately i cant guarantee that i will be able to do it this weekend (other volunteers?). Thanks again for your help! :) - -- Daniel Ribeiro -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHJzy5w3OYl0G0liQRAo6kAJ4tvQeRHcotDTPtI1upv+BSwTNDjgCfTp5N SEZpMKTLPnj7k+GKc67CXZU= =udAQ -END PGP SIGNATURE-
Re: Preparing discussion with gsmd developers.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Antonio Ospite wrote: If we (read _not_me_ :)) manage to make it work well, we can think to use its non-muxed mode for gsmd for the time being, so to start doing b. (see previous messages). This will prevent us to have gps on a780, so it is not ideal. When gsmd will support muxed devices we will use also gps, still clumsy? I may be completely wrong, but i believe that a non-muxed mode cannot be implemented without changes to BP software. And what about GPRS? AFAIK GPRS uses a separate mux device too. I think it is much easier to change gsmd code to support our mux devices, than to change our kernel to spit data in the way that gsmd wants. - -- Daniel Ribeiro -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHChVrw3OYl0G0liQRAgbxAJ9nzKW2FbfQjpnwHyTLg2KZZu80VACePDkV IREsm54nhVObzN1uCKdKTqw= =k5EH -END PGP SIGNATURE-
Re: Preparing discussion with gsmd developers.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: 2007/10/4, Koen Kooi [EMAIL PROTECTED]: Daniel's suggestion of a named pipe that gsmd talks to and ezxd forwards to /dev/mux* would be the easiest thing to start with. Has anyone figured out how to reset the modem, since atz doesn't seem to be present? Yes, i think that an unix socket would be the easiest way-to-go for the A option. We can reset the modem in kernel space by asserting BB_RESET high for 1ms, but i think this is not what you want :) Any particular reason that requires the modem reset?? Or just because gsmd thinks that it should reset the modem? If the reset is *really* necessary, and there is no other way to do it via an AT command, we could have an ioctl for this task. gsmd hardcodes an ATZ, which is perfectly legal, but moto seems to have removed atz. since we're talking thru ezxd anyway, we can intercept that atz :) regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHBUXuMkyGM64RGpERAmbbAJwI5FLCwvuPSlZt9zwC0P0gJoCxYQCffCnr icf6vZpa1nzcoZqc+FjkUyE= =D4QN -END PGP SIGNATURE-
Re: Preparing discussion with gsmd developers.
On Thu, 27 Sep 2007 14:15:33 -0300 Daniel Ribeiro [EMAIL PROTECTED] wrote: 2007/9/27, Antonio Ospite [EMAIL PROTECTED]: I would like to summarize our ideas and needs about gsmd [...] So, please reply to this mail to comment, complete or correct what I wrote, so we can extract a text to send to gsmd-devel. I think that your email has all the points, we need to talk to Harald and other gsmd developers about the changes needed on gsmd for the B option, if they agree with the define custom AT commands inside a plugin then we should start working on the B option, otherwise, I cant see another way to have a full featured 'gsmd+system tasks' other than the A fallback. Ok, I'm writing to gsmd-devel adding the sentence about mux devices and unsolicited data. Ah, and we should get brave and think about some work on mux_cli itself, too. Having a much stable mux_cli driver on x86 can speedup gsmd _and_ gpsd integration a lot :) Bye, Antonio -- Web site: http://www.studenti.unina.it/~ospite Public key: http://www.studenti.unina.it/~ospite/aopubkey.asc pgpB2PMxi2hvh.pgp Description: PGP signature
Re: Preparing discussion with gsmd developers.
Hello. On Fri, 2007-09-28 at 11:22, Daniel Ribeiro wrote: Antonio Ospite wrote: Ah, and we should get brave and think about some work on mux_cli itself, too. Having a much stable mux_cli driver on x86 can speedup gsmd _and_ gpsd integration a lot :) I tried before, but never managed to get mux_cli compiled for x86. Can you point me on how to do it?? Did you apply this patch? (Its commented out in the series file) https://svn.openezx.org/trunk/src/kernel-2.6/patches/mux-ifdef-ezx-features.patch regards Stefan Schmidt signature.asc Description: Digital signature
Re: Preparing discussion with gsmd developers.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan Schmidt wrote: Did you apply this patch? (Its commented out in the series file) Guess not, i will try again this weekend. Thanks. :) - -- Daniel Ribeiro -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/YPvw3OYl0G0liQRAiH9AJ9rVF4i/G0O6GUtfB4ArcQytW2xLQCggVZS nOJ8rVGd2GS5DgHIrWMybq8= =1KN7 -END PGP SIGNATURE-
