The rf233 and rf231 are sufficiently similar that we can treat
rf233 like rf231.
rf233 is missing some features that rf231 has, but we don't currently
make use of them so there's nothing to handle differently yet.
Should we add support in the future for rf231 *_NOCLK or SLEEP states,
or PAD_IO dr
There is no need to lock the clearing of IRQ_TRX_END in status.
Signed-off-by: Alexander Aring
---
drivers/net/ieee802154/at86rf230.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ieee802154/at86rf230.c
b/drivers/net/ieee802154/at86rf230.c
index 2b638b0..706b71
This patch fix a unexpected state change for the at86rf231 chip.
We can't change into STATE_FORCE_TX_ON while the chip is in one of
SLEEP, P_ON, RESET, TRX_OFF, and all *_NOCLK states.
In this case we are in the TRX_OFF state. See datasheet [1] page 71 for
more information.
Without this patch you
This patch fix a lockdep in the at86rf230 driver, otherwise we get:
[ 30.206517] =
[ 30.211078] [ INFO: inconsistent lock state ]
[ 30.215647] 3.14.0-20140108-1-00994-g32e9426 #163 Not tainted
[ 30.221660] -
[ 30.226222] inc
Hi,
this patch series will fix some issues with the at86rf231 chip
and the at86rf230 driver. If all things seems fine then I will
send this patch series to netdev.
Phoebe can you please test this with the at86rf212?
- Alex
Alexander Aring (3):
at86rf230: fix unexpected state change
at86rf23
From: Alexander Aring
Date: Sun, 9 Mar 2014 09:51:40 +0100
> Correct offset is 3 of the 6lowpanfrag_max_datagram_size value in proc
> entry ctl table and not 2.
>
> Signed-off-by: Alexander Aring
Applied, thanks.
--
Hi,
I am maintaining a driver outside of the kernel. I'm more than happy to
keep abreast of any changes via this forum and implement any changes needed.
On Point 3) I would be happy to see this go, for us it will be 1 WPAN
<-> 1 PHY.
Point 4) Yielding the processor in the driver doesn't feel r
Hi all,
Sorry, I will resend this patch series now I see that my patch rework
script doesn't work correctly.
It drops the [PATCH #/10] to [PATCH #/0], seems that my regex checks
only for one number. :-)
Sorry!
--
Learn
This patch makes the data pointer in lowpan_fetch_skb optionally. We can
use this if we doesn't care about the fetched data.
Signed-off-by: Alexander Aring
---
include/net/6lowpan.h | 4 +++-
net/ieee802154/6lowpan_rtnl.c | 5 -
2 files changed, 7 insertions(+), 2 deletions(-)
diff
This patch removes the own implementation to check of link-layer,
broadcast and any address type and use the IPv6 api for that.
Signed-off-by: Alexander Aring
---
include/net/6lowpan.h | 15 ---
net/ieee802154/6lowpan_iphc.c | 38 ++
2 file
This patch uses the lowpan_push_hc_data functions in several places
where we can use it. The lowpan_push_hc_data was introduced in some
previous patches.
Signed-off-by: Alexander Aring
---
net/ieee802154/6lowpan_iphc.c | 46 ---
1 file changed, 21 insertio
Signed-off-by: Alexander Aring
---
net/ieee802154/6lowpan_rtnl.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/net/ieee802154/6lowpan_rtnl.c b/net/ieee802154/6lowpan_rtnl.c
index 62fe4bf..710e06a 100644
--- a/net/ieee802154/6lowpan_rtnl.c
+++ b/net/ieee802154/6lowpan
Signed-off-by: Alexander Aring
---
net/ieee802154/6lowpan_rtnl.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/net/ieee802154/6lowpan_rtnl.c b/net/ieee802154/6lowpan_rtnl.c
index 1bbab89..62fe4bf 100644
--- a/net/ieee802154/6lowpan_rtnl.c
+++ b/net/ieee802154/6lowpan_rtnl.c
@@ -77,13
Signed-off-by: Alexander Aring
---
include/net/6lowpan.h | 15 ---
1 file changed, 15 deletions(-)
diff --git a/include/net/6lowpan.h b/include/net/6lowpan.h
index ead38af..0d8c78f 100644
--- a/include/net/6lowpan.h
+++ b/include/net/6lowpan.h
@@ -74,10 +74,6 @@
(((a)->s6_ad
Signed-off-by: Alexander Aring
---
net/ieee802154/6lowpan_iphc.c | 23 ++-
1 file changed, 14 insertions(+), 9 deletions(-)
diff --git a/net/ieee802154/6lowpan_iphc.c b/net/ieee802154/6lowpan_iphc.c
index e0e0dba..b63a6e1 100644
--- a/net/ieee802154/6lowpan_iphc.c
+++ b/net/i
Hi,
this patch series cleanups a little bit the current 6lowpan dataflow.
Mostly used more function which we already included mainline and use
ipv6 api instead of own implemented functions. At least I remove some
unused functions and magic numbers.
I will send it to netdev if all things looks fin
The hc06_ptr pointer variable stands for header compression draft-06. We
are mostly rfc complaint. This patch rename the variable to normal hc_ptr.
Signed-off-by: Alexander Aring
---
net/ieee802154/6lowpan_iphc.c | 108 +-
1 file changed, 54 insertions(+),
We introduced the lowpan_fetch_skb function in some previous patches for
6lowpan to have a generic fetch function. This patch drops the old
function and use the generic lowpan_fetch_skb one.
Signed-off-by: Alexander Aring
---
include/net/6lowpan.h | 22 --
net/bluetoo
We can also compare with dev->broadcast instead to have some macro which
compare with static numbers.
Signed-off-by: Alexander Aring
---
include/net/6lowpan.h | 10 --
net/ieee802154/6lowpan_rtnl.c | 2 +-
2 files changed, 1 insertion(+), 11 deletions(-)
diff --git a/include/ne
On Mon, Mar 10, 2014 at 09:59:07AM +0100, Rafik Harzi wrote:
> Thanks
>
> Yes I have had look into it but since I am still waiting to receive my
> device I postponed it and focused on the application that provides the IPv6
> packets :)
>
What a device is it? I know there is a econotag firmware wh
Thanks
Yes I have had look into it but since I am still waiting to receive my
device I postponed it and focused on the application that provides the IPv6
packets :)
2014-03-10 9:36 GMT+01:00 Alexander Aring :
> On Mon, Mar 10, 2014 at 09:25:18AM +0100, Rafik Harzi wrote:
> > Hi,
> >
> >I w
On Mon, Mar 10, 2014 at 09:25:18AM +0100, Rafik Harzi wrote:
> Hi,
>
>I want to use the LoWPAN implementation and I have a question about the
> IPv6 Packets that I should provide to my lowpan interface (because I will
> be developing my own application that will send IPv6 packets) :
>
> 1 -
Hi,
I want to use the LoWPAN implementation and I have a question about the
IPv6 Packets that I should provide to my lowpan interface (because I will
be developing my own application that will send IPv6 packets) :
1 - should the packets have an IEEE802.15.4 header or just stop at the
level o
23 matches
Mail list logo
