linux-wpan.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Achim Kraus <achimkraus@gmx.net>
To: Alexander Aring <alex.aring@gmail.com>,
	Michael Richardson <mcr@sandelman.ca>
Cc: linux-wpan - ML <linux-wpan@vger.kernel.org>
Subject: Re: 6lowpan Support for Raspberry PI 3B+ - CYW43455
Date: Sat, 26 Sep 2020 14:51:35 +0200	[thread overview]
Message-ID: <0d77ac6a-c90e-8113-4554-6fc3a444bea9@gmx.net> (raw)
In-Reply-To: <a9280f74-54f0-917f-22a7-8907afd33c95@gmx.net>

Hi Alex,
Hi Michael,

after using the firmware with compliant address mapping for the
nrf52840, it starts to work.

With a linux kernel 4.15.0 stable over a couple of hours.
With a linux kernel5.4.0 or 5.4.51 it's possible to connect, but that
connection is dropped after a couple of seconds (30-40s).

So, seems, that the "old bug" is back in 5.4.

With "kernel lockdown", it seems to be not possible to connect.
At least I didn't find out how.

best regards
Achim

Am 16.09.20 um 07:38 schrieb Achim Kraus:
> Hi Alex,
>
>> 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.
>
> "a lot of races", recently? Or some time ago?
>
>>
>>> for any BT device.  I would love to be wrong!!
>>>
>
> Hi Michael,
>
> The current Raspi OS (based on Debian, kernel 5.4) contains a
> bluetooth_6lowpan module. With that it's possible to connect the
> nrf52840 using a "plain raspi 3b+" (without extra rf module).
>
> Unfortunately, nordic decided to provide precompile examples with the
> old, deprecated address mapping and so I need to spend some time in
> compile these examples before I can report, if it works at all, and the
> experienced stability.
>
> best regards
> Achim
>
> P.S.: though linux-wpan is not bluetooth, I hope the misuse of this list
> is still OK ;-). But I guess, moving it to the right list will alos have
> advantages. Does anyone know, which would be the proper list for that?


  parent reply	other threads:[~2020-09-26 12:56 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 [this message]
2020-09-16 17:01     ` Michael Richardson
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=0d77ac6a-c90e-8113-4554-6fc3a444bea9@gmx.net \
    --to=achimkraus@gmx.net \
    --cc=alex.aring@gmail.com \
    --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).