Hi, On Mon, Sep 11, 2017 at 11:17 AM, StarNight <starnight@xxxxxxxxxxxx> wrote: > Hi, > > 2017-09-11 20:47 GMT+08:00 Alexander Aring <aring@xxxxxxxxxxxx>: >> Hi, >> >> On Mon, Sep 11, 2017 at 3:50 AM, Xue Liu <liuxuenetmail@xxxxxxxxx> wrote: >>> Hello Pan, >>> >>> From my point of view, it is not a good idea to write sx127x driver >>> for IEEE 802154. Because LoRa is not compatible with IEEE 802.15.4 in >>> PHY and MAC layer. >>> >> >> This isn't true. The security layer is exactly the same and copied >> from IEEE 802.15.4. >> The rest of the mac layer is pretty simple. Simpler than IEEE >> 802.15.4... for now. > > That is the first reason why I write this driver. > > I also found "Transmission of IPv6 Packets over LoRaWAN" on IETF website > https://datatracker.ietf.org/doc/draft-vilajosana-lpwan-lora-hc/ > However, it has been expired since 2017-01-09. > It is the second reason why I write this driver. > >>> I think it is better to make individual Phy and MAC layers for LoRa in >>> Linux kernel, where a sx127x driver will make sense. >> >> What about to introduce a new interface type? Then you can do a >> complete different parsing on this interface type and share the code >> what you need from 802.15.4 > > So, will the suggestion be a new interface like "6LoWPAN over LoRaWAN"? > You mixing L2 and 6LoWPAN here. L2 layer is 802.15.4, there we have the device nodes "node", "monitor" and "coordinator" (not implemented yet). My idea is to add a Lora L2 interface type there and then you can catch frames and make a "lora.c" file in net/mac802154 for lora frame handling. If you need 802.15.4 stuff just use it then. This makes sense, because Lora use some 802.15.4 stuff which is mostly the same. For 6LoWPAN you need to make an implementation for Lora 6LoWPAN adaptation, question is if we want to put that in net/ieee802154 :-/ or do e.g. "net/lora" (There you can put lora socket handling/6lowpan adaptation etc.) Will wait for Stefan's opinion according to that. - Alex -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
