Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!yarrina.connect.com.au!belfast.dcd.wa.gov.au!belfast.dcd.wa.gov.au!not-for-mail From: juliane@belfast.dcd.wa.gov.au (Julian Elischer) Newsgroups: comp.os.386bsd.development Subject: Re: [Q] How should config file and device probe relate Date: 6 Sep 1993 10:54:53 +0800 Organization: Dept of Community Development, Perth, Australia Lines: 34 Distribution: world Message-ID: <26e8pt$b9h@belfast.dcd.wa.gov.au> References: <2663rn$3k6@vixen.cso.uiuc.edu> NNTP-Posting-Host: belfast.dcd.wa.gov.au Keywords: probe config drivers In article <2663rn$3k6@vixen.cso.uiuc.edu> rkb55989@uxa.cso.uiuc.edu (Rafal Boni) writes: > (a) Initialize the board to use it's stored configuration, > and if this configuration does not match that given in the > the config file, fail the probe > (b) Initialize the board to use the parameters given in the > config file, ignoring all paramters stored in the board's > NVRAM, and thus force the board to fit the config file's > idea of where the board should be > (2) How is this handled on 4.4/Sun/other BSD or BSD-ish systems??? Well, I can say what I do for the SCSI code.. (in 386BSD/derivatives) Most of the scsi boards allow you to read the settings.. assuming a board is at the location (ioport) I expect, then I read the DMA and IRQ off the board and change the values in the table derived from the config file. These figures can then be checked for clashes just as config'd figures would be (if the system fully supported such checks). In the case of the EISA 1742, I even get the ioport values from the card (you can do that with EISA). this is not option a or b ... In the config file you can just leave out the drq and ioport entries, indicating that they will be supplied later. Unfortunatly you can't leave out the irq value (or set it to ?) becasue if you do, it won't generate an interrupt vector for you. (I speak of 386bsd 0.1.. this may have changed with NetBSD, and I will know more about that soon when I get my copy) julian