From owner-freebsd-stable Fri Nov 17 23:53:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-210.dsl.snfc21.pacbell.net [63.202.177.210]) by hub.freebsd.org (Postfix) with ESMTP id B7D6937B479 for ; Fri, 17 Nov 2000 23:53:21 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAI7xwF01223; Fri, 17 Nov 2000 23:59:58 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011180759.eAI7xwF01223@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: nate@yogotech.com (Nate Williams) Cc: stable@FreeBSD.ORG Subject: Re: 4.2-BETA hangs on boot In-reply-to: Your message of "Fri, 17 Nov 2000 17:01:11 MST." <14869.50887.741133.148588@nomad.yogotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Nov 2000 23:59:58 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > However, that code had problems in that it didn't work if FreeBSD had no > driver for a particular piece of hardware, and assumed the IRQ was free > even if it wasn't. Although, from hearing Mike Smith talk, the new VM86 > and PnP code should have 'informed the kernel' of all such resources > used, even if FreeBSD had no driver for the hardware. The problem is not so much whether the interrupt is free, it's whether the interrupt is *routed* anywhere. Note that in all of this discussion, almost all of the "pccard" bridges are really CardBus bridges, and many of them don't get an interrupt assigned *AT*ALL* by the BIOS by default (even though they are routed to a specific IRQ). -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message