From owner-freebsd-hackers Thu Sep 18 00:29:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA15108 for hackers-outgoing; Thu, 18 Sep 1997 00:29:09 -0700 (PDT) Received: from usr06.primenet.com (tlambert@usr06.primenet.com [206.165.6.206]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA15101 for ; Thu, 18 Sep 1997 00:29:07 -0700 (PDT) Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id AAA19024; Thu, 18 Sep 1997 00:28:55 -0700 (MST) From: Terry Lambert Message-Id: <199709180728.AAA19024@usr06.primenet.com> Subject: Re: INB question To: sos@sos.freebsd.dk (Søren Schmidt) Date: Thu, 18 Sep 1997 07:28:55 +0000 (GMT) Cc: tlambert@primenet.com, hackers@freebsd.org In-Reply-To: <199709180725.JAA01170@sos.freebsd.dk> from "Søren Schmidt" at Sep 18, 97 09:25:33 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > OK, I give up: other than calling INT 0x15, AH=0xC0, how do I detect > > whether a machine is MCA or not without hard coding it in my kernel > > configuration file? > > You giving up, so easy ?? naw.... > > There must be some device or something on a MCA board thats different > form the ISA/EISA/PCI systems, probe for that... Well, I can look for MCA cards. That assumes I have MCA cards installed or locally bridged (I have an MCA SCSI on the motherboard, so that'll do my machine, but not anyone else's). > > I need an MCA bus detect. 8-(. > > The only thing I really know about the MCA bus is that I avoid it > like the plaque, besides that I'm not too familliar with it, but > a detect routine cant be that difficult to make... Heh. That's what I thought when I bought the thing and drug out all that old ABIOS code about 6 months ago... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.