From owner-freebsd-hackers Wed May 6 17:40:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28319 for freebsd-hackers-outgoing; Wed, 6 May 1998 17:40:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28200 for ; Wed, 6 May 1998 17:39:57 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id SAA25911; Wed, 6 May 1998 18:39:38 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id SAA06961; Wed, 6 May 1998 18:39:33 -0600 Date: Wed, 6 May 1998 18:39:33 -0600 Message-Id: <199805070039.SAA06961@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: Nate Williams , Archie Cobbs , stefan@promo.de (Stefan Bethke), luigi@labinfo.iet.unipi.it, freebsd-hackers@FreeBSD.ORG Subject: Re: ISA-PnP w\o BIOS support? In-Reply-To: <199805062212.PAA00530@antipodes.cdrom.com> References: <199805061517.JAA05337@mt.sri.com> <199805062212.PAA00530@antipodes.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Things is, this falls really short for non-ISA/non-PnP devices as well. > > No, it doesn't. But I may not have answered your specific qualms. > > > Think hot-swappable devices, and devices that *really* no one knows > > about? > > Yes, what about them? How about a concrete problem rather than FUD? There's no FUD. You just erased my specific examples. > > Also, devices that can use IRQ's, but don't necessarily need > > them. How do you say 'go ahead and use it', vs. 'don't bother'. > > Huh? You must specifically be talking about the resource starvation > case where the "can but don't have to" device comes up before a "must > have" device and takes the last interrupt. No, I'm talking about cases where hardware *can* use IRQ's, but don't need them. > Firstly, there aren't too many devices in the "can but don't have to" > class, so this is a pathalogical example. But it's an example of something we need to have now. (Like, if it were there, I could use it today.) Right not, to get a 'real' interrupt, you must be an ISA device. Otherwise, you've got to hope for the best. This is simply bogus. And, sysctl is a *huge* hack that's completely incapable of dealing with it. You can't tell a device to not use an interrupt via a sysctl, since by the time the syctl is active it's much too late. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message