Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: David Lang <david@lang.hm>, Mikael Abrahamsson <swmike@swm.pp.se>,
	cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] I so love seeing stuff like this
Date: Sat, 2 Feb 2019 12:00:24 +0100	[thread overview]
Message-ID: <CAE4EF85-765E-4079-B519-997B774C6134@gmx.de> (raw)
In-Reply-To: <874l9miiju.fsf@toke.dk>



> On Feb 2, 2019, at 11:36, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> 
> David Lang <david@lang.hm> writes:
> 
>> On Sat, 2 Feb 2019, Mikael Abrahamsson wrote:
>> 
>>> On Fri, 1 Feb 2019, David Lang wrote:
>>> 
>>>> I had high hopes for these, but the driver development is not working well, 
>>>> it's one guy at Marvell who does it in his spare time, nobody else has the 
>>>> info to be able to work on it.
>>> 
>>> It's the wifi you're worried about? I've read about people having problems 
>>> with the wifi part.
>> 
>> Yes, it's the wifi development and support that is the biggest problem with 
>> these APs.
> 
> The Turris Omnia is the same platform but with ath9/10k pcie cards for
> WiFi. I'm using one of those as my daily driver. Not exactly cheap,
> though :(
> 


They also have the turris MOX in the works wich is modular and might also be an interesting option.

Sebastian

> -Toke
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel


  reply	other threads:[~2019-02-02 11:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-01 16:28 Dave Taht
2019-02-01 17:26 ` Matt Taggart
2019-02-01 19:14   ` Mikael Abrahamsson
2019-02-01 19:20     ` Jonathan Morton
2019-02-01 20:42     ` David Lang
2019-02-02  6:09       ` Mikael Abrahamsson
2019-02-02  8:23         ` David Lang
2019-02-02 10:36           ` Toke Høiland-Jørgensen
2019-02-02 11:00             ` Sebastian Moeller [this message]
2019-02-02 22:55       ` Aaron Wood
2019-02-03  7:56         ` Mikael Abrahamsson
2019-02-03 22:29           ` Aaron Wood

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=CAE4EF85-765E-4079-B519-997B774C6134@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=david@lang.hm \
    --cc=swmike@swm.pp.se \
    --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