Messages in this thread | | | Date | Fri, 6 Jan 2006 11:15:08 -0600 | From | Matt Domsch <> | Subject | Re: [PATCH 2.6.15 1/2] ia64: use i386 dmi_scan.c |
| |
On Thu, Jan 05, 2006 at 05:02:00PM -0700, Bjorn Helgaas wrote: > On Thursday 05 January 2006 10:54, Bjorn Helgaas wrote: > > On Thursday 05 January 2006 10:37, Matt Domsch wrote: > > > This system (Dell PowerEdge 7250, very very similar to an Intel > > > 4-way Itanium2 server) doesn't have an SPMI table, but it does have > > > the IPMI information in the SMBIOS table. > > > > But the IPMI device *should* be described in the ACPI namespace, so > > using acpi_bus_register_driver() should be sufficient. > > You mentioned on IRC that /sys/firmware/acpi/namespace didn't > contain anything that looked like an IPMI device. Try dumping the > actual DSDT and looking there -- I'm not sure everything makes it > into /sys/firmware/acpi/... > > Use the latest "pmtools" from here: > http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils > > and "iasl" to disassemble it. > > I did this on an Intel Tiger, and didn't see any "IPI" devices in the > namespace either. I think it's a firmware bug if the hardware > is there but not described in the namespace. > > So maybe you'd have to grub through SMBIOS to workaround > the firmware defect.
Indeed. I updated the BIOS to the latest available, and it doesn't list the IPMI controller in the ACPI namespace. FWIW, this is effectively an Intel S870BN4 "Tiger4" system. FWIW2, the Dell PowerEdge x8xx line (current shipping EM64T servers) doesn't have the IPMI controller in the ACPI namespace either.
I reworked the patch, such that on EFI-capable systems, it uses efi.smbios to find the _DMI_ table header, and on all non-EFI systems, continues the brute force search from 0xF0000 as before.
Thanks, Matt
-- Matt Domsch Software Architect Dell Linux Solutions linux.dell.com & www.dell.com/linux Linux on Dell mailing lists @ http://lists.us.dell.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |