From: Greg KH <gregkh@linuxfoundation.org>
To: "Shah, Nehal-bakulchandra" <Nehal-bakulchandra.Shah@amd.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: PCI Express gen 4.0 linux support
Date: Fri, 1 Sep 2017 17:02:40 +0200 [thread overview]
Message-ID: <20170901150240.GA30459@kroah.com> (raw)
In-Reply-To: <DM5PR1201MB2488D6B1322227EE0A06E8C8A0920@DM5PR1201MB2488.namprd12.prod.outlook.com>
On Fri, Sep 01, 2017 at 11:50:12AM +0000, Shah, Nehal-bakulchandra wrote:
> Hi All,
>
>
> I would like to know that is for PCI Express gen 4.0 supported in linux ? or any discussion/patches are underway for the same?
What specifically does the kernel need to provide for 4.0 that it does
not already handle? Usually new versions of the PCIe spec are all at
the BIOS and hardware level, not at the kernel level, right?
And have you tried the latest kernel release on this type of hardware
and had problems? If so, what were the results?
thanks,
greg k-h
prev parent reply other threads:[~2017-09-01 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 11:50 PCI Express gen 4.0 linux support Shah, Nehal-bakulchandra
2017-09-01 15:02 ` Greg KH [this message]
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=20170901150240.GA30459@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Nehal-bakulchandra.Shah@amd.com \
--cc=linux-pci@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).