From: "H. Peter Anvin" <hpa@zytor.com>
To: Ben Greear <greearb@candelatech.com>
Cc: "Pan, Jacob jun" <jacob.jun.pan@intel.com>,
Robert Hancock <hancockrwd@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"jbarnes@virtuousgeek.org" <jbarnes@virtuousgeek.org>
Subject: Re: Regression: 2.6.34 boot fails on E5405 system, bisected: de08e2c26
Date: Wed, 14 Jul 2010 11:47:29 -0700 [thread overview]
Message-ID: <4C3E0641.4020706@zytor.com> (raw)
In-Reply-To: <4C3E0073.7070302@candelatech.com>
On 07/14/2010 11:22 AM, Ben Greear wrote:
>
> Is there at least a maximum number of capabilities that can exist so that
> you can limit the loop by that?
>
Well, 3072 bytes and a minimum size of 4 bytes, so 768. However, a
capability ID of 0000 or FFFF means no capabilities (PCIe 2.01 sec
7.9.1-2), so we should terminate the search on finding one of those
capability ID.
[Also note: bits 21:20 are reserved and need to be masked, per PCIe 2.01
7.9.3.]
The spec seems to imply that capabilities should be sequential, but I
really don't know if that is actually the case in the field.
-hpa
next prev parent reply other threads:[~2010-07-14 18:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 0:36 Regression: 2.6.34 boot fails on E5405 system, bisected: de08e2c26 Ben Greear
2010-07-14 1:17 ` Ben Greear
2010-07-14 1:56 ` Robert Hancock
2010-07-14 2:22 ` Ben Greear
2010-07-14 3:29 ` Robert Hancock
2010-07-14 14:14 ` Ben Greear
2010-07-14 15:36 ` Pan, Jacob jun
2010-07-14 16:09 ` Ben Greear
2010-07-14 16:11 ` Ben Greear
2010-07-14 17:06 ` Ben Greear
2010-07-14 18:19 ` Pan, Jacob jun
2010-07-14 18:22 ` Ben Greear
2010-07-14 18:47 ` H. Peter Anvin [this message]
2010-07-14 18:25 ` H. Peter Anvin
2010-07-14 18:35 ` H. Peter Anvin
2010-07-14 18:41 ` Ben Greear
2010-07-14 2:19 ` Jesse Barnes
2010-07-14 2:24 ` Ben Greear
2010-07-14 18:52 ` H. Peter Anvin
2010-07-14 18:59 ` Jesse Barnes
2010-07-14 19:01 ` Pan, Jacob jun
2010-07-14 19:55 ` H. Peter Anvin
2010-07-15 16:38 ` Ben Greear
2010-07-16 17:33 ` Pan, Jacob jun
2010-07-16 18:28 ` H. Peter Anvin
2010-07-14 19:03 ` H. Peter Anvin
2010-07-14 19:27 ` Ben Greear
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=4C3E0641.4020706@zytor.com \
--to=hpa@zytor.com \
--cc=greearb@candelatech.com \
--cc=hancockrwd@gmail.com \
--cc=jacob.jun.pan@intel.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.