summaryrefslogtreecommitdiff
path: root/src/mainboard/bcom
diff options
context:
space:
mode:
authorMike Loptien <mike.loptien@se-eng.com>2013-03-15 13:22:32 -0600
committerStefan Reinauer <stefan.reinauer@coreboot.org>2013-03-17 19:54:23 +0100
commit9c3d112bb686f1c044aeb501ef810e2fb8c9310e (patch)
tree83f9a869407dde9ebebd0b340aa2a77096d11f2e /src/mainboard/bcom
parent061c66406ffebb298ba06ac7ecf7e14c5d55cc24 (diff)
ASROCK Fam14 DSDT: Add OSC method
The _OSC method is used to tell the OS what capabilities it can take control over from the firmware. This method is described in chapter 6.2.9 of the ACPI spec v3.0. The method takes 4 inputs (UUID, Rev ID, Input Count, and Capabilities Buffer) and returns a Capabilites Buffer the same size as the input Buffer. This Buffer is generally 3 Dwords long consisting of an Errors Dword, a Supported Capabilities Dword, and a Control Dword. The OS will request control of certain capabilities and the firmware must grant or deny control of those features. We do not want to have control over anything so let the OS control as much as it can. The _OSC method is required for PCIe devices and dmesg checks for its existence and issues an error if it is not found. This is the same change made to Persimmon with Change-ID I149428: http://review.coreboot.org/#/c/2684/ Change-Id: I2701d915338294bdade2ad334b22a51db980892e Signed-off-by: Mike Loptien <mike.loptien@se-eng.com> Reviewed-on: http://review.coreboot.org/2739 Tested-by: build bot (Jenkins) Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
Diffstat (limited to 'src/mainboard/bcom')
0 files changed, 0 insertions, 0 deletions