From: Jim Gettys <jg@freedesktop.org>
To: Rick <graham.rick@gmail.com>
Cc: bloat-devel@lists.bufferbloat.net, bloat@lists.bufferbloat.net
Subject: Re: CeroWrt RC6 (beta 2) ready for testing.
Date: Tue, 20 Sep 2011 11:53:01 -0400 [thread overview]
Message-ID: <4E78B6DD.2080409@freedesktop.org> (raw)
In-Reply-To: <CAGDjS3fC+be867LohaRWbfqY=WR-qMtD=yKQ1qkGa9cNtCMfiw@mail.gmail.com>
On 09/20/2011 11:30 AM, Rick wrote:
> On Tue, Sep 20, 2011 at 11:18 AM, Jim Gettys <jg@freedesktop.org> wrote:
>> CeroWrt is aimed at (currently) a single hardware platform
>> for which fully open drivers are available: the Netgear WNDR3700v2.
> Am I correct in assuming that this software is not available for the
> original WNDR3700 (i.e. v1) because of the memory required?
>
> From my purchasing research my understanding is that v2 has:
>
> 1. Twice the RAM.
Twice the flash, same RAM (IIRC).
> 2. Less effective aerials.
2 As far as we know, the radios/antennae are the same.
Note that there is substantial variation in production between antennae
(I know this first hand from OLPC; some were much more sensitive than
others and I guarantee anyone's production will vary. Anecdotal reports
aren't useful about signal strength, as a result.).
>
> Both were available at the time of my purchase. I suppose (2.) is
> repairable, but it is the reason I bought the original.
>
Right now, there is a build for the v1 in the download directory
(squashfs) that would fit in a v1; it is untested (by us). The jffs2
image is too big for a v1 at all; for most development, that's a lot
easier to deal with (as your file system is entirely read/write). No
warranties, expressed or implied will be given on the v1. We aren't
willing to spend time shoehorning stuff into an 8Meg limit and recommend
you get a v2.
- Jim
prev parent reply other threads:[~2011-09-20 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 15:18 Jim Gettys
2011-09-20 15:30 ` Rick
2011-09-20 15:53 ` Jim Gettys [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E78B6DD.2080409@freedesktop.org \
--to=jg@freedesktop.org \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=graham.rick@gmail.com \
/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