Hello.
On 27/01/16 21:46, Alexander Aring wrote:
This patch moves 6lowpan receive handling into 6lowpan generic. I
introduced some callback ops to make some link-layer specific handling.
Signed-off-by: Alexander Aring <aar@xxxxxxxxxxxxxx>
---
Hi,
this patch is a draft to talking about to move the receive handling
and evaluation of 6LoWPAN dispatches into net/6lowpan instead that
every 6lowpan specific link-layer implementation will do that on his
own.
I added some callbacks for receive handling, other solutions would
be to add runtime decisions into net/6lowpan/rx.c by eval the
interface type.
Any comments are welcome. It's not perfect yet and it can be still
improved at some places, if we really like to go that way.
The first questions that comes to mind is why rx only and not tx?
This would also allow the fragment handling to move into the generic
part. I'm aware that bluetooth is not using it but other 6LoWPAN
adaptation layers do and it part of the RFC4944.
regards
Stefan Schmidt
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
