From: Felix Fietkau <nbd@openwrt.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] almond
Date: Thu, 11 Apr 2013 00:14:48 +0200 [thread overview]
Message-ID: <5165E458.8040402@openwrt.org> (raw)
In-Reply-To: <CAA93jw7aLbThUqk32FZY=ajJLzEGAQv2vRt6sDypL8X8XcPy3A@mail.gmail.com>
On 2013-04-09 5:12 PM, Dave Taht wrote:
> It looks so close to what I thought a home wifi router would look
> like... in 1999.
>
> If it's openwrt, or open source, it would be nice to see the tree. The
> reviews of the product seem to say it's a run-of-the-mill device
> performancewise....
I just took a look at the kernel binary inside their firmware image.
It's a Ralink MIPS based device running 2.6.21. Unfortunately there
doesn't seem to be a source code download link, and the binary looks
like it may be problematic wrt. license issues as well: the proprietary
Ralink wifi driver seems to be statically linked into the kernel binary.
- Felix
prev parent reply other threads:[~2013-04-10 22:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 8:54 Dave Taht
2013-04-09 13:01 ` Richard Smith
2013-04-09 13:28 ` Michael Richardson
2013-04-09 15:12 ` Dave Taht
2013-04-10 22:14 ` Felix Fietkau [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=5165E458.8040402@openwrt.org \
--to=nbd@openwrt.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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