From owner-freebsd-mobile Sat Apr 10 21:27:38 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from netrinsics.com (unknown [202.99.58.9]) by hub.freebsd.org (Postfix) with ESMTP id 2508D15118 for ; Sat, 10 Apr 1999 21:27:16 -0700 (PDT) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.9.2/8.8.7) id MAA03941 for freebsd-mobile@FreeBSD.ORG; Sun, 11 Apr 1999 12:25:26 +0800 (CST) (envelope-from robinson) Date: Sun, 11 Apr 1999 12:25:26 +0800 (CST) From: Michael Robinson Message-Id: <199904110425.MAA03941@netrinsics.com> To: freebsd-mobile@FreeBSD.ORG Subject: Re: PCIC (was Re: Any success) In-Reply-To: <199904092237.PAA00799@dingo.cdrom.com> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith writes: >> "There is no theoretical reason why a user should have to set a PCIC IRQ." >> or: >> "There exists a foolproof method for automatically determining the proper >> PCIC IRQ on all hardware supported by FreeBSD, and someone should implement >> that method." > >Both. > >The "automatic" method may require user help in the form of parametric >information, but it should in no way be pcic-specific. So presumably new-bus has a method for providing parametric IRQ allocation information for specific ISA devices in general, and as soon as new-bus is working this whole problem will go away. -Michael Robinson P.S. Right now, though, it seems we have a pcic-specific method for assigning IRQs (sysctl), and a non-pcic-specific method for assigning IRQs for all other devices that require "user help" (are there any devices besides ISA devices that require manual IRQ assignment?). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message