From owner-freebsd-current Wed Feb 25 15:09:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19704 for freebsd-current-outgoing; Wed, 25 Feb 1998 15:09:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA19686 for ; Wed, 25 Feb 1998 15:09:24 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 15576 invoked by uid 1000); 25 Feb 1998 23:15:51 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-022398 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 25 Feb 1998 15:15:51 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Tom Subject: Re: Help needed with DPT card + Asus M/B Cc: freebsd-current@FreeBSD.ORG, Kingson Gunawan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Feb-98 Tom wrote: > > On Wed, 25 Feb 1998, Simon Shapiro wrote: > >> On 25-Feb-98 Tom wrote: >> > >> > On Tue, 24 Feb 1998, Simon Shapiro wrote: >> > >> >> That is not it. Unless some other driver is stealing the PCI >> >> interrupt >> >> (which I do not know how to do with PCI). >> > >> > Unless it is a silly ISA device... >> >> True only if the MB allows interrupts to be shared between ISA and PCI, >> which it should not. Kingston reports that Win95 works on that MB, with >> the DPT and all. > > Hmmm, but how does a motherboard know what interupts a ISA card might > use? You certainly can't have ISA and PCI devices sharing the IRQ, but > it > is up to the operators to make sure it doesn't happen. Most MB I am familiar with route interrupts from the ISA bus to a PCI-ISA bridge. The bridge is programmable and will not pass interrupts form ISA that it was told not to. OTOH, I amy be talking about what things should have been. I think Steve Passe (amoung others) knows the definite answer here as he has to deal with it in the APIC code. > Win95 often works great in that situation, up until you address the > rogue ISA device. Or maybe it doesn't even have a driver installed for > the rogue device. Or, the driver knows about some problem with the MB and avoids it or works around it. This is why I suggested a call to DPT. It is a free call and they know about such intractions better than I do. ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message