summaryrefslogtreecommitdiff
path: root/targets/totalimpact/briq
diff options
context:
space:
mode:
authorRudolf Marek <r.marek@assembler.cz>2009-03-26 21:45:26 +0000
committerRudolf Marek <r.marek@assembler.cz>2009-03-26 21:45:26 +0000
commit3a8565a77bbf8f41c2c5560fb2c195c71949fc8c (patch)
tree05313fc08ce0431132e78979502632a9493cbd6b /targets/totalimpact/briq
parent83da8dcf608d4b6549399581463fe484b71bca6f (diff)
During the suspend/resume programming I came to an issue that first 4KB of
memory must be clear with 0s because otherwise the resources of K8 will be totally messed up. res = probe_resource(dev, 0x100 + (reg | link)); This is called with dev = NULL and this is no good for probe_resource at all. The attached patch fixes the potential problems and of course the problem itself. On one particular place was missing test if the device really exists. This was copied to fam10 and perhaps the same issue is in v3 (DID NOT check). The rest of the patch is just very paranoid and do all checkings. Signed-off-by: Rudolf Marek <r.marek@assembler.cz> Acked-by: Myles Watson <mylesgw@gmail.com> --This line, and those below, will be igno red-- M src/devices/pci_ops.c M src/northbridge/amd/amdk8/northbridge.c M src/northbridge/amd/amdfam10/northbridge.c git-svn-id: svn://svn.coreboot.org/coreboot/trunk@4030 2b7e53f0-3cfb-0310-b3e9-8179ed1497e1
Diffstat (limited to 'targets/totalimpact/briq')
0 files changed, 0 insertions, 0 deletions