Linux wireless drivers development
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>,
	Marcel Holtmann <marcel@holtmann.org>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
	"Subash Abhinov Kasiviswanathan" <subashab@codeaurora.org>,
	"Dan Williams" <dcbw@redhat.com>,
	"Sean Tranchetti" <stranche@codeaurora.org>,
	"Daniele Palmas" <dnlplm@gmail.com>,
	"Aleksander Morgado" <aleksander@aleksander.es>,
	"Bjørn Mork" <bjorn@mork.no>
Subject: Re: cellular modem APIs - take 2
Date: Wed, 29 May 2019 15:44:12 -0500	[thread overview]
Message-ID: <8b6b6174-7de4-b9a9-242b-765da647402e@gmail.com> (raw)
In-Reply-To: <acf18b398fd63f2dfece5981ebd5057141529e6a.camel@sipsolutions.net>

Hi Johannes,

> 
> After all, I'm not really proposing that we put oFono or something like
> it into the kernel - far from it! I'm only proposing that we kill the
> many various ways of creating and managing the necessary netdevs (VLANs,
> sysfs, rmnet, ...) from a piece of software like oFono (or libmbim or
> whatever else).

I do like the concept of unifying this if possible.  The question is, is 
it actually possible :)  I think Dan covered most of the aspects of what 
userspace has to deal with already.  But the basic issue is that there's 
a heck of a lot of different ways of doing it.

> 
> Apart from CAIF and phonet, oFono doesn't even try to do this though,
> afaict, so I guess it relies on the default netdev created, or some out-
> of-band configuration is still needed?

Actually it can.  We can drive modems which provide only a single serial 
port and run multiplexing over that.  So we fully control the number of 
control channels created, the number of netdevs created and even 
create/destroy them on as needed basis.  And these netdevs can be PPP 
encapsulated or pure IP or whatever else.

Regards,
-Denis

  reply	other threads:[~2019-05-29 20:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27 13:20 cellular modem APIs - take 2 Johannes Berg
2019-05-29 19:05 ` Marcel Holtmann
2019-05-29 19:59   ` Johannes Berg
2019-05-29 20:44     ` Denis Kenzior [this message]
2019-05-30  5:28     ` Marcel Holtmann
2019-05-29 19:59 ` Dan Williams
2019-05-29 20:16   ` Johannes Berg
2019-05-29 20:35     ` Denis Kenzior

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8b6b6174-7de4-b9a9-242b-765da647402e@gmail.com \
    --to=denkenz@gmail.com \
    --cc=aleksander@aleksander.es \
    --cc=bjorn@mork.no \
    --cc=dcbw@redhat.com \
    --cc=dnlplm@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=stranche@codeaurora.org \
    --cc=subashab@codeaurora.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox