From: "David S. Miller" <davem@redhat.com>
To: beezly@beezly.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: Sun GEM card looses TX on x86 32bit PCI
Date: Tue, 12 Mar 2002 12:39:04 -0800 (PST) [thread overview]
Message-ID: <20020312.123904.78107946.davem@redhat.com> (raw)
In-Reply-To: <1015965269.1937.22.camel@monkey>
In-Reply-To: <1015887102.2051.4.camel@monkey> <20020312.093134.35196670.davem@redhat.com> <1015965269.1937.22.camel@monkey>
From: Beezly <beezly@beezly.org.uk>
Date: 12 Mar 2002 20:34:29 +0000
I had a quick fiddle around with pci_find_capability(<blah>,
PCI_CAP_ID_VPD), but it always returns NULL (i.e. no VPD). However, I've
also noticed that no-one appears to use that macro in any of the kernel
source. Is there another way to look at the VPD?
The vital product data is stored in the PCI ROM.
pci_find_capability() does not give you the VPD, it is for
capabilities indicated in PCI config space.
The VPD format in the PCI ROM is specified in the PCI-2.x
specification. To dump out the PCI ROM you'll need to
ioremap() the PCI_ROM_RESOURCE it just like we do the registers.
Then you have to enable the ROM so it will respond (by setting
PCI_ROM_ADDRESS_ENABLE in "PCI_ROM_ADDRESS" in PCI config space).
Then you can use the ioremap() cookie to read the ROM using
readl(cookie + offset).
next prev parent reply other threads:[~2002-03-12 20:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-10 20:36 Sun GEM card looses TX on x86 32bit PCI Beezly
2002-03-11 0:43 ` David S. Miller
2002-03-11 8:19 ` Beezly
2002-03-11 12:19 ` Beezly
2002-03-11 12:21 ` David S. Miller
2002-03-11 18:35 ` Beezly
2002-03-11 19:02 ` David S. Miller
2002-03-11 21:11 ` Beezly
2002-03-11 21:23 ` Beezly
2002-03-11 22:51 ` Beezly
2002-03-12 17:31 ` David S. Miller
2002-03-12 20:34 ` Beezly
2002-03-12 20:39 ` David S. Miller [this message]
2002-03-14 20:43 ` Aaron Sethman
2002-03-14 21:21 ` Aaron Sethman
2002-03-11 1:39 ` David S. Miller
2002-03-11 1:58 ` David S. Miller
2002-03-11 8:29 ` Beezly
2002-03-11 8:42 ` David S. Miller
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=20020312.123904.78107946.davem@redhat.com \
--to=davem@redhat.com \
--cc=beezly@beezly.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox