linux-wpan.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: Achim Kraus <achimkraus@gmx.net>,
	linux-wpan - ML <linux-wpan@vger.kernel.org>
Subject: Re: 6lowpan Support for Raspberry PI 3B+ - CYW43455
Date: Sun, 18 Oct 2020 19:32:01 -0400	[thread overview]
Message-ID: <CAB_54W786Cfox4_CLMa1SteX_xab4X1bbwBsgqb_Ok5rQBS_8w@mail.gmail.com> (raw)
In-Reply-To: <9724.1600275702@localhost>

Hi,

On Wed, 16 Sep 2020 at 13:01, Michael Richardson <mcr@sandelman.ca> wrote:
>
>
> Alexander Aring <alex.aring@gmail.com> wrote:
>     > I tried to use BT 6LoWPAN and experienced a lot of races there, sadly
>     > nobody is fixing it. I sent a RFC some years ago to tackle these
>     > issues, also that the link-layer address is reconstructed by L3
>     > address and not by a ndisc lookup is very weird. I don't know if this
>     > is fixed or not.  However it was nothing related to the new BT mesh
>     > stuff.
>
>     >> for any BT device.  I would love to be wrong!!
>     >>
>     >> Running BTLE mesh is something I'd really like to do.
>     >> My guess is that one could probably prototype this in userspace on top of
>     >> bluez, and then use Alex' 6lowpan tap interface.
>
>     > I did not do the "6lowpan tap" interface, the bluetooth people did
>     > that and I complained about it and I never would accept this upstream.
>
> okay, what did you use to connect the OpenThread native-build processes together?
>

sorry for the late reply. This was doing L2 and above in user space,
it was the Linux driver layer only... I thought it was about using
6LoWPAN until the transport layer in kernel and link-layer in user
space.
It also had some problems with ack handling and you will not really
use Linux then, however I was always thinking about to wrap a whole
library around openthread and do some daemon to using Linux then,
instead running an OS on an OS.

- Alex

      reply	other threads:[~2020-10-18 23:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-08  5:55 6lowpan Support for Raspberry PI 3B+ - CYW43455 Achim Kraus
2020-09-15 20:21 ` Michael Richardson
2020-09-15 22:07   ` Alexander Aring
2020-09-16  5:38     ` Achim Kraus
2020-09-16 17:06       ` Michael Richardson
2020-09-16 17:14         ` Achim Kraus
2020-09-16 23:05           ` Michael Richardson
2020-09-26 12:51       ` Achim Kraus
2020-09-16 17:01     ` Michael Richardson
2020-10-18 23:32       ` Alexander Aring [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAB_54W786Cfox4_CLMa1SteX_xab4X1bbwBsgqb_Ok5rQBS_8w@mail.gmail.com \
    --to=alex.aring@gmail.com \
    --cc=achimkraus@gmx.net \
    --cc=linux-wpan@vger.kernel.org \
    --cc=mcr@sandelman.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).