From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Realtek RTL8139 driver
Date: Mon, 28 Jan 2002 21:54:50 -0500 [thread overview]
Message-ID: <20020129025452.E7B36199BB@mail.cse.psu.edu> (raw)
I wrote the instructions in the README file for adding to 9load
based on our current copy of the source. I hadn't realised that the
'ethercards[]' array had moved from load.c to ether.c since the
distribution. So, the instructions should say
To add to 9load:
1) do the above copy;
2) in /sys/src/boot/pc/load.c after
{ "AMD79C970", amd79c970reset, },
add
{ "RTL8139", rtl8139pnp, },
and after
extern int amd79c970reset(Ether*);
add
extern int rtl8139pnp(Ether*);
3) in /sys/src/boot/pc/mkfile after
ether8003.$O\
add
ether8139.$O\
4) mk
Sorry about the confusion.
next reply other threads:[~2002-01-29 2:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-29 2:54 jmk [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-28 14:47 andrey mirtchovski
2002-01-24 16:27 jmk
2002-01-25 15:59 ` Jason Gurtz
2002-01-28 11:12 ` deicide
2002-01-28 11:12 ` north_
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=20020129025452.E7B36199BB@mail.cse.psu.edu \
--to=jmk@plan9.bell-labs.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).