From: Michael Richardson <mcr@sandelman.ca>
To: smlng <s@mlng.net>
Cc: Tao Liu <liu3tao@gmail.com>, linux-wpan@vger.kernel.org
Subject: Re: at86rf233 in Raspberry Pi 3
Date: Mon, 22 Aug 2016 11:30:34 -0400 [thread overview]
Message-ID: <2270.1471879834@obiwan.sandelman.ca> (raw)
In-Reply-To: <C218BF9B-CADB-4AF6-8ADE-795F51A09859@mlng.net>
[-- Attachment #1: Type: text/plain, Size: 973 bytes --]
smlng <s@mlng.net> wrote:
> the RIOT-OS Wiki-Guide is rather outdated on this, please have look at
> [1] - this approach works for me and I heard from other, successfully
> using that one too.
In my experience the most challenging part of this is getting the right
upstream RPI3 kernel things with and the right linux-bluetooth-next stuff.
On RPI2, everything is upstream, so the bt-next tree just works. That might
not be the case for RPI3... and I'd probably stick to 32-bit kernels/systems
for now, since I still see lots of 64-bit fixes going upstream.
I have two RPI2 unit working fine, but I traded my RPI3 for an RPI2, because
the serial console UART on the RPI3 is wonky. I believe that this is now fixed.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 464 bytes --]
next prev parent reply other threads:[~2016-08-22 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 7:50 at86rf233 in Raspberry Pi 3 Tao Liu
2016-08-22 14:11 ` smlng
2016-08-22 15:30 ` Michael Richardson [this message]
2016-08-22 21:34 ` Tao Liu
2016-08-23 7:26 ` smlng
2016-08-23 17:49 ` Tao Liu
[not found] ` <1472122778.2490.149.camel@newmarch.name>
2016-08-25 11:10 ` [Fwd: Re: at86rf233 in Raspberry Pi 3] Jan Newmarch
2016-08-25 11:12 ` at86rf233 in Raspberry Pi 3 smlng
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=2270.1471879834@obiwan.sandelman.ca \
--to=mcr@sandelman.ca \
--cc=linux-wpan@vger.kernel.org \
--cc=liu3tao@gmail.com \
--cc=s@mlng.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.