From owner-freebsd-stable Sat Mar 25 17:12:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D457237B51B for ; Sat, 25 Mar 2000 17:12:24 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA47347; Sat, 25 Mar 2000 18:12:18 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA76635; Sat, 25 Mar 2000 18:12:07 -0700 (MST) Message-Id: <200003260112.SAA76635@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... Cc: Mitsuru IWASAKI , freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Sat, 25 Mar 2000 19:43:22 EST." References: Date: Sat, 25 Mar 2000 18:12:07 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : Ah. So what we really want is some mechanism to tell the kernel 'hey, : you! don't use this ioport/irq whatever.' (or otherwise mark some : resources as not being available to PnP devices.) I think that a null driver could easily be written. I also think that combined with the hint mechanism I posted to new-bus a couple of days ago this could be a viable way to reserve interrupts from the boot loader. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message