From: "Richard A. Smith" <richard@laptop.org>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] anybody here hacking on android?
Date: Fri, 10 May 2013 08:19:51 -0400 [thread overview]
Message-ID: <518CE5E7.50705@laptop.org> (raw)
In-Reply-To: <CAA93jw7pcX9DzygHYVQ+i_EaGsY9f-DWpEWM+HTqmYOVVY0DpA@mail.gmail.com>
On 05/10/2013 04:23 AM, Dave Taht wrote:
> I am planning to add a few android devices to the fq_codel'd campground
> wifi testbed this summer. It looks like the nexus 7 is well supported by
> cyanogenmod, my only kvetch with that device is that there is no 5ghz
> support on it, and it looks like there are blobs to be had in various
> bits of that platform.
> Is there a better device more worth hacking on? Is there anybody else
> here hacking on a specific device?
For the Ethiopian reading project we used Motorola Xooms.
http://blog.laptop.org/tag/ethiopia/#.UYzcvP1Dsp8
I'd give you one but all I have left is 2 broken ones. They support
5Ghz and we ran a TeamEOS build on them.
http://www.xoomforums.com/forum/team-eos/
Actually our build was and earlier build before the name changed to
team-eos. I also ran CyanogenMod 10.0 on the last working one I had.
It works well.
I've built apps but not yet built a full OS build. Building a full tree
requires a pretty beefy machine these days and CyanogenMod >= 10
requires you use a 64-bit os now.
> My core criteria is being able to have deep insight into the gsm/lte
> and/or wifi drivers.
The Xoom has a BCM4329 802.11n WiFi which may not be the best choice for
you.
OLPC is currently investigating running android on the XO-4. I'll let
you know if we actually do a port.
--
Richard A. Smith <richard@laptop.org>
One Laptop per Child
prev parent reply other threads:[~2013-05-10 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 8:23 Dave Taht
2013-05-10 12:19 ` Richard A. Smith [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
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=518CE5E7.50705@laptop.org \
--to=richard@laptop.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