RE: [PATCH] Support for 1K I/O space granularity on the Intel P64H2

From: Yeisley, Dan P.
Date: Wed Nov 23 2005 - 13:57:17 EST

The problem with implementing this with a quirk is this line:
res->end = limit + 0xfff;

That hard coded value of 0xfff is the problem. I suppose I could make
it a variable and initialize it to 0xfff and then set it to 0x3ff in the

I'll take a look at doing it that way (and try to fix my line wrap


-----Original Message-----
From: Greg KH [mailto:gregkh@xxxxxxx]
Sent: Wednesday, November 23, 2005 13:18
To: Yeisley, Dan P.
Cc: linux-kernel@xxxxxxxxxxxxxxx
Subject: Re: [PATCH] Support for 1K I/O space granularity on
the Intel P64H2

On Wed, Nov 23, 2005 at 01:02:52PM -0500, Yeisley, Dan P. wrote:
> The Intel P64H2 PCI bridge has the ability to allocate I/O space with
> 1KB granularity. I've written a patch against to take
> advantage of this option. I've tested it on the latest Unisys
> ES7000-600.

Shouldn't this be made into a pci quirk somehow?

> linux-
> --- linux- 2005-11-11
> -0500

Your patch is linewrapped and can't be applied :(


greg k-h
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at