Subject: Re: new EISA autoconfiguration code committed...
To: Michael L. VanLoon -- HeadCandy.com <michaelv@HeadCandy.com>
From: None <Chris_G_Demetriou@NIAGARA.NECTAR.CS.CMU.EDU>
List: current-users
Date: 02/27/1996 02:33:25
> So, what is going to be necessary to make the BT742/747/757 use the
> EISA stuff?  Make a BT7XX-specific driver, separate from the ISA one?

I see it as being mostly a matter of splitting the driver up into
front-ends which touch the busses, and a back end that touches the
hardware.  This shouldn't be too hard.

Some people (I honestly forget who, right now) are working on
code/infrastructure to make this a bit easier...  they can/should
speak up, and discuss their plans.


Worth noting that to do this right, you really need to create some way
to deal with the aha/bt conflicts/interactions, perhaps with one
'universal' probe routine, to check for any of the boards.


chris