From: Larry Finger <Larry.Finger@lwfinger.net>
To: Jon Mason <jdmason@kudzu.us>
Cc: James Smart <james.smart@emulex.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Richard Lary <rlary@us.ibm.com>,
wey-yi.w.guy@intel.com, Stanislaw Gruszka <sgruszka@redhat.com>,
chaoming_li@realsil.com.cn
Subject: Re: Warning: iwlegacy/iwlwifi/rtlwifi : removal of PCI_CAP_ID_EXP
Date: Sat, 02 Jul 2011 11:49:18 -0500 [thread overview]
Message-ID: <4E0F4C0E.5060306@lwfinger.net> (raw)
In-Reply-To: <BANLkTi=-43qKpbb6HdYuNTna__5cxVMfoA@mail.gmail.com>
On 07/01/2011 10:08 AM, Jon Mason wrote:
> pci_is_pcie checks for a PCI-E capability offset that was determined
> by calling pci_find_capability during the PCI bus walking. Based on
> your description above this should be functionally equivalent. If
> this is not safe, then the PCI bus walking code is most likely busted
> on EEH enabled PPC systems (and that is a BIG problem).
Are there PPC systems that support PCI-E cards? I looked for one earlier and did
not find any. In particular, I wanted a machine to test the Realtek drivers for
correct big-endian operation. I settled on a Powerbook G4 so that I could test
the USB drivers.
Larry
next prev parent reply other threads:[~2011-07-02 16:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1309196346-15749-1-git-send-email-jdmason@kudzu.us>
[not found] ` <4E0CDF8B.3020505@emulex.com>
2011-07-01 14:49 ` Warning: iwlegacy/iwlwifi/rtlwifi : removal of PCI_CAP_ID_EXP James Smart
2011-07-01 15:08 ` Jon Mason
2011-07-02 16:49 ` Larry Finger [this message]
2011-07-02 17:04 ` Jon Mason
2011-07-04 1:47 ` Adrian Chadd
2011-07-06 3:15 ` Jon Mason
[not found] ` <4E0DDE5D.8040904@emulex.com>
2011-07-06 14:38 ` James Smart
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=4E0F4C0E.5060306@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--cc=james.smart@emulex.com \
--cc=jdmason@kudzu.us \
--cc=linux-wireless@vger.kernel.org \
--cc=rlary@us.ibm.com \
--cc=sgruszka@redhat.com \
--cc=wey-yi.w.guy@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;
as well as URLs for NNTP newsgroup(s).