Date: Mon, 24 Feb 2003 12:41:13 -0800 From: Marcel Moolenaar <marcel@xcllnt.net> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-arch@FreeBSD.ORG Subject: Re: [RFC] splitting of conf/NOTES Message-ID: <20030224204113.GC661@athlon.pn.xcllnt.net> In-Reply-To: <20030224.060315.63039059.imp@bsdimp.com> References: <20030224064129.GA13290@dhcp53.pn.xcllnt.net> <20030224185033.H6037-100000@gamplex.bde.org> <20030224094856.GA21088@athlon.pn.xcllnt.net> <20030224.060315.63039059.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 24, 2003 at 06:03:15AM -0700, M. Warner Losh wrote: > > The big problem is with the ISA bus. The ISA bus has too many > overloaded meanings right now. It means those funky old cards that we > know and love, as well as devices that look like they are on an ISA or > ISA-like bus, but really are just a few gates in some bridge chip. Maybe ACPI helps out here a bit. On i386 and ia64, where the ISA legacy rears its ugly head the most (I think), ACPI can be used to enumerate the legacy devices. In that sense I treat ACPI as a bus. The tricky part still is that there's a lot of assumptions about the BIOS and the BIOS data area that, if I understand correctly, goes beyond plain ISA and is best described as PC specific. I think this is more a driver issue than anything else. I think if we can tackle ISA or PC legacy fairly decently, we should have something that would work good in general. > This whole discussion shows that our tree is still to x86 centric > (with alpha hacks for extra lovin' goodness). With non-i386 platforms the common case now, I think it's time to bring the balance back. Anakin, bring me my lightsaber... and coffee... no, the green one... -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030224204113.GC661>