<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/include/net/ieee802154_netdev.h, branch linux-3.17.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-3.17.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-3.17.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2014-05-16T21:23:42Z</updated>
<entry>
<title>ieee802154, mac802154: implement devkey record option</title>
<updated>2014-05-16T21:23:42Z</updated>
<author>
<name>Phoebe Buckheister</name>
<email>phoebe.buckheister@itwm.fraunhofer.de</email>
</author>
<published>2014-05-16T15:46:45Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=f0f77dc6be76ed1854b08688390e156e4b351ab5'/>
<id>urn:sha1:f0f77dc6be76ed1854b08688390e156e4b351ab5</id>
<content type='text'>
The 802.15.4-2011 standard states that for each key, a list of devices
that use this key shall be kept. Previous patches have only considered
two options:

 * a device "uses" (or may use) all keys, rendering the list useless
 * a device is restricted to a certain set of keys

Another option would be that a device *may* use all keys, but need not
do so, and we are interested in the actual set of keys the device uses.
Recording keys used by any given device may have a noticable performance
impact and might not be needed as often. The common case, in which a
device will not switch keys too often, should still perform well.

Signed-off-by: Phoebe Buckheister &lt;phoebe.buckheister@itwm.fraunhofer.de&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>mac802154: add llsec configuration functions</title>
<updated>2014-05-16T21:23:41Z</updated>
<author>
<name>Phoebe Buckheister</name>
<email>phoebe.buckheister@itwm.fraunhofer.de</email>
</author>
<published>2014-05-16T15:46:42Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=29e023746a672e4ff702ca9dc63a06145fd8f4b0'/>
<id>urn:sha1:29e023746a672e4ff702ca9dc63a06145fd8f4b0</id>
<content type='text'>
Signed-off-by: Phoebe Buckheister &lt;phoebe.buckheister@itwm.fraunhofer.de&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>mac802154: integrate llsec with wpan devices</title>
<updated>2014-05-16T21:23:41Z</updated>
<author>
<name>Phoebe Buckheister</name>
<email>phoebe.buckheister@itwm.fraunhofer.de</email>
</author>
<published>2014-05-16T15:46:40Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=f30be4d53cada48598dab0983866ae4b16af46dc'/>
<id>urn:sha1:f30be4d53cada48598dab0983866ae4b16af46dc</id>
<content type='text'>
Signed-off-by: Phoebe Buckheister &lt;phoebe.buckheister@itwm.fraunhofer.de&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>ieee802154: add types for link-layer security</title>
<updated>2014-05-16T21:23:40Z</updated>
<author>
<name>Phoebe Buckheister</name>
<email>phoebe.buckheister@itwm.fraunhofer.de</email>
</author>
<published>2014-05-16T15:46:35Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=dc20759f281c0f9e6c4fca8be251deca2954862a'/>
<id>urn:sha1:dc20759f281c0f9e6c4fca8be251deca2954862a</id>
<content type='text'>
The added structures match 802.15.4-2011 link-layer security PIBs as
closely as is reasonable. Some lists required by the standard were
modeled as bitmaps (frame_types and command_frame_ids in *llsec_key,
802.15.4-2011 7.5/Table 61), since using lists for those seems a bit
excessive and not particularly useful. The DeviceDescriptorHandleList
was inverted and is here a per-device list, since operations on this
list are likely to have both a key and a device at hand, and per-device
lists of keys are shorter than per-key lists of devices.

Signed-off-by: Phoebe Buckheister &lt;phoebe.buckheister@itwm.fraunhofer.de&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>ieee802154: change _cb handling slightly</title>
<updated>2014-05-15T19:51:42Z</updated>
<author>
<name>Phoebe Buckheister</name>
<email>phoebe.buckheister@itwm.fraunhofer.de</email>
</author>
<published>2014-05-14T15:43:08Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=32edc40ae65cf84e1ab69f6f8316ce81559e115d'/>
<id>urn:sha1:32edc40ae65cf84e1ab69f6f8316ce81559e115d</id>
<content type='text'>
The current mac_cb handling of ieee802154 is rather awkward and limited.
Decompose the single flags field into multiple fields with the meanings
of each subfield of the flags field to make future extensions (for
example, link-layer security) easier. Also don't set the frame sequence
number in upper layers, since that's a thing the MAC is supposed to set
on frame transmit - we set it on header creation, but assuming that
upper layers do not blindly duplicate our headers, this is fine.

