From owner-freebsd-current Tue Jan 18 22:44:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 8FA99150CC; Tue, 18 Jan 2000 22:44:14 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id HAA33350; Wed, 19 Jan 2000 07:43:58 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: boot messages for pci devices... In-reply-to: Your message of "Tue, 18 Jan 2000 18:10:00 PST." Date: Wed, 19 Jan 2000 07:43:58 +0100 Message-ID: <33348.948264238@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: > > >> On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote: >> > fxp0: port 0xc400-0xc43f mem 0xefe00000-0xefefffff,0xeffff000-0xefffffff irq 9 at device 14.0 on pci0 >> >> Agreed. For a PCI card all I want to know is what it is, and what IRQ it >> was assigned. A single line should be suffient. > >Do you even need to know what IRQ it was assigned? It seems to me that IRQ, >like IO-PORT, is only needed if you're either interested in such stuff or to >catch conflicts (both are under bootverbose) The IRQ is useful to me at least, since the ISA/PCI irq distribution is rather hackish and non-trivial to get right at times. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message