[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAC=mGzijVyqEG=DXH4v9WkD0kXR2WOJC4KBPzoT7g5wqVrPGXA@mail.gmail.com>
Date: Tue, 8 May 2018 23:33:01 +0800
From: Jian-Hong Pan <starnight@...cu.edu.tw>
To: "David S. Miller" <davem@...emloft.net>,
Alexander Aring <alex.aring@...il.com>,
Stefan Schmidt <stefan@....samsung.com>,
linux-wpan - ML <linux-wpan@...r.kernel.org>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [RFC] net: Add new LoRaWAN subsystem
A Low-Power Wide-Area Network (LPWAN) is a type of wireless
telecommunication wide area network designed to allow long range
communications at a low bit rate among things (connected objects), such
as sensors operated on a battery. It can be used widely in IoT area.
LoRaWAN, which is one kind of implementation of LPWAN, is a medium
access control (MAC) layer protocol for managing communication between
LPWAN gateways and end-node devices, maintained by the LoRa Alliance.
LoRaWAN™ Specification could be downloaded at:
https://lora-alliance.org/lorawan-for-developers
However, LoRaWAN is not implemented in Linux kernel right now, so I am
trying to develop it. Here is my repository:
https://github.com/starnight/LoRa/tree/lorawan-ndo/LoRaWAN
Because it is a kind of network, the ideal usage in an user space
program should be like "socket(PF_LORAWAN, SOCK_DGRAM, 0)" and with
other socket APIs. Therefore, the definitions like AF_LORAWAN,
PF_LORAWAN ..., must be listed in the header files of glibc.
For the driver in kernel space, the definitions also must be listed in
the corresponding Linux socket header files.
Especially, both are for the testing programs.
Back to the mentioned "LoRaWAN is not implemented in Linux kernel now".
Could or should we add the definitions into corresponding kernel header
files now, if LoRaWAN will be accepted as a subsystem in Linux?
Thanks,
Jian-Hong Pan
Powered by blists - more mailing lists