Date: Thu, 21 Aug 2003 10:32:25 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: John Baldwin <jhb@FreeBSD.org> Cc: Perforce Change Reviews <perforce@FreeBSD.org> Subject: Re: PERFORCE change 36551 for review Message-ID: <20030821173225.GA780@dhcp42.pn.xcllnt.net> In-Reply-To: <XFMail.20030821131303.jhb@FreeBSD.org> References: <20030821164706.GA566@dhcp42.pn.xcllnt.net> <XFMail.20030821131303.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 21, 2003 at 01:13:03PM -0400, John Baldwin wrote: > > I'd still be interested to see what the MADT output from acpidump > is on one of these machines. See http://people.freebsd.org/~marcel/acpidump.txt I just made it. > What I plan to have is an ISA bus that has a identify routine > that uses ACPI to enumerate ISA devices defined in ACPI. I'm not sure I like the sound of that. We need a clear distinction between ISA and ACPI on ia64, because not all machines have ISA compatibility in their chipsets. It must therefore be possible to build kernels without ISA but still have well-known devices (from the ISA era) used as ACPI devices. Take for example the code in sio(4) that tries to detect which IRQ is raised by the device. This is perfectly valid for true ISA, but utterly and miserably fails for ACPI devices in non-ISA machines. So, you want the ISA bus attachment to be able to detect the IRQ, and have a seperate ACPI bus attachment that simply doesn't bother. This means that you need an ISA bus that doesn't double for something that isn't ISA, like ACPI. So, please. Do not blur the distinction by having it all mapped as ISA devices. I really don't want to have to shoot you :-) > PCI devices are described in ACPI, so I don't think we can make > assumptions about ACPI devices having interrupt properties. How > are you getting the interrupt number for the UART devices anyway? > Does ACPI specify an IRQ of 66 or whatever it is? Yes. > If the UART devices raise an ISA interrupt, then by my reading, > the ACPI resource should specify the ISA interrupt number (0-15), > and the MADT should include a source override that maps that > ISA interrupt number to a global interrupt number of 66 or > whatever (which maps to a SAPIC:intpin). This makes sense. It's however not how it is (unfortunately). I'll ask around. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030821173225.GA780>