On Mon, 2010-06-07 at 20:52 +0800, Matthew Garrett wrote:
> On Mon, Jun 07, 2010 at 05:27:22PM +0800, yakui.zhao@xxxxxxxxx wrote:
>
> > Use the ACPI detection mechanism firstly to detect the IPMI system interface
> > so that we can know which IPMI system interface is detected in ACPI namespace and
> > then install the IPMI opregion to enable ACPI to access the BMC controller.
> > But the hardcode detection mechanism is still put in the first order.
>
> This is less than ideal. I've seen several machines where the PCI IPMI
> device is the only one to provide interrupts, so using the ACPI one and
> refusing to register the PCI one isn't really an option.
Does there exist the ACPI detection mechanism on the machines you
mentioned? If exists, does it detect the same IPMI interface with the
PCI IPMI detection mechanism?
If the two mechanisms will detect the same IPMI interface, I agree with
what you are concerned. Do you have an idea/thought to set up the
relationship between ACPI and IPMI interface? In order to enable that
AML code can access the IPMI, it should know which IPMI interface will
be accessed and create the corresponding user interface. If ACPI
mechanism will fail to register the IPMI interface, maybe it is
difficult to create the correct user interface.
Thanks
Yakui
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
