From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] gsoc2010 + plan9
Date: Thu, 4 Mar 2010 21:25:50 -0500 [thread overview]
Message-ID: <55b95c2fcc02ec9910e47fd33c367299@ladd.quanstro.net> (raw)
In-Reply-To: <408e17f9aeb6335970650379e8d7d401@plan9.bell-labs.com>
On Thu Mar 4 17:15:19 EST 2010, David.Eckhardt@cs.cmu.edu wrote:
> > for example, there are a number of 10/100 chipsets that have
> > good documentation that's under 100 pages. complete with
> > (oh, my) a theory of operation.
>
> Such as?
and
On Thu Mar 4 20:28:36 EST 2010, geoff@plan9.bell-labs.com wrote:
> It's not worth supporting any new 10Mb ethernet controllers,
> and new 100Mb ones are borderline.
for the pc architechture, this is certianly true. i would even bias
development toward 10 and 40gbe.
but for other platforms, i think 10/100 chipsets make a lot of sense
today. 10/100 is great for appliance-ish applications/
for example, this is a very interesting bit of hardware
(sorry, ron, mips, not arm)
http://www.ubiquitistore.com/ls2
an ethernet driver is here
https://dev.openwrt.org/browser/trunk/target/linux/atheros/patches-2.6.33/110-ar2313_ethernet.patch?rev=19906
it's a mere 1200 lines, which is just trivial in the linux world so if one
were to scare up documentation, it might be quite a dream to
program.
there were a few others i stumbled on recently. i recall reading
the datasheets for a few spi-based chipsets that looked pretty clean.
(obviously 10mbps.)
- erik
next prev parent reply other threads:[~2010-03-05 2:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 23:09 Tim Newsham
2010-03-03 23:40 ` David Leimbach
2010-03-04 1:35 ` Venkatesh Srinivas
2010-03-04 17:39 ` Balwinder S Dheeman
2010-03-04 18:04 ` erik quanstrom
2010-03-05 15:39 ` Balwinder S Dheeman
2010-03-04 18:43 ` Chad Brown
2010-03-04 19:05 ` erik quanstrom
2010-03-04 21:13 ` ron minnich
2010-03-04 21:45 ` Patrick Kelly
2010-03-05 2:55 ` erik quanstrom
2010-03-05 12:13 ` Georg Lehner
2010-03-05 1:27 ` geoff
2010-03-05 2:25 ` erik quanstrom [this message]
2010-03-08 10:57 ` Balwinder S Dheeman
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=55b95c2fcc02ec9910e47fd33c367299@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).