Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: RE: [PATCH] 2.6.14.2  Support for 1K I/O space granularity on the Intel P64H2
Date: Wed, 23 Nov 2005 13:57:36 -0500
Message-ID: <94C8C9E8B25F564F95185BDA64AB05F6028E120C@USTR-EXCH5.na.uis.unisys.com>
Thread-Topic: [PATCH] 2.6.14.2  Support for 1K I/O space granularity on the Intel P64H2
Thread-Index: AcXwWq5obGxyb4O6SqmDYN5Sq17hjgABHgMQ
From: "Yeisley, Dan P." <dan.yeisley@unisys.com>
To: "Greg KH" <gregkh@suse.de>
Cc: <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1351
Lines: 45

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
quirk.

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

Thanks,
Dan


-----Original Message-----
From: Greg KH [mailto:gregkh@suse.de] 
Sent: Wednesday, November 23, 2005 13:18
To: Yeisley, Dan P.
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.14.2 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 2.6.14.2 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-2.6.14.2-en1k/drivers/pci/probe.c
> --- linux-2.6.14.2/drivers/pci/probe.c	2005-11-11
00:33:12.000000000
> -0500

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

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/