Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Luis E. Garcia" <luis@bitamins.net>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] trying a pcengines box
Date: Wed, 20 Apr 2016 00:12:50 -0700	[thread overview]
Message-ID: <CALnBQ5=zvvnWjhe0nyQufgNFGV-LYR01jsfgSoMkUx6t9UYrOg@mail.gmail.com> (raw)
In-Reply-To: <20160420055843.GA9772@radio2.ebirdie>

[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]

I have both boards and can say that they both very good networking
platforms - the apu1 has the small issue of the Realtek drivers for the
ethernet ports, Pascal has solved that i the apu2 by going with Intel
ethernet ports - My guess is that they won't do a full marketing push on
the apu2 until the bios for it is feature-complete (it's very close now).


On Tuesday, April 19, 2016, Erkki Lintunen <erkki.lintunen@iki.fi> wrote:

> * Dave Taht <dave.taht@gmail.com <javascript:;>> [2016-04-19 21:07:52
> -0700]:
>
> > http://pcengines.ch/apu1d4.htm
>
> May it be you have missed their latest apu2 board with a better cpu?
>
> http://pcengines.ch/apu2b2.htm
>
> According to their price list apu2 with 4GB ram costs the same as
> apu1d4. A strange thing is that PC Engines is a bit shy on telling about
> apu2 and only link to apu2 product page I could find is very briefly on
> the bottom of their front page.
>
> - Erkki
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net <javascript:;>
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

[-- Attachment #2: Type: text/html, Size: 1749 bytes --]

  parent reply	other threads:[~2016-04-20  7:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20  4:07 Dave Taht
2016-04-20  5:58 ` Erkki Lintunen
2016-04-20  7:09   ` Dave Taht
2016-04-20  7:12   ` Luis E. Garcia [this message]
2016-04-20  7:29     ` Dave Taht
2016-04-20 22:01       ` Luis E. Garcia
2016-04-23  0:42     ` Dave Taht
2016-04-23  1:00       ` Luis E. Garcia
2016-04-23  1:29         ` Luis E. Garcia
2016-04-23  1:39           ` Dave Taht
2016-04-23  2:31             ` Dave Taht
2016-04-23  5:14               ` Luis E. Garcia
2016-04-23  5:42                 ` Dave Taht
2016-04-23  5:45                   ` Luis E. Garcia
2016-04-24  7:24                     ` Dave Taht
2016-04-24 16:50                       ` Dave Taht
2016-04-24 18:01                         ` Luis E. Garcia
2016-04-23  9:52                   ` Alan Jenkins
2016-04-23  1:30         ` Dave Taht
2016-04-23  1:34           ` Outback Dingo

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='CALnBQ5=zvvnWjhe0nyQufgNFGV-LYR01jsfgSoMkUx6t9UYrOg@mail.gmail.com' \
    --to=luis@bitamins.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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