From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sis900
Date: Mon, 21 Apr 2003 07:38:04 -0600 [thread overview]
Message-ID: <Pine.LNX.4.44.0304210735260.19133-100000@fbsd.cpsc.ucalgary.ca> (raw)
In-Reply-To: <16035.45487.228762.749829@nanonic.hilbert.space>
here it is: http://www.acl.lanl.gov/plan9/sis900/ethersis.c
haven't used it since april last year, when i made sure it works with R4...
some work may be required to add your revision chipset in. see the top of
the file:
* some registers not appearing in the documentation
* were 'stolen' from freebsd's if_sis.c (found at
* the end of the enums -- the uncommented ones).
* eeprom reading routines come from the same driver
* but are untested (the chipset revision we have here
* reads the mac address from cmos).
andrey
On Mon, 21 Apr 2003 paurea@gsyc.escet.urjc.es wrote:
> Someone was writting a driver for the ethernet sis900. In which state
> is it?. Thanks a lot.
>
next prev parent reply other threads:[~2003-04-21 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 8:54 paurea
2003-04-21 13:38 ` andrey mirtchovski [this message]
2003-04-21 17:11 ` Geoff Collyer
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=Pine.LNX.4.44.0304210735260.19133-100000@fbsd.cpsc.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--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).