Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Rich Brown <richb.hanover@gmail.com>
To: Jim Gettys <jg@freedesktop.org>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] New Linksys router
Date: Tue, 7 Jan 2014 11:17:21 -0500	[thread overview]
Message-ID: <B1FFFE6C-4C3E-42F2-867C-5E65B56A490A@gmail.com> (raw)
In-Reply-To: <CAGhGL2D+UrzUX6qb4nrK7kZ6rwT1v2rfHL=JPeEp3f+C3NCkmA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 891 bytes --]

The press release for the new Linksys WRT1900AC has some details: 1.2GHz dual-core ARM, 128MBytes Flash, 256MBytes DDR3 RAM, 2.4 & 5 GHz dual band, lots of other good stuff. http://www.linksys.com/en-us/press/releases/2014-01-06_Linksys_wrt_revolutionizes_wireless_networking

… and also…

On Jan 7, 2014, at 11:05 AM, Jim Gettys <jg@freedesktop.org> wrote:

> Exactly what chips are inside?
> 
> Any binary blobs?  Binary blob device drivers are non-starters. Binary blob firmware (e.g. in a wireless chip), can be handled if necessary if the code is available to the community (as is the case with ath9k).
>                      
> When we can get some (if they are interesting)? 
> 
> When will their code base be available?

Good point on the blobs. I’m hopeful that their big emphasis on Open Source versions (they mention OpenWrt) will avoid the blobs. 

Best, 

Rich

[-- Attachment #2: Type: text/html, Size: 3965 bytes --]

  reply	other threads:[~2014-01-07 16:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07 15:46 Toke Høiland-Jørgensen
2014-01-07 15:56 ` Rich Brown
2014-01-07 16:03   ` David Personette
2014-01-07 16:14     ` Sebastian Moeller
2014-01-07 16:05   ` Jim Gettys
2014-01-07 16:17     ` Rich Brown [this message]
2014-01-11 16:34       ` Rich Brown

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=B1FFFE6C-4C3E-42F2-867C-5E65B56A490A@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=jg@freedesktop.org \
    --cc=toke@toke.dk \
    /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