From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dan Cross <cross@math.psu.edu>
Message-Id: <200111142233.RAA23393@augusta.math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ideas for a new install procedure
In-Reply-To: <20011114213222.E1198199ED@mail.cse.psu.edu>
Cc:
Date: Wed, 14 Nov 2001 17:33:10 -0500
Topicbox-Message-UUID: 23481318-eaca-11e9-9e20-41e7f4b1d025

In article <20011114213222.E1198199ED@mail.cse.psu.edu> you write:
>actually, i'd say the real problem is writing all the required
>drivers in the first place, not the dynamic loading of
>the same.  no, that's not right.  the real problem is getting
>the data required to be able to write the drivers.

I disagree.  With no mechanism to deliver those drivers, they
don't do much good, nor does obtaining the information needed
to write them.  :-)

>so, who volunteers to write what?

I volunteer to write drivers for the SiS900 ethernet (done, sans a
few small things), the SiS5597 VGA interface (working on it), and
the C-Media audio chip in the NIC (I forget the exact model number).
I'd also like to look into the CS4624 audio chip in the Thinkpad,
and maybe into porting (as opposed to rewriting) the Adaptec 78xxx
driver from Unix.  The last is probably more ambitious than I am
prepared to work on right now.  As part of the audio chip support,
I plan to utterly divorce the audio framework from the soundblaster
family, and say that everything is based on PCM audio samples,
instead.

>perhaps a list of need-driver/will-attempt on the wiki?

That's an excellent idea.

	- Dan C.