Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP
id AA1591 ; Tue, 23 Feb 93 14:49:47 EST
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!network.ucsd.edu!usc!howland.reston.ans.net!gatech!destroyer!cs.ubc.ca!unixg.ubc.ca!kakwa.ucs.ualberta.ca!acs.ucalgary.ca!cpsc.ucalgary.ca!xenlink!fsa.ca!deraadt
From: deraadt@fsa.ca (Theo de Raadt)
Subject: Re: [386BSD] Followup: WD8013 card
In-Reply-To: julian@tfs.com's message of 6 Feb 93 18: 34:32 GMT
Message-ID: <DERAADT.93Feb18022343@newt.fsa.ca>
Sender: news@fsa.ca
Nntp-Posting-Host: newt.fsa.ca
Organization: little lizard city
References: <C1FuJ7.4A9@rot.qc.ca> <1993Jan26.205504.24467@fcom.cc.utah.edu>
<DERAADT.93Feb1010127@newt.newt.cuc.ab.ca>
<1993Feb6.183432.9396@tfs.com>
Date: Thu, 18 Feb 1993 09:23:43 GMT
Lines: 69
In article <1993Feb6.183432.9396@tfs.com> julian@tfs.com (Julian Elischer) writes:
In article <DERAADT.93Feb1010127@newt.newt.cuc.ab.ca> deraadt@newt.cuc.ab.ca (Theo de Raadt) writes:
[deleted]
>it generally keeps interrupts off. I'm not a fan of this at all. If we
>were to write the probe routines more carefully, we could do this:
>
[deleted]
>controller ahb0 at isa? port "IO_AHB0" bio irq ? drq ? vector ahbintr
[deleted]
>
>
>If this method is used, we don't have to worry about getting all those
>nasty little interrupt vectors correct any longer, and trying to watch
>out for errors. The isa_configure() routine can watch for conflicts,
>since it is the routine that calls each of the probe routines. Notice how
>the ahb controller does not have a drq line either? Some controllers can
>tell you what DRQ they are configured to use..
Actually, the AHB controller DOES do this..
there is only an entry in the config file for drq and irq because
the config program and autoconfigure routine do the wrong thing
if I put a ? in there. The driver figures out the
irq and the drq used is an EISA drq. The bustek does the same
except that it can decide to use a normal drq as well as the EISA dma.
I noticed that in the AHB controller. I was greatly confused by the
code, because it collided with another patch that I had which fixed
DRQ enabling. Julian, I wish you had fixed the config program then --
it seems to me that patches to hidden subsystems like that never
really make it into effect. Actually, there are now 4 sets of patches
to the config program (of which 3 conflict with each other). Oh joy.
>Every day I spent in 386BSD, I am amazed at how much stuff got lost in
>the transition from BSD4.3tahoe to BSD4.3reno to NET2 to 386BSD...
The reason is that it was such a huge re-write to get to 386bsd that
some files were left at the 'works but is not perfect' stage so that
work could proceed at some other place..
Having DOS information in ufs/ufs_disksubr.c turned my stomach.
Calling it /usr/src/sys.386bsd turned my stomach too. Having over 40
#ifdef {hp300,vax,tahoe}/#endif pairs just *poof* deleted so that
people porting would have no idea that this piece of code might be ohh
just a wee bit nonportable...
But, no what I was really talking about was that entire directories
were deleted, and numerous version numbers on files were from before
NET2. Perhaps we can say that 386BSD is not really based on NET2, it
just tried to look like NET2 when it was finished..
The autoconfigure code is a neat piece that one person could take on
and add this functionallity to.. (need to touch each driver too)
volunteers?
I've mashed most of them to operate much more like on the vax (one big
change is to not do the XXattach() until we've printed out the address
and interrupt information. This helps in debugging of improperly
configured machines MASSIVELY). Bruce Evans, with a lot more PC
experience, has also added a bunch more sophistication to them (though
not in a BSD vax-like fashion). I believe that anyone making efforts
in this area though is doomed to making the effort only for his own
benefit. I don't think these changes will make it into general use
(pity, damn pity..)
<tdr.
--
This space not left unintentionally unblank. deraadt@fsa.ca