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

[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]


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?

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2020-09-16 20: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 [this message]
2020-10-18 23:32       ` Alexander Aring

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=9724.1600275702@localhost \
    --to=mcr@sandelman.ca \
    --cc=achimkraus@gmx.net \
    --cc=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    /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).