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
PCCBB(4) BSD Kernel Interfaces Manual PCCBB(4)NAME
pccbb -- cardbus bridge driver
SYNOPSIS
device cbb
device pccard
device cardbus
device exca
DESCRIPTION
The pccbb driver implements the Yenta specification for CardBus bridges.
The following PCI cardbus and pcmcia bridges are supported:
Cirrus Logic PD6832
Cirrus Logic PD6833
Cirrus Logic PD6834
O2micro OZ6812
O2micro OZ6832
O2micro OZ6833
O2micro OZ6836
O2micro OZ6860
O2micro OZ6872
O2micro OZ6912
O2micro OZ6922
O2micro OZ6933
O2micro OZ6972
O2Micro OZ711E1
O2Micro OZ711M1
Ricoh RL4C475
Ricoh RL4C476
Ricoh RL4C477
Ricoh RL4C478
TI PCI-1031
TI PCI-1130
TI PCI-1131
TI PCI-1210
TI PCI-1211
TI PCI-1220
TI PCI-1221
TI PCI-1225
TI PCI-1250
TI PCI-1251
TI PCI-1251B
TI PCI-1260
TI PCI-1260B
TI PCI-1410
TI PCI-1420
TI PCI-1450
TI PCI-1451
TI PCI-1510
TI PCI-1515
TI PCI-1520
TI PCI-1530
TI PCI-1620
TI PCI-4410
TI PCI-4450
TI PCI-4451
TI PCI-4510
TI PCI-4520
TI PCI-[67]x[12]1
TI PCI-[67]x20
ENE CB710
ENE CB720
ENE CB1211
ENE CB1255
ENE CB1410
ENE CB1420
Toshiba ToPIC95
Toshiba ToPIC95B
Toshiba ToPIC97
Toshiba ToPIC100
TUNABLES
The driver supports the following tunable parameters, which may be added to /boot/loader.conf or set via the sysctl(8) command:
hw.cbb.debug Non-zero values cause more verbose information to be printed to aid in debugging problems with the bridge chipset.
SEE ALSO cardbus(4), pccard(4), exca(4)BSD July 21, 2004 BSD
: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)