From: Jeff Garzik <jgarzik@pobox.com>
To: Greg KH <greg@kroah.com>
Cc: "Durairaj, Sundarapandian" <sundarapandian.durairaj@intel.com>,
Andi Kleen <ak@muc.de>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
marcelo.tosatti@cyclades.com, "Carbonari,
Steven" <steven.carbonari@intel.com>,
"Seshadri, Harinarayanan" <harinarayanan.seshadri@intel.com>
Subject: Re: [BK PATCH] PCI Express patches for 2.4.27-pre3
Date: Wed, 26 May 2004 13:30:33 -0400 [thread overview]
Message-ID: <40B4D439.3080504@pobox.com> (raw)
In-Reply-To: <20040526170345.GB28578@kroah.com>
Greg KH wrote:
> On Wed, May 26, 2004 at 11:59:43AM +0530, Durairaj, Sundarapandian wrote:
>
>>I think its important that we have this patch for 2.4 kernel as well, as
>>it will enable the PCI express devices to access extended config space
>>(above 256 bytes), where all Advance feature of PCI Express config
>>registers resides.
>
>
> Are there any drivers or devices on the market today that need access to
> this extended config space?
"need"? Not AFAIK. Not yet, anyway.
Most PCI-Ex devices I've seen are designed such that they work under
OS's and drivers that do not support the extended configuration area.
Jeff
next prev parent reply other threads:[~2004-05-26 17:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 6:29 [BK PATCH] PCI Express patches for 2.4.27-pre3 Durairaj, Sundarapandian
2004-05-26 13:48 ` Matthew Wilcox
2004-05-26 17:03 ` Greg KH
2004-05-26 17:30 ` Jeff Garzik [this message]
[not found] <1ZuS0-1b4-15@gated-at.bofh.it>
[not found] ` <1ZuS3-1b4-35@gated-at.bofh.it>
2004-05-24 22:21 ` Andi Kleen
2004-05-24 22:40 ` Greg KH
[not found] ` <1ZE52-8sy-15@gated-at.bofh.it>
[not found] ` <1ZFaF-10N-13@gated-at.bofh.it>
[not found] ` <1ZIrV-3xS-7@gated-at.bofh.it>
[not found] ` <1ZJHt-4At-33@gated-at.bofh.it>
2004-05-25 13:38 ` Andi Kleen
[not found] ` <1ZLpV-5YK-37@gated-at.bofh.it>
[not found] ` <1ZNBb-7QA-1@gated-at.bofh.it>
2004-05-25 17:14 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2004-05-24 21:01 Greg KH
2004-05-24 21:02 ` Greg KH
2004-05-24 21:02 ` Greg KH
2004-05-25 6:53 ` Arjan van de Ven
2004-05-25 8:00 ` Greg KH
2004-05-25 11:32 ` Matthew Wilcox
2004-05-25 12:54 ` Marcelo Tosatti
2004-05-25 13:01 ` Arjan van de Ven
2004-05-25 13:24 ` Matthew Wilcox
2004-05-25 14:41 ` Greg KH
2004-05-26 2:49 ` Jeff Garzik
2004-05-26 4:29 ` Greg KH
2004-05-25 14:40 ` Greg KH
2004-05-25 16:59 ` Marcelo Tosatti
2004-05-25 17:05 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40B4D439.3080504@pobox.com \
--to=jgarzik@pobox.com \
--cc=ak@muc.de \
--cc=greg@kroah.com \
--cc=harinarayanan.seshadri@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=marcelo.tosatti@cyclades.com \
--cc=steven.carbonari@intel.com \
--cc=sundarapandian.durairaj@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox