| commit | 9d265124d051c2cf6716639239609d83f736dcdb | |
| author | Daniel Yeisley <dan.yeisley@unisys.com> | |
| Mon, 5 Dec 2005 12:06:43 +0000 (5 07:06 -0500) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Mon, 9 Jan 2006 20:13:18 +0000 (9 12:13 -0800) | ||
| tree | 24f84b02d4a4506606af4f6d17c3a90fd914e825 | treesnapshot (tar.gz zip) |
| parent | 81f154427c0c50b6492d454abf98e15c1c2e354e | commitdiff |
[PATCH] PCI Quirk: 1K I/O space granularity on Intel P64H2
I've implemented a quirk to take advantage of the 1KB I/O space
granularity option on the Intel P64H2 PCI Bridge. I had to change
probe.c because it sets the resource start and end to be aligned on 4k
boundaries (after the quirk sets them to 1k boundaries). I've tested
this patch on a Unisys ES7000-600 both with and without the 1KB option
enabled. I also tested this on a 2 processor Dell box that doesn't have
a P64H2 to make sure there were no negative affects there.
Signed-off-by: Dan Yeisley <dan.yeisley@unisys.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
I've implemented a quirk to take advantage of the 1KB I/O space
granularity option on the Intel P64H2 PCI Bridge. I had to change
probe.c because it sets the resource start and end to be aligned on 4k
boundaries (after the quirk sets them to 1k boundaries). I've tested
this patch on a Unisys ES7000-600 both with and without the 1KB option
enabled. I also tested this on a 2 processor Dell box that doesn't have
a P64H2 to make sure there were no negative affects there.
Signed-off-by: Dan Yeisley <dan.yeisley@unisys.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| drivers/pci/probe.c | diffblobblamehistory | |
| drivers/pci/quirks.c | diffblobblamehistory |