linux-kernel - [RFC] ACPI IPMI changes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1348499140-13550-1-git-send-email-mjg@redhat.com>
Date:	Mon, 24 Sep 2012 11:05:36 -0400
From:	Matthew Garrett <mjg@...hat.com>
To:	yakui.zhao@...el.com
Cc:	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
	cminyard@...sta.com
Subject: [RFC] ACPI IPMI changes 

The ACPI IPMI code doesn't seem to work on many real-world devices. Part of
that is because many shipping systems have a _CID of PNP0C01 or PNP0C02 and
the PNP core never lets the IPMI driver bind, but it's also a problem if
it's being used for AC adapter state (since they're typically built in)
and on some systems that have IPMI opregions declared outside the IPMI
device's scope (spec violation, but what else is new). These patches don't
do anything for the first problem (that's going to have to be handled in
the PNP core) but handle the latter two by ensuring that IPMI can be
initialised before any built-in ACPI drivers, and by providing support for
a fallback IPMI handler that just uses the first IPMI device in the system.

-- 
Matthew Garrett | mjg59@...f.ucam.org

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/