From: Jim Gettys <jg@freedesktop.org>
To: Rich Brown <richb.hanover@gmail.com>
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:05:31 -0500 [thread overview]
Message-ID: <CAGhGL2D+UrzUX6qb4nrK7kZ6rwT1v2rfHL=JPeEp3f+C3NCkmA@mail.gmail.com> (raw)
In-Reply-To: <785EE459-3175-40FC-870C-79A3295FD35E@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
On Tue, Jan 7, 2014 at 10:56 AM, Rich Brown <richb.hanover@gmail.com> wrote:
> I was going to find some time today to call the product manager and/or
> marketing contact to see if they can give advice.
>
> What else would the collective wisdom care to know about?
>
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?
- Jim
>
> Rich
>
> On Jan 7, 2014, at 10:46 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> > Looks promising, if somewhat pricey?
> >
> >
> http://www.linksys.com/en-us/press/releases/2014-01-06_Linksys_wrt_revolutionizes_wireless_networking
> >
> > Anyone knows what chipset it features/will feature?
> >
> > -Toke
> > _______________________________________________
> > Cerowrt-devel mailing list
> > Cerowrt-devel@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 2882 bytes --]
next prev parent reply other threads:[~2014-01-07 16:05 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 [this message]
2014-01-07 16:17 ` Rich Brown
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='CAGhGL2D+UrzUX6qb4nrK7kZ6rwT1v2rfHL=JPeEp3f+C3NCkmA@mail.gmail.com' \
--to=jg@freedesktop.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=richb.hanover@gmail.com \
--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