From: Jakub Kicinski <kuba@kernel.org>
To: "i.n.a" <quiet-daffodil@proton.me>
Cc: "andrew@lunn.ch" <andrew@lunn.ch>,
"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: Wed, 23 Sep 2026 18:32:42 -0700 [thread overview]
Message-ID: <20260923183242.1ea56c5d@kernel.org> (raw)
In-Reply-To: <4vyyH7e6jQ1f1QSNRo16qvvSXxieE4qNs02suWZW-hC6P5pzxq8wmywfogCLRsj-_oucoBZRFxccllsuEPFGqkqTz9TF1h52zWaViQqzDkE=@proton.me>
On Sun, 20 Sep 2026 23:06:39 +0000 i.n.a wrote:
> >Is stacking protocols on top of the MAC that different to IEEE
> 802.15.4?
>
> Had a look through `mac802154` and `ieee802154_ops`, the hardware boundary does look quite similar, particularly packet TX/RX, start/stop, TX power and energy detection.
>
> The main differences seem to be the 802.15.4-specific parts such as channel/page addressing, CSMA parameters and address filtering, versus PHY-specific configuration for LoRa/GFSK.
>
> Would it make sense to investigate factoring out a small generic packet-radio layer beneath the MAC-specific interfaces?
Not an expert, but IMO, you'll need to take it up with ieee802154
maintainers. If they are not interested in broadening the support
I'd say keeping the code in user space seems perfectly fine.
next prev parent reply other threads:[~2026-09-24 1:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 23:06 [RFC] Appropriate subsystem/UAPI for Semtech SX126x packet radio support i.n.a
2026-09-24 1:32 ` Jakub Kicinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-20 21:50 i.n.a
2026-09-20 22:15 ` Andrew Lunn
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=20260923183242.1ea56c5d@kernel.org \
--to=kuba@kernel.org \
--cc=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