Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!mel.dit.csiro.au!david From: david@mlb.geomechanics.csiro.au (David Le Blanc) Subject: Re: Problem with 386BSD and Network Message-ID: <david.715825003@mlb.geomechanics.csiro.au> Sender: news@mel.dit.csiro.au Organization: CSIRO DIT (Melb.) References: <Bu3nKA.21q@nicedel.north.de> <34cNqB1w165w@student.business.uwo.ca> Date: 7 Sep 92 00:16:43 GMT Lines: 24 >> ne0 ethernet address 00:00:4d:21:65:97 at 0x300 irq9 on isa >I have a wd elite 16 on irq 2, and the machine comes back as irq 9 also. Just a point to you all. Due to the utter rubbish that the PC motherboard must conform to (you know, the IBM original :-)) It is forced to act like an original AT. AT architecture has a problem with the interrupt hardware (a conflict somewhere but I cannot remember the specifics) and the hardware automatically takes interrupt 2, and cascades it so that it is now in the SECOND interrupt controller. This 'cascading' of interrupts is done mostly invisibly, but you must remember that interrupts on a pc go 1 9 3 4 5 6 7 8. Then you directly program the second controller. Its stupid, but its backward compatible with the XT (as if anybody cares!) >mark@student.business.uwo.ca (Mark Bramwell CS Staff) >Western Business School -- London, Ontario -- David Le Blanc : Email: david@mlb.geomechanics.csiro.au : `Sort of a cross between a Jaguar CSIRO Division of Geomechanics, : and a freight train.' the Alien P.O. Box 54 Mt Waverley 3149 : in Alien^3.