linux-kernel - Re: Droid 4 modem support in kernel & ofono

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20190201205032.GF5720@atomide.com>
Date:   Fri, 1 Feb 2019 12:50:32 -0800
From:   Tony Lindgren <tony@...mide.com>
To:     Pavel Machek <pavel@....cz>
Cc:     ofono@...no.org, kernel list <linux-kernel@...r.kernel.org>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        linux-omap@...r.kernel.org, sre@...nel.org, nekit1000@...il.com,
        mpartap@....net, merlijn@...zup.org
Subject: Re: Droid 4 modem support in kernel & ofono

* Pavel Machek <pavel@....cz> [190201 20:36]:
> 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..

> I pushed the tree to git@...hub.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 :)

Regards,

Tony