From: Andrew Lunn <andrew@lunn.ch>
To: "i.n.a" <quiet-daffodil@proton.me>
Cc: "linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [RFC] Appropriate subsystem/UAPI for Semtech SX126x packet radio support
Date: Mon, 21 Sep 2026 00:15:04 +0200 [thread overview]
Message-ID: <a809e324-c282-4524-bf3e-95a7583c607b@lunn.ch> (raw)
In-Reply-To: <blQUbzijkKTlQdGuLj0o-ZJ_Their5EXvu2RW5b0q-tuU0SBmwqMjpk6HprXKRq0Yn_RHathROFMQ3T8nnPaW3nrq9lQdwIG-cF6YaFIte4=@proton.me>
On Sun, Sep 20, 2026 at 09:50:17PM +0000, i.n.a wrote:
> > You want to make whatever API you design vendor independent.
>
> Thanks, that's a good point. I'll keep the API
> vendor-independent. Is there an existing kernel abstraction you'd
> suggest as a starting point?
This is not really my area, but i would look at the ieee802154 code in
the kernel. They are different technologies, but is the MAC interface
that different? Both need to pass packets to send, both need to
receive packets. There needs to be some why to select frequency, etc.
Is stacking protocols on top of the MAC that different to IEEE
802.15.4?
Andrew
next prev parent reply other threads:[~2026-09-20 22:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 21:50 [RFC] Appropriate subsystem/UAPI for Semtech SX126x packet radio support i.n.a
2026-09-20 22:15 ` Andrew Lunn [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-20 23:06 i.n.a
2026-09-24 1:32 ` Jakub Kicinski
2026-09-20 21:15 i.n.a
2026-09-20 21:38 ` Andrew Lunn
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=a809e324-c282-4524-bf3e-95a7583c607b@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=quiet-daffodil@proton.me \
/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