* Re: Droid 4 modem support in kernel & ofono
@ 2019-02-07 22:17 ` Pavel Machek
0 siblings, 0 replies; 11+ messages in thread
From: Pavel Machek @ 2019-02-07 22:17 UTC (permalink / raw)
To: Tony Lindgren
Cc: ofono, kernel list, linux-arm-kernel, linux-omap, sre, nekit1000,
mpartap, merlijn
[-- Attachment #1: Type: text/plain, Size: 1847 bytes --]
Hi!
> > Ok, so I got calls and smses somehow working in kernel&ofono ... which
> > is really all I need.
>
> Nice :)
>
> I think the SIM card reading and writing should be doable
> using dlci10 /dev/motmdm10 for AT+CRSM calls..
Might be. Sorry, this is outside of my area of interest, because LTE
would not be on usable frequencies, anyway.
> > I pushed the tree to git@github.com:pavelmachek/ofono.git , branch
> > d4... But I had to do some "rather interesting" hacks. D4 modem
> > expects packets and current kernel drivers rely on write() boundaries
> > and flush(). .. which is a bit of problem for in ofonod, as it expects
> > to work with bytestream with no explicit packet boundaries.
> >
> > However D4 still uses normal AT commands, so... it would be good to be
> > able to use AT parsing framework in ofono.
> >
> > I believe easiest solution would be to automatically do the packet
> > splitting in kernel, it should be as easy as splitting on \r and
> > ^Z. (Currently packets are only generated when \r or ^Z is seen on
> > write boundary, but that does not work well for ofono).
>
> OK yeah it's worth trying. I hit that issue too with the
> flush needed for droid4-sms-tools scripts. And the traffic
> we're seeing is minimal and AFAIK there's no network port
> for ts27010. And SMS messages are PDU encoded anyways.
>
> Hmm should we do it for \r\n and \r? Otherwise the \n
> will be left out of the packet :)
I guess splitting on \n makes sense, yes.
Ofono normally uses just \r. Translating it to \r\n in kernel (ttys
already do that) would be super nice, but I think this is easy enough
to handle in ofono.
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Droid 4 modem support in kernel & ofono
@ 2019-02-07 22:17 ` Pavel Machek
0 siblings, 0 replies; 11+ messages in thread
From: Pavel Machek @ 2019-02-07 22:17 UTC (permalink / raw)
To: Tony Lindgren
Cc: mpartap, merlijn, sre, kernel list, nekit1000, ofono, linux-omap,
linux-arm-kernel
[-- Attachment #1.1: Type: text/plain, Size: 1847 bytes --]
Hi!
> > Ok, so I got calls and smses somehow working in kernel&ofono ... which
> > is really all I need.
>
> Nice :)
>
> I think the SIM card reading and writing should be doable
> using dlci10 /dev/motmdm10 for AT+CRSM calls..
Might be. Sorry, this is outside of my area of interest, because LTE
would not be on usable frequencies, anyway.
> > I pushed the tree to git@github.com:pavelmachek/ofono.git , branch
> > d4... But I had to do some "rather interesting" hacks. D4 modem
> > expects packets and current kernel drivers rely on write() boundaries
> > and flush(). .. which is a bit of problem for in ofonod, as it expects
> > to work with bytestream with no explicit packet boundaries.
> >
> > However D4 still uses normal AT commands, so... it would be good to be
> > able to use AT parsing framework in ofono.
> >
> > I believe easiest solution would be to automatically do the packet
> > splitting in kernel, it should be as easy as splitting on \r and
> > ^Z. (Currently packets are only generated when \r or ^Z is seen on
> > write boundary, but that does not work well for ofono).
>
> OK yeah it's worth trying. I hit that issue too with the
> flush needed for droid4-sms-tools scripts. And the traffic
> we're seeing is minimal and AFAIK there's no network port
> for ts27010. And SMS messages are PDU encoded anyways.
>
> Hmm should we do it for \r\n and \r? Otherwise the \n
> will be left out of the packet :)
I guess splitting on \n makes sense, yes.
Ofono normally uses just \r. Translating it to \r\n in kernel (ttys
already do that) would be super nice, but I think this is easy enough
to handle in ofono.
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Droid 4 modem support in kernel & ofono
@ 2019-02-07 22:17 ` Pavel Machek
0 siblings, 0 replies; 11+ messages in thread
From: Pavel Machek @ 2019-02-07 22:17 UTC (permalink / raw)
To: ofono
[-- Attachment #1: Type: text/plain, Size: 1849 bytes --]
Hi!
> > Ok, so I got calls and smses somehow working in kernel&ofono ... which
> > is really all I need.
>
> Nice :)
>
> I think the SIM card reading and writing should be doable
> using dlci10 /dev/motmdm10 for AT+CRSM calls..
Might be. Sorry, this is outside of my area of interest, because LTE
would not be on usable frequencies, anyway.
> > I pushed the tree to git(a)github.com:pavelmachek/ofono.git , branch
> > d4... But I had to do some "rather interesting" hacks. D4 modem
> > expects packets and current kernel drivers rely on write() boundaries
> > and flush(). .. which is a bit of problem for in ofonod, as it expects
> > to work with bytestream with no explicit packet boundaries.
> >
> > However D4 still uses normal AT commands, so... it would be good to be
> > able to use AT parsing framework in ofono.
> >
> > I believe easiest solution would be to automatically do the packet
> > splitting in kernel, it should be as easy as splitting on \r and
> > ^Z. (Currently packets are only generated when \r or ^Z is seen on
> > write boundary, but that does not work well for ofono).
>
> OK yeah it's worth trying. I hit that issue too with the
> flush needed for droid4-sms-tools scripts. And the traffic
> we're seeing is minimal and AFAIK there's no network port
> for ts27010. And SMS messages are PDU encoded anyways.
>
> Hmm should we do it for \r\n and \r? Otherwise the \n
> will be left out of the packet :)
I guess splitting on \n makes sense, yes.
Ofono normally uses just \r. Translating it to \r\n in kernel (ttys
already do that) would be super nice, but I think this is easy enough
to handle in ofono.
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Droid 4 modem support in kernel & ofono
2019-02-07 22:17 ` Pavel Machek
@ 2019-02-08 15:22 ` Tony Lindgren
-1 siblings, 0 replies; 11+ messages in thread
From: Tony Lindgren @ 2019-02-08 15:22 UTC (permalink / raw)
To: Pavel Machek
Cc: ofono, kernel list, linux-arm-kernel, linux-omap, sre, nekit1000,
mpartap, merlijn
* Pavel Machek <pavel@ucw.cz> [190207 22:18]:
> Hi!
>
> > > Ok, so I got calls and smses somehow working in kernel&ofono ... which
> > > is really all I need.
> >
> > Nice :)
> >
> > I think the SIM card reading and writing should be doable
> > using dlci10 /dev/motmdm10 for AT+CRSM calls..
>
> Might be. Sorry, this is outside of my area of interest, because LTE
> would not be on usable frequencies, anyway.
Oh I did not mean LTE, I meant for general SIM access for
ofono for pin codes etc. Anyways, if anybody needs the sim,
it should be available at /dev/motmdm10.
> > > I pushed the tree to git@github.com:pavelmachek/ofono.git , branch
> > > d4... But I had to do some "rather interesting" hacks. D4 modem
> > > expects packets and current kernel drivers rely on write() boundaries
> > > and flush(). .. which is a bit of problem for in ofonod, as it expects
> > > to work with bytestream with no explicit packet boundaries.
> > >
> > > However D4 still uses normal AT commands, so... it would be good to be
> > > able to use AT parsing framework in ofono.
> > >
> > > I believe easiest solution would be to automatically do the packet
> > > splitting in kernel, it should be as easy as splitting on \r and
> > > ^Z. (Currently packets are only generated when \r or ^Z is seen on
> > > write boundary, but that does not work well for ofono).
> >
> > OK yeah it's worth trying. I hit that issue too with the
> > flush needed for droid4-sms-tools scripts. And the traffic
> > we're seeing is minimal and AFAIK there's no network port
> > for ts27010. And SMS messages are PDU encoded anyways.
> >
> > Hmm should we do it for \r\n and \r? Otherwise the \n
> > will be left out of the packet :)
>
> I guess splitting on \n makes sense, yes.
>
> Ofono normally uses just \r. Translating it to \r\n in kernel (ttys
> already do that) would be super nice, but I think this is easy enough
> to handle in ofono.
Do you have some simple test case with printf?
This test case works just fine already:
$ printf "AT+CFUN=1\rAT+SCRN=0\r" > /dev/motmdm1
But maybe the modem behaves in a different way for different
dlci.. So a minimal test case would be good to have :)
Regards,
Tony
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Droid 4 modem support in kernel & ofono
@ 2019-02-08 15:22 ` Tony Lindgren
0 siblings, 0 replies; 11+ messages in thread
From: Tony Lindgren @ 2019-02-08 15:22 UTC (permalink / raw)
To: Pavel Machek
Cc: mpartap, merlijn, sre, kernel list, nekit1000, ofono, linux-omap,
linux-arm-kernel
* Pavel Machek <pavel@ucw.cz> [190207 22:18]:
> Hi!
>
> > > Ok, so I got calls and smses somehow working in kernel&ofono ... which
> > > is really all I need.
> >
> > Nice :)
> >
> > I think the SIM card reading and writing should be doable
> > using dlci10 /dev/motmdm10 for AT+CRSM calls..
>
> Might be. Sorry, this is outside of my area of interest, because LTE
> would not be on usable frequencies, anyway.
Oh I did not mean LTE, I meant for general SIM access for
ofono for pin codes etc. Anyways, if anybody needs the sim,
it should be available at /dev/motmdm10.
> > > I pushed the tree to git@github.com:pavelmachek/ofono.git , branch
> > > d4... But I had to do some "rather interesting" hacks. D4 modem
> > > expects packets and current kernel drivers rely on write() boundaries
> > > and flush(). .. which is a bit of problem for in ofonod, as it expects
> > > to work with bytestream with no explicit packet boundaries.
> > >
> > > However D4 still uses normal AT commands, so... it would be good to be
> > > able to use AT parsing framework in ofono.
> > >
> > > I believe easiest solution would be to automatically do the packet
> > > splitting in kernel, it should be as easy as splitting on \r and
> > > ^Z. (Currently packets are only generated when \r or ^Z is seen on
> > > write boundary, but that does not work well for ofono).
> >
> > OK yeah it's worth trying. I hit that issue too with the
> > flush needed for droid4-sms-tools scripts. And the traffic
> > we're seeing is minimal and AFAIK there's no network port
> > for ts27010. And SMS messages are PDU encoded anyways.
> >
> > Hmm should we do it for \r\n and \r? Otherwise the \n
> > will be left out of the packet :)
>
> I guess splitting on \n makes sense, yes.
>
> Ofono normally uses just \r. Translating it to \r\n in kernel (ttys
> already do that) would be super nice, but I think this is easy enough
> to handle in ofono.
Do you have some simple test case with printf?
This test case works just fine already:
$ printf "AT+CFUN=1\rAT+SCRN=0\r" > /dev/motmdm1
But maybe the modem behaves in a different way for different
dlci.. So a minimal test case would be good to have :)
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 11+ messages in thread