From owner-freebsd-current Sun Aug 6 20:23:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8AFE537B6AB for ; Sun, 6 Aug 2000 20:23:37 -0700 (PDT) (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 VAA84892; Sun, 6 Aug 2000 21:23:31 -0600 (MDT) (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 VAA28590; Sun, 6 Aug 2000 21:23:13 -0600 (MDT) Message-Id: <200008070323.VAA28590@harmony.village.org> To: "Brandon D. Valentine" Subject: Re: vga0, atkbdc0, fdc0 attaching to ISA bus? Cc: Donn Miller , current@FreeBSD.ORG In-reply-to: Your message of "Sun, 06 Aug 2000 16:57:50 EDT." References: Date: Sun, 06 Aug 2000 21:23:13 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Brandon D. Valentine" writes: : I've got a machine with an Abit SL6 w/ AGP/PCI/CNR onboard, but no ISA : slots, and it still has an ISA to PCI bridge built in. Some of the : devices still register with the kernel on the ISA bus, even though they : are quite obviously connected to the PCI bus. I suspect that some of : these devices may be tied to the ISA bus in the BIOS for arcane PC/AT : reasons. I would be interested to know details though, if someone could : spare a moment to give an over-the-top explanation of why this is true. Well, here's the short answer: The reason you have a ISA to PCI bridge still is that the serial ports, parallel ports, floppy, keyboard and mouse devices still live on the ISA bus. They aren't full PCI nodes just yet in most hardware designs (I've yet to see a floppy, keyboard or mouse on the pci bus, but I'm sure people will tell me where I can find such beasts). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message