Signed-off-by: Phoebe Buckheister &lt;phoebe.buckheister@itwm.fraunhofer.de&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>ieee802154: add definitions for link-layer security and header functions</title>
<updated>2014-05-15T19:51:42Z</updated>
<author>
<name>Phoebe Buckheister</name>
<email>phoebe.buckheister@itwm.fraunhofer.de</email>
</author>
<published>2014-05-14T15:43:06Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=c3a6114f31600b94ee10ebf62e4d493b401ade87'/>
<id>urn:sha1:c3a6114f31600b94ee10ebf62e4d493b401ade87</id>
<content type='text'>
When dealing with 802.15.4, one often has to know the maximum payload
size for a given packet. This depends on many factors, one of which is
whether or not a security header is present in the frame. These
definitions and functions provide an easy way for any upper layer to
calculate the maximum payload size for a packet. The first obvious user
for this is 6lowpan, which duplicates this calculation and gets it
partially wrong because it ignores security headers.

Signed-off-by: Phoebe Buckheister &lt;phoebe.buckheister@itwm.fraunhofer.de&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>mac802154: make csma/cca parameters per-wpan</title>
<updated>2014-04-01T20:25:51Z</updated>
<author>
<name>Phoebe Buckheister</name>
<email>phoebe.buckheister@itwm.fraunhofer.de</email>
</author>
<published>2014-03-31T19:37:46Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=e462ded699aa2cca04b68fbf203ea4675d4c44d4'/>
<id>urn:sha1:e462ded699aa2cca04b68fbf203ea4675d4c44d4</id>
<content type='text'>
Commit 9b2777d6089bcd (ieee802154: add TX power control to wpan_phy)
and following erroneously added CSMA and CCA parameters for 802.15.4
devices as PHY parameters, while they are actually MAC parameters and
can differ for any two WPAN instances. Since it is now sensible to have
multiple WPAN devices with differing CSMA/CCA parameters, make these
parameters MAC parameters instead.

Signed-off-by: Phoebe Buckheister &lt;phoebe.buckheister@itwm.fraunhofer.de&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>6lowpan: move lowpan frag_info out of 802.15.4 headers</title>
<updated>2014-03-15T02:15:26Z</updated>
<author>
<name>Phoebe Buckheister</name>
<email>phoebe.buckheister@itwm.fraunhofer.de</email>
</author>
<published>2014-03-14T20:24:03Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=a13061ec04e9168625427a591235b167d5499bc6'/>
<id>urn:sha1:a13061ec04e9168625427a591235b167d5499bc6</id>
<content type='text'>
Fragmentation and reassembly information for 6lowpan is independent from
the 802.15.4 stack and used only by the 6lowpan reassembly process. Move
the ieee802154_frag_info struct to a private are, it needn't be in the
802.15.4 skb control block.

Signed-off-by: Phoebe Buckheister &lt;phoebe.buckheister@itwm.fraunhofer.de&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>ieee802154: use ieee802154_addr instead of *_sa variants</title>
<updated>2014-03-15T02:15:26Z</updated>
<author>
<name>Phoebe Buckheister</name>
<email>phoebe.buckheister@itwm.fraunhofer.de</email>
</author>
<published>2014-03-14T20:24:02Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=ae531b9475f62c5e1863508604cd6b3faf362d56'/>
<id>urn:sha1:ae531b9475f62c5e1863508604cd6b3faf362d56</id>
<content type='text'>
Change all internal uses of ieee802154_addr_sa to ieee802154_addr,
except for those instances that communicate directly with userspace.

Signed-off-by: Phoebe Buckheister &lt;phoebe.buckheister@itwm.fraunhofer.de&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>mac802154: use header operations to create/parse headers</title>
<updated>2014-03-15T02:15:26Z</updated>
<author>
<name>Phoebe Buckheister</name>
<email>phoebe.buckheister@itwm.fraunhofer.de</email>
</author>
<published>2014-03-14T20:24:01Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=e6278d92005e9d6e374f269b4ce39c908a68ad5d'/>
<id>urn:sha1:e6278d92005e9d6e374f269b4ce39c908a68ad5d</id>
<content type='text'>
Use the operations on 802.15.4 header structs introduced in a previous
patch to create and parse all headers in the mac802154 stack. This patch
reduces code duplication between different parts of the mac802154 stack
that needed information from headers, and also fixes a few bugs that
seem to have gone unnoticed until now:

 * 802.15.4 dgram sockets would return a slightly incorrect value for
   the SIOCINQ ioctl
 * mac802154 would not drop frames with the "security enabled" bit set,
   even though it does not support security, in violation of the
   standard

Signed-off-by: Phoebe Buckheister &lt;phoebe.buckheister@itwm.fraunhofer.de&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
