SCANPCI(1) General Commands Manual SCANPCI(1)NAME
scanpci - scan/probe PCI buses
SYNOPSIS
scanpci [-v12OfV]
DESCRIPTION
Scanpci is a utility that can be used to scan PCI buses and report information about the configuration space settings for each PCI device.
On most platforms, scanpci can only be run by the root user.
OPTIONS -v Print the configuration space information for each device in a verbose format. Without this option, only a brief description is
printed for each device.
-x Show hexadecimal dump of the first 64 bytes of each PCI device's configuration space. For CardBus bridges, the first 128 bytes are
dumped instead. This option can be repeated to dump all 256 or 4096 bytes, but doing so might cause scanpci (or the system) to
crash because some devices cannot tolerate reads of undefined portions of their configuration space.
-1 Use PCI config type 1.
-2 Use PCI config type 2.
-f Used in conjunction with the above two options, this forces the specified configuration type to be used for config space access.
-O Use the OS's PCI config space access mechanism to access the PCI config space (when available).
-V n Set the verbosity level to n for the internal PCI scanner. This is primarily for debugging use.
SEE ALSO pcitweak(1)AUTHORS XFree86 Version 4.7.0 SCANPCI(1)
Check Out this Related Man Page
PCITWEAK(1) General Commands Manual PCITWEAK(1)NAME
pcitweak - read/write PCI config space
SYNOPSIS
pcitweak -l
pcitweak -r PCI-ID [-b|-h] offset
pcitweak -w PCI-ID [-b|-h] offset value
DESCRIPTION
Pcitweak is a utility that can be used to examine or change registers in the PCI configuration space. On most platforms pcitweak can only
be run by the root user.
OPTIONS -l Probe the PCI buses and print a line for each detected device. Each line contains the bus location (bus:device:function), chip
vendor/device, card (subsystem) vendor/card, revision, class and header type. All values printed are in hexadecimal.
-r PCI-ID
Read the PCI configuration space register at offset for the PCI device at bus location PCI-ID. PCI-ID should be given in the form
bus:device:function, with each value in hexadecimal. By default, a 32-bit register is read.
-w PCI-ID
Write value to the PCI configuration space register at offset for the PCI device at bus location PCI-ID. PCI-ID should be given in
the form bus:device:function, with each value in hexadecimal. By default, a 32-bit register is written.
-b Read or write an 8-bit value (byte).
-h Read or write a 16-bit value (halfword).
SEE ALSO scanpci(1)AUTHORS
David Dawes (dawes@xfree86.org).
XFree86 Version 4.7.0 PCITWEAK(1)
:confused:
Hi, everybody.
Pleeeeese HLP!!!
I write PCI device driver for bridge controller PCI-VME bus in freeBSD 2.2.
And firs run function probe():
static char* probe(tag, type).
Whuy probe() don't work for my vendorID and deviceID (bridge controller and videoadapter). But... (1 Reply)
hi i have a file content like
my_file:
1US8738297897918000
000
000
i used
while IFS= read line
do
echo "$line" | grep '^\
then
last=`echo "$line" | cut -c 3-20`
echo "$last"
fi
done < $my_file
but it is writing blank spaces into the o/p fie (1 Reply)
Hi all,
Am working on an enhancement to access Solaris PCI Config Space. I got basic pci config space properties like vendor-id using di_node system calls. But i am not able to access the extended configuration space. Can you please suggest an approach to access the pci extended configuration... (0 Replies)
From the nessus scanner tool report i got below vulnerability
PCI DSS Compliance : Insecure Communication Has Been Detected
http://www.tenable.com/plugins/index.php?view=single&id=56208
As per the description given in above link - I am not able to understand
How to find insecure port... (2 Replies)
F7FA22C9 I O SYSJ2 UNABLE TO ALLOCATE SPACE IN FILE SYSTEM
edit by bakunin: until you are willing to phrase a decent question i am unwilling to tolerate such a spammed thread here.
- Thread closed - (0 Replies)