Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Aaron Wood <woody77@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] WRT1900AC support finally in OpenWRT -> New Cero Dev platform?
Date: Thu, 8 Jan 2015 09:56:38 -0800	[thread overview]
Message-ID: <CAA93jw5N6xyTWC-O50pKGDtr0sA1oQGQTqopapU7BU8PLY_pSQ@mail.gmail.com> (raw)
In-Reply-To: <CALQXh-Msu64fLWGi91w3sY2iB+sG9DEZaiYR2Gxiv+44ug9v7Q@mail.gmail.com>

On Wed, Jan 7, 2015 at 8:12 PM, Aaron Wood <woody77@gmail.com> wrote:
> So it appears that Marvell pushed a bunch of patches to OpenWRT on
> Christmas, and as a result, trunk OpenWRT (kernel 3.18) can run, and run
> pretty well, on the 1900AC.
>
> https://forum.openwrt.org/viewtopic.php?pid=258634#p258634

The rest of that thread was not particularly encouraging.

I don't have at 1900AC. I do have the netgear X4 sitting on a shelf
awaiting better support.

> dual-core 1.2GHz ARM.  Given my experience with processors like the iMX 6,
> this should be light-years ahead of the WNDR3800 in terms of CPU
> performance.  Perhaps this will let the sqm scripts go well above 100Mbps?

as the sqm-scripts work well on even the lowest end modern x86 system,
I will argue that what is needed is mostly larger caches on the arms.
Over the holidays I snagged a bunch of arm based platforms to (I'd
hoped) more easily test (with decent flash and memory)

xgene: boots, the root password is not published, then the serial port
went flaky
u-droid U1: got two, both boot, get an IP, then crash 3 seconds later, no logs
                 even though there are 4 A5 cores, SMP support doesn't
work yet in linux
u-droid U3: doesn't even boot
radxa rock-lite (Seems to need uboot and linux flashed from a special utility)
(the rock2 seemed promising)

My enthusiasm for hacking on teeny little boxes was subsequently
dimmed, and I went back to wrestling with vivado and the paralllelas.

If anybody in the bay area wants to try to bring up any of these boxes
to usefulness,
I will gladly make christmas presents of them and hand deliver.

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



-- 
Dave Täht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks

      parent reply	other threads:[~2015-01-08 17:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08  4:12 Aaron Wood
2015-01-08 16:52 ` Joel Wirāmu Pauling
2015-01-08 17:56 ` Dave Taht [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=CAA93jw5N6xyTWC-O50pKGDtr0sA1oQGQTqopapU7BU8PLY_pSQ@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=woody77@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