From: Brantley Coile <brantley@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Status of 3C589D driver (and BCM57XX)
Date: Fri, 3 Feb 2006 08:30:12 -0500 [thread overview]
Message-ID: <e256117032b3615cb9e60f3b4903d9ed@coraid.com> (raw)
In-Reply-To: <e0ac85f90602021857y177f472fn633128880906d509@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 27 bytes --]
We would LOVE to test it!
[-- Attachment #2: Type: message/rfc822, Size: 3941 bytes --]
From: Christopher Nielsen <cnielsen@pobox.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Status of 3C589D driver (and BCM57XX)
Date: Thu, 2 Feb 2006 18:57:35 -0800
Message-ID: <e0ac85f90602021857y177f472fn633128880906d509@mail.gmail.com>
On 2/2/06, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
> I have started examining the FreeBSD bge driver in the hope it will make the
> basis for a driver port. (Anyone out there have a pointer to
> hardware doc for the 57XX series? I've looked in the obvious places
> but can't find anything.)
the only docs for the BCM57XX family are the open source drivers.
jmk has sent me what he started on for a driver, and he and i are
actively working on a driver for the broadcom chips. he has hardware
to tes it, and i have time to write it. if you'd like to be a tester,
that would be helpful.
--
Christopher Nielsen
"They who can give up essential liberty for temporary
safety, deserve neither liberty nor safety." --Benjamin Franklin
next prev parent reply other threads:[~2006-02-03 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 2:43 Lyndon Nerenberg
2006-02-03 2:57 ` Christopher Nielsen
2006-02-03 3:12 ` Lyndon Nerenberg
2006-02-03 13:30 ` Brantley Coile [this message]
2006-02-03 14:20 ` uriel
2006-02-03 14:24 ` Dan Cross
2006-03-02 16:08 ` Gabriel Diaz
2006-02-03 3:23 ` jmk
2006-02-03 10:13 ` Martin Neubauer
2006-02-03 16:02 ` jmk
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=e256117032b3615cb9e60f3b4903d9ed@coraid.com \
--to=brantley@coraid.com \
--cc=9fans@cse.psu.edu \
/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).