From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: <Narendra_K@Dell.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<Matt_Domsch@Dell.com>, <Jordan_Hargrave@Dell.com>,
<Charles_Rose@Dell.com>
Subject: Re: [PATCH] Enable pci=bfsort by default on future Dell systems
Date: Fri, 7 Jan 2011 14:27:42 -0800 [thread overview]
Message-ID: <20110107142742.0b1bcfaa@jbarnes-desktop> (raw)
In-Reply-To: <20101214175048.GC31345@fedora-14-r710.oslab.blr.amer.dell.com>
On Tue, 14 Dec 2010 09:57:12 -0800
<Narendra_K@Dell.com> wrote:
> Hello,
>
> This patch enables pci=bfsort by default on future Dell systems.
> Please consider for inclusion if acceptable.
>
> From: Jordan Hargrave <jordan_hargrave@dell.com>
> Subject: [PATCH] Enable pci=bfsort by default on future Dell systems
>
> This patch enables pci=bfsort by default on future Dell systems.
> It reads SMBIOS type 0xB1 vendor specific record and sets pci=bfsort accordingly.
>
> Offset Name Length Value Description
>
> 04 Flags0 Word Varies Bits 9-10
> - 10:9 = 00 Unknown
> - 10:9 = 01 Breadth First
> - 10:9 = 10 Depth First
> - 10:9 = 11 Reserved
>
> 1. Any time pci=bfsort has to be enabled on a system, we need to add the model
> number of the system to the white list. With this patch, that is not required.
>
> 2. Typically, model number has to be added to the white list when the system is
> under development. With this change, that is not required.
>
> Signed-off-by: Jordan Hargrave <jordan_hargrave@dell.com>
> Signed-off-by: Narendra K <narendra_k@dell.com>
> ---
Applied, thanks.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2011-01-07 22:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 17:57 Narendra_K
2010-12-14 19:54 ` Matt Domsch
2010-12-14 20:12 ` Matthew Wilcox
2010-12-15 2:51 ` Matt Domsch
2010-12-17 16:17 ` Narendra_K
2010-12-17 18:06 ` Jesse Barnes
2010-12-20 6:54 ` Narendra_K
2011-01-07 22:27 ` Jesse Barnes [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=20110107142742.0b1bcfaa@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=Charles_Rose@Dell.com \
--cc=Jordan_Hargrave@Dell.com \
--cc=Matt_Domsch@Dell.com \
--cc=Narendra_K@Dell.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®