From: Dave Taht <dave.taht@gmail.com>
To: Maciej Soltysiak <maciej@soltysiak.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] WNDR6300 - 802.11ac device - any good?
Date: Mon, 2 Jul 2012 13:29:52 -0400 [thread overview]
Message-ID: <CAA93jw4YBQFKaRTZBKCgKLX_SP1EORubM3oZPNy1+mbBy0GMNA@mail.gmail.com> (raw)
In-Reply-To: <CAMZR1YB0Rb2mRnT5nqGh51+1pJZ0+1_C2RzDOH7bF7_im9rwmA@mail.gmail.com>
On Mon, Jul 2, 2012 at 1:09 PM, Maciej Soltysiak <maciej@soltysiak.com> wrote:
> Hi,
>
> Netgear has recently released a 802.11ac device dubbed WNDR6300 with 128 MB
> Flash and 128 MB RAM.
> Not sure what chip it has, probably BCM4360.
>
> Anybody knows if this is as open as WNDR3800 to allow cerowrt and open the
> door for even more problem with gigabit wireless? ;-)
>
> Regards,
> Maciej
I would ask the openwrt list this question.
But I doubt that it's presently very open to radical developments.
It would be very nice if the 6300 was usable in various ways (does it
at least have apps?) - I'd like to get bufferbloat related fixes in by
default on the 802.11ac stack, as one major example -
and oooh! 128MB flash. LUXURY.
I personally am not in a position to do any more work on cerowrt than
I currently do; it's a full time job that doesn't pay anything at all.
And then I have two other full time volunteer jobs.
Adding direct support for more cerowrt hardware on that budget is just
not in the cards... (I do try to focus high enough on the stack to get
fixes out for linux mainline and openwrt that apply across everything,
however. I'm very happy with how fast fq_codel is propagating)
Although the karmic rewards of these volunteer jobs (fixing the
internet, working with you all) are often quite satisfying, I'm 8
months past the point where I need to find some work that puts food on
the table, even if not so karmically rewarding. As much as I like
living in a yurt, I kind of need a car to survive in the US as one
problem I'm dealing with now. Last week I came very close to moving
back to Nicaragua in time for debconf, (a horse is 200 bucks!) but I
feel I'm more effective in the valley (the nearest radio shack is 6km,
rather than 100km, away), and have found a good site for future
experimentation, so I hope to find a way to continue in the US for the
rest of the year.
Somehow. On something.
>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
--
Dave Täht
http://www.bufferbloat.net/projects/cerowrt/wiki - "3.3.8-6 is out
with fq_codel!"
next prev parent reply other threads:[~2012-07-02 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 17:09 Maciej Soltysiak
2012-07-02 17:29 ` Dave Taht [this message]
2012-07-03 10:23 ` Maciej Soltysiak
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=CAA93jw4YBQFKaRTZBKCgKLX_SP1EORubM3oZPNy1+mbBy0GMNA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=maciej@soltysiak.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