lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 29 Jan 2019 07:57:08 -0500 From: Alexander Aring <aring@...atatu.com> To: Andreas Färber <afaerber@...e.de> Cc: linux-lpwan@...ts.infradead.org, linux-wpan@...r.kernel.org, Alexander Aring <alex.aring@...il.com>, Stefan Schmidt <stefan@...enfreihafen.org>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, support@...cean.com Subject: Re: [RFC net-next 1/4] net: Reserve protocol identifiers for EnOcean 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
Powered by blists - more mailing lists