[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <acff4139b1286a0c047ffb3001d2e0b5.squirrel@webmail.itwm.fhg.de>
Date: Mon, 7 Apr 2014 00:43:01 +0200
From: "Phoebe Buckheister" <phoebe.buckheister@...m.fraunhofer.de>
To: "Ben Hutchings" <ben@...adent.org.uk>
Cc: "Alexander Smirnov" <alex.bluesman.smirnov@...il.com>,
"Dmitry Eremin-Solenikov" <dbaryshkov@...il.com>,
netdev@...r.kernel.org, linux-zigbee-devel@...ts.sourceforge.net,
"Phoebe Buckheister" <phoebe.buckheister@...m.fraunhofer.de>
Subject: Re: nl802154 UAPI definitions
On Mon, April 7, 2014 12:22 am, Ben Hutchings wrote:
> On Mon, 2014-03-31 at 15:17 +0200, Phoebe Buckheister wrote:
> [...]
>> --- a/include/linux/nl802154.h
>> +++ b/include/linux/nl802154.h
>> @@ -132,7 +132,7 @@ enum {
>> IEEE802154_ADD_IFACE,
>> IEEE802154_DEL_IFACE,
>>
>> - IEEE802154_SET_PHYPARAMS,
>> + IEEE802154_SET_MACPARAMS,
>>
>> __IEEE802154_CMD_MAX,
>> };
> [...]
>
> By the way, this header file belongs in include/uapi/linux (except for
> the ieee802154_policy declaration).
Yes, I've talked about that with other 802154 devs a few times as well. No
kernel until 3.15 will have had a 802.15.4 stack that's seriously usable,
whether at all or in compliance with regulations, do to an impressive list
of bugs and missing control knobs. I'd suggest to move all user-relevant
API descriptions to uapi/ once all that is sorted out to signify that the
stack is now somewhat usable beyond the toy examples of sending and
receiving five packets or so. (For example, before 3.15, anything 6lowpan
might crash the kernel, and opening 802.15.4 sockets while a 6lowpan
device *exists* will crash the machine hard. Unfortunately, byte ordering
in the APIs will stay with us nonetheless.)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists