From: noloader@gmail.com (Jeffrey Walton)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Interface between LTE devices and Linux
Date: Tue, 13 Feb 2018 08:21:23 -0500 [thread overview]
Message-ID: <CAH8yC8mEK8OLOEn16qGt5zv6XG-bBVvrw2L4uALzJ9TTC_pPHg@mail.gmail.com> (raw)
In-Reply-To: <CAOhBGduK6iq+FQ527+JG9BHwziCjBzkeP-3MjivCuVAFE0P7XA@mail.gmail.com>
On Thu, Feb 8, 2018 at 12:10 PM, jjDaNiMoTh <jjdanimoth@gmail.com> wrote:
> Hello everyone,
>
> There is an example of LTE netdevice in the Linux source tree?
>
> In particular, I would like to know if there is any device driver that
> implements the layers required by the 3GPP standard. I imagine that it
> should exist something since Android is communicating over LTE, but I can't
> find any reference. What I fear more is that everything related to LTE is
> inside the closed device firmware, and data is sent from the TC layer into
> this black-box firmware through a sort of API. In this case, it would be
> wonderful to know where, exactly, this API is used, to try to understand
> what the firmware is doing.
In addition to GKH's answer, what I have seen...
Some Android code to talk to the radio is written in plain java, like
https://chromium.googlesource.com/android_tools/+/18728e9dd5dd66d4f5edf1b792e77e2b544a1cb0/sdk/sources/android-19/com/android/internal/telephony/CommandsInterface.java
.
The GNU Radio folks may have relevant information. I seem to recall
they work from userland and not the kernel, though.
Jeff
next prev parent reply other threads:[~2018-02-13 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 17:10 Interface between LTE devices and Linux jjDaNiMoTh
2018-02-08 17:18 ` Greg KH
2018-02-13 7:59 ` Nuno Sá
2018-02-13 13:21 ` Jeffrey Walton [this message]
2018-02-13 15:30 ` Bjørn Mork
2018-02-13 16:07 ` Jeffrey Walton
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=CAH8yC8mEK8OLOEn16qGt5zv6XG-bBVvrw2L4uALzJ9TTC_pPHg@mail.gmail.com \
--to=noloader@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.