Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Patrick <patrick@spellingbeewinnars.org>
To: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: help with setpci "no devices at"
Date: Fri, 13 Jun 2014 12:25:45 -0400	[thread overview]
Message-ID: <539B2609.3090106@spellingbeewinnars.org> (raw)

Hi Everyone

Thanks again to Bjorn for helping me in the thread "updating firmware 
with setpci"

I have started a new thread as it's more specific than the previous one 
and might be more valuable this way in the archives.

I replaced a PCI chip on one card I am trying to copy the good PCI 
configuration space settings from another card, as-is they are very 
different and the repaired card is failing.

I found a perfect little awk script here to generate setpci commands 
from lspci -xxx  :

https://gist.github.com/jlopez-git/4594728

I ended up with setpci complaining about missing a width. I found this 
thread:
https://access.redhat.com/site/solutions/45240

It looks like older versions of the tool did not require widths to be 
specified. The awk script may be a bit dated.

I changed XX= to XX.b=
setpci -sD 04:01.0 00.b=813010e8

based on:
http://www.tutorialspoint.com/unix_commands/setpci.htm
which gave this example:
setpci -s 13:8.4 40.b=50:d0,04:0c,ff


but now I have another error:
setpci: Warning: No devices selected for "04:01.0".
setpci: Invalid width "0".


lspci shows the device at:
04:01.0 Unassigned class [ff00]: Device a101:81ff

The example showed the b near the register address but the "invalid 
width 0" error has me wondering if it's supposed to go somewhere else or 
I should be using a different width flag.

Could someone point me in the right direction ?

Thanks for reading-Patrick















             reply	other threads:[~2014-06-13 16:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13 16:25 Patrick [this message]
2014-06-13 17:44 ` help with setpci "no devices at" Patrick
2014-06-13 18:02   ` Alex Williamson

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=539B2609.3090106@spellingbeewinnars.org \
    --to=patrick@spellingbeewinnars.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