yhlu at tyan.com
Sun Dec 12 15:27:01 CET 2004
Actually for cpu0 link1, in the auto.c stage, incoherent.c only need to
handle bus 0, because ht device only at bus 0 (8131 and 8111).
For cpu1 link2, in the auto.c stage, incoherent device only need to handle
to bus 4, because we put the device on bus 4 according to setting in 0xe4 of
The purpose of incoherent.c is set the HT-link and width and return
need_reset. Auto.c will according to need_reset from coherent.c and
incoherent.c to reset in auto.c stage.
So in the northbrige.c of hardwaremain stage will not need to reset and make
ht speed and width effective.
The HT devices in the same HT chain are always in the same bus.
From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of Stefan Reinauer
Sent: Saturday, December 11, 2004 12:12 PM
To: linuxbios at clustermatic.org
Subject: collapsing devices.
I am desperate, still getting:
LinuxBIOS-220.127.116.11-fallback Sat Dec 11 20:30:55 CET 2004 starting...
setting up resource map....done.
04 nodes initialized.
Pretending to collapse device 74501022 on bus 00000000
Pretending to collapse device 74501022 on bus 00000004
* Why would only bus 0 and 4 be collapsed, but not bus 1,2,3?
Linuxbios mailing list
Linuxbios at clustermatic.org
More information about the coreboot