Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	 bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: suggestions for building a better switch?
Date: Wed, 17 Dec 2014 07:09:57 -0800	[thread overview]
Message-ID: <CAA93jw6MNutsSvOsnxRB5kXeJbq8AgUS9aNsfj_uSYnyLS5cnQ@mail.gmail.com> (raw)

OK, I am ranting here... and looking for suggestions:

https://plus.google.com/u/0/107942175615993706558/posts/TM3A43PhTq8

If anyone knows of something better than a zynq to start with, please
post.... If there are any zynq based boards that are better than the
zedboard (picozed?) please post... any other suggestions for design
tools, IP, processes, etc... post.... I'm fed up, time to go do
something about it.

Secondly I am looking over the design tools for riscv and liking what
I see, compared to vivado...

Thirdly I am trying to fix the mips profiler.

-- 
Dave Täht

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

                 reply	other threads:[~2014-12-17 15:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw6MNutsSvOsnxRB5kXeJbq8AgUS9aNsfj_uSYnyLS5cnQ@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=bloat@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