summaryrefslogtreecommitdiffstats
path: root/net/tipc
diff options
context:
space:
mode:
authorJesse Barnes <jbarnes@virtuousgeek.org>2007-03-24 11:03:32 -0700
committerGreg Kroah-Hartman <gregkh@suse.de>2007-05-02 19:02:35 -0700
commit40ee9e9f8d52d85f2446bbdda7823a3f1de62f3f (patch)
treebad4181bf7e0f7dc37b69522f0588be9788b269d /net/tipc
parent8d7d86e9bd377e5779bf3c8da03b27d823c039b4 (diff)
downloadkernel-crypto-40ee9e9f8d52d85f2446bbdda7823a3f1de62f3f.tar.gz
kernel-crypto-40ee9e9f8d52d85f2446bbdda7823a3f1de62f3f.tar.xz
kernel-crypto-40ee9e9f8d52d85f2446bbdda7823a3f1de62f3f.zip
PCI: fix sysfs rom file creation for BIOS ROM shadows
At one time, if a BIOS ROM shadow was detected for the boot video device (stored at offset 0xc0000), we'd set a special resource flag, IORESOURCE_ROM_SHADOW, so that the sysfs ROM file code could handle it properly. That broke along the way somewhere though, so current kernels will be missing 'rom' files in sysfs if the video device doesn't have an explicit ROM BAR. This patch fixes the regression by moving the video fixup quirk to a little later in the boot cycle (to avoid having its work undone by PCI resource allocation) and checking in the PCI sysfs code whether a rom file should be created due to a shadow resource, which is also moved to a little later in the boot cycle so it will occur after the video fixup. Tested and works on my i386 test box. Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'net/tipc')
0 files changed, 0 insertions, 0 deletions