Asus F2A85-M: Fix the _CRS PCI0 bus info
On Asus F2A85-M, the Linux kernel complains that the _CRS method does
not specify the number of PCI busses.
[FIRMWARE BUG]: ACPI: no secondary bus range in _CRS
Just put there 256. This should be part of re-factoring of the whole
ACPI stuff.
The same change was already done for the AMD Brazos (SB800) boards,
based on commit »Persimmon DSDT: Add secondary bus range to PCI0«
(4733c647
) [1].
[1] http://review.coreboot.org/2592
Change-Id: I06f90ec353df9198a20b2165741ea0fe94071266
Signed-off-by: Rudolf Marek <r.marek@assembler.cz>
Reviewed-on: http://review.coreboot.org/3320
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Tested-by: build bot (Jenkins)
Reviewed-by: Martin Roth <martin.roth@se-eng.com>
Reviewed-by: David Hubbard <david.c.hubbard+coreboot@gmail.com>
This commit is contained in:
parent
01c095ff4c
commit
1b22827cf0
|
@ -1334,6 +1334,22 @@ DefinitionBlock (
|
|||
} /* end Ac97modem */
|
||||
|
||||
Name(CRES, ResourceTemplate() {
|
||||
/* Set the Bus number and Secondary Bus number for the PCI0 device
|
||||
* The Secondary bus range for PCI0 lets the system
|
||||
* know what bus values are allowed on the downstream
|
||||
* side of this PCI bus if there is a PCI-PCI bridge.
|
||||
* PCI busses can have 256 secondary busses which
|
||||
* range from [0-0xFF] but they do not need to be
|
||||
* sequential.
|
||||
*/
|
||||
WordBusNumber (ResourceProducer, MinFixed, MaxFixed, PosDecode,
|
||||
0x0000, /* address granularity */
|
||||
0x0000, /* range minimum */
|
||||
0x00FF, /* range maximum */
|
||||
0x0000, /* translation */
|
||||
0x0100, /* length */
|
||||
,, PSB0) /* ResourceSourceIndex, ResourceSource, DescriptorName */
|
||||
|
||||
IO(Decode16, 0x0CF8, 0x0CF8, 1, 8)
|
||||
|
||||
WORDIO(ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange,
|
||||
|
|
Loading…
Reference in New Issue