Lines Matching +full:device +full:- +full:id +full:- +full:base
34 .Fl l Oo Fl BbceVv Oc Op Ar device
36 .Fl a Ar device
38 .Fl r Oo Fl b | h Oc Ar device addr Ns Op : Ns Ar addr2
40 .Fl w Oo Fl b | h Oc Ar device addr value
42 .Fl D Oo Fl b | h | x Oc Ar device bar Op Ar start Op Ns Ar count
53 normally only the super-user.
60 .Bd -literal
61 foo0@pci0:0:4:0: class=0x010000 rev=0x01 hdr=0x00 vendor=0x1000 device=0x000f \
63 bar0@pci0:0:5:0: class=0x000100 rev=0x00 hdr=0x00 vendor=0x88c1 device=0x5333 \
65 none0@pci0:0:6:0: class=0x020000 rev=0x00 hdr=0x00 vendor=0x10ec device=0x8029 \
73 device in question, the driver name will be
76 each detached device that is encountered.
80 hex digits, followed by the sub-class and the interface bytes.
81 The third column prints the device's revision.
98 device, it is a
99 .Em multi-function
100 device, which contains several (similar or independent) functions on
103 The sixth and seventh columns contain the vendor ID and the device ID of the
104 device.
115 .Bd -literal
116 drv selector class rev hdr vendor device subven subdev
122 All fields retain the same definition as with the non-compact form.
143 .Bd -literal
144 window[1c] = type I/O Port, range 16, addr 0x5000-0x8fff, enabled
164 will list any base address registers
166 that are assigned resources for each device.
168 .Bd -literal
169 bar [10] = type Memory, range 32, base 0xda060000, size 131072, enabled
182 The base and size indicate the start and length of the BAR's address window,
190 will list any capabilities supported by each device.
195 .Bd -literal
196 cap 10[40] = PCI-Express 1 root port
201 prefix is the capability ID in hexadecimal.
204 The format of the text after the equals sign is capability-specific.
207 .Bd -literal
213 prefix is the extended capability ID in hexadecimal.
216 The format of the text after the equals sign is capability-specific.
222 will list any errors reported for this device in standard PCI error registers.
224 the PCI-express device status register,
231 will attempt to load the vendor/device information database, and print
232 vendor, device, class and subclass identification strings for each device.
240 provided by each device.
242 .Bd -literal
248 prefix indicates if the keyword is read-only
250 or read-write
257 .Ar device
262 will only list details about a single device instead of all devices.
269 .Ar device .
270 The device can be identified either by a device name if the device is
272 Selectors identify a PCI device by its address in PCI config space and
275 .Bl -bullet -offset indent -compact
277 .Li pci Ns Va domain Ns \&: Ns Va bus Ns \&: Ns Va device Ns \&: \
280 .Li pci Ns Va bus Ns \&: Ns Va device Ns \&: Ns Va function Ns
282 .Li pci Ns Va bus Ns \&: Ns Va device Ns
286 An optional leading device name followed by @ and an optional final colon
291 All numbers are base 10.
297 determines whether any driver has been assigned to the device
300 An exit status of zero indicates that the device has a driver;
301 non-zero indicates that it does not.
307 of device
319 of device
329 to convert them to human-readable dump,
330 or redirect into a file to save the snapshot of the device state.
347 indicates a halfword (two-byte) operation.
349 indicates a quadword (four-byte) operation.
354 PCI vendor and device information is read from
377 .An -nosplit
394 It might be useful to give non-root users access to the
401 to provide the device with a driver KLD, and reading of configuration space