From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
"babel-users@lists.alioth.debian.org"
<babel-users@lists.alioth.debian.org>
Subject: [Cerowrt-devel] beaglebone green wireless boards now available
Date: Tue, 21 Jun 2016 16:54:44 -0700 [thread overview]
Message-ID: <CAA93jw4bFAKVvNYSRj=_nZRZkd9Nkkw-fKz56+sU59givEPFCw@mail.gmail.com> (raw)
I just got two of 'em and getting usbnet up was a snap. I got 'em
because they have
dual 2.4ghz 802.11n antennas and I figured the wifi would be faster
than the getchip stuff.
(there is no adhoc support. another reason for looking at this board
is to look at the structure of the drivers for make-wifi-fast)
I have long liked the beaglebones as being a well built product, with
some special features like the onboard PRUs nothing else can match.
The cpu is getting a bit long in the tooth tho, and these wireless
ones (no ethernet!) are so new that cases don't exist for them yet.
https://www.amazon.com/Seeedstudio-BeagleBone-Green-Wireless-Bluetooth/dp/B01GKE8F10/ref=sr_1_1?ie=UTF8&qid=1466552623&sr=8-1&keywords=beaglebone+green+wireless
they boot up (pretty fast) with debian jesse, kernel 4.4.9-ti-r25, on
the onboard 4GB emmc flash chip.
I was unaware until this moment that debian jesse appears to be
shipping babeld 1.5.1.
The preinstalled OS has sufficient compiler and onboard flash space to
build a current babeld from git, and I'm happy to report IPV6_SUBTREES
is compiled in by default.
As for whether or not I'll end up going through the same hell I'm
going through elsewhere, too soon to tell.
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next reply other threads:[~2016-06-21 23:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 23:54 Dave Taht [this message]
2016-06-22 11:31 ` [Cerowrt-devel] Cross-compiling to armhf [was: beaglebone green wireless boards...] Juliusz Chroboczek
2016-06-22 12:08 ` [Cerowrt-devel] [Babel-users] " Benjamin Henrion
2016-06-22 13:10 ` [Cerowrt-devel] Cross-compiling to armhf Juliusz Chroboczek
2016-06-22 13:15 ` Benjamin Henrion
2016-06-22 20:38 ` Juliusz Chroboczek
2016-06-22 16:38 ` [Cerowrt-devel] Cross-compiling to armhf [was: beaglebone green wireless boards...] Dave Taht
2016-06-23 22:10 ` Juliusz Chroboczek
2016-06-23 22:45 ` Dave Taht
2016-06-23 22:57 ` Juliusz Chroboczek
2016-06-23 23:13 ` Dave Taht
2016-06-24 0:02 ` [Cerowrt-devel] Why we are discussing ARM [was: Cross-compiling to armhf] Juliusz Chroboczek
2016-06-24 2:37 ` Jonathan Morton
2016-06-24 11:04 ` Juliusz Chroboczek
2016-06-24 16:36 ` Eric Johansson
2016-06-24 20:27 ` David Lang
[not found] ` <E1bH8oe-0000Wv-EO@stardust.g4.wien.funkfeuer.at>
2016-06-26 17:59 ` [Cerowrt-devel] [Babel-users] " Juliusz Chroboczek
2016-06-26 19:02 ` Baptiste Jonglez
2016-06-26 19:58 ` Jonathan Morton
2016-06-26 20:03 ` Juliusz Chroboczek
2016-06-23 23:20 ` [Cerowrt-devel] Cross-compiling to armhf [was: beaglebone green wireless boards...] Jonathan Morton
2016-06-23 23:27 ` Dave Taht
2016-06-23 23:42 ` Dave Taht
2016-06-24 16:25 ` Eric Johansson
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4bFAKVvNYSRj=_nZRZkd9Nkkw-fKz56+sU59givEPFCw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=babel-users@lists.alioth.debian.org \
--cc=cerowrt-devel@lists.bufferbloat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox