From: Alexander Aring <aring@mojatatu.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: linux-lpwan@lists.infradead.org, linux-wpan@vger.kernel.org,
Alexander Aring <alex.aring@gmail.com>,
Stefan Schmidt <stefan@datenfreihafen.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
support@enocean.com
Subject: Re: [RFC net-next 1/4] net: Reserve protocol identifiers for EnOcean
Date: Tue, 29 Jan 2019 07:57:08 -0500 [thread overview]
Message-ID: <20190129125708.plsbgcpcwhtezgo5@x220t> (raw)
In-Reply-To: <20190129050130.10932-2-afaerber@suse.de>
Hi,
On Tue, Jan 29, 2019 at 06:01:27AM +0100, Andreas Färber wrote:
> EnOcean wireless technology is based on ASK (ERP1) and FSK (ERP2) modulations
> for sub-GHz and on IEEE 802.15.4 for 2.4 GHz.
>
I am not sure what you try to do here. If I see that correctly you
want to add for some special protocol vendor specific transceiver which
is underneath an 802.15.4 transceiver a new ARPHRD type and even more
for each modulation what it supports?
If it's a 802.15.4 transceiver why not using the 802.15.4 subsystem?
For me it sounds more like a HardMAC transceiver driver for doing the
vendor protocol. The different modulations is part of a 802.15.4 phy
device class. Similar like in wireless.
- Alex
next prev parent reply other threads:[~2019-01-29 12:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 5:01 [RFC net-next 0/4] net: EnOcean prototype driver Andreas Färber
2019-01-29 5:01 ` [RFC net-next 1/4] net: Reserve protocol identifiers for EnOcean Andreas Färber
2019-01-29 12:57 ` Alexander Aring [this message]
2019-01-30 1:42 ` Andreas Färber
2019-02-01 0:58 ` Alexander Aring
2019-02-18 4:41 ` Andreas Färber
2019-01-29 5:01 ` [RFC net-next 2/4] net: Prepare EnOcean device drivers Andreas Färber
2019-01-29 5:01 ` [RFC net-next 3/4] net: enocean: Add ESP3 driver Andreas Färber
2019-01-29 5:01 ` [RFC net-next 4/4] net: enocean: Prepare ESP2 support Andreas Färber
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=20190129125708.plsbgcpcwhtezgo5@x220t \
--to=aring@mojatatu.com \
--cc=afaerber@suse.de \
--cc=alex.aring@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lpwan@lists.infradead.org \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stefan@datenfreihafen.org \
--cc=support@enocean.com \
/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;
as well as URLs for NNTP newsgroup(s).