[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7A25B56E4BE99C4283EB931CD1A40E1101587039@pdsmsx414.ccr.corp.intel.com>
Date: Tue, 29 Jul 2008 10:36:49 +0800
From: "Zhao, Yu" <yu.zhao@...el.com>
To: "Matthew Wilcox" <matthew@....cx>
Cc: <linux-kernel@...r.kernel.org>, <eric@...olt.net>,
"Matthew Wilcox" <willy@...ux.intel.com>,
<jbarnes@...tuousgeek.org>
Subject: RE: [PATCH 3/3] PCI: Add pci_read_base() API
On Tuesday, July 29, 2008 9:50 AM, Matthew Wilcox <mailto:matthew@....cx> wrote:
> On Tue, Jul 29, 2008 at 09:22:03AM +0800, Zhao, Yu wrote:
>> Greetings,
>>
>> It would be nice if people can have an enhanced
> pci_update_resource to update non-standard BARs probed by
> pci_read_base.
>
> Yes, that would be a natural addition to the API. However, we don't
> tend to add APIs until we have a use case for them. Do you have
> anything in the pipeline that could use this feature? I'm quite happy
> to write the code for you if you do.
There is a new PCIe extended capability SR-IOV, which defines 6 additional BARs encapsulated inside the capability. I'm writing code to support it, and will be using your APIs to probe and update these non-standard BARs.
The SR-IOV specification can be found at:
http://www.pcisig.com/members/downloads/specifications/iov/sr-iov1.0_11Sep07.pdf
Thanks.
>
> --
> Intel are signing my paycheques ... these opinions are still mine
> "Bill, look, we understand that you're interested in selling us this
> operating system, but compare it to ours. We can't possibly take such
> a retrograde step."
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists