Home Explore Help
Register Sign In
phyus
/
linux-vybrid_public
8
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Tree: 0cc6bfe901
Branches Tags
linux-vybrid_pu...
/
Documentation
/
ABI
/
testing
/
sysfs-bus-pci

sysfs-bus-pci 2.3 KB
History Raw

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354 
  1. What:		/sys/bus/pci/drivers/.../bind
    2. 

  2. Date:		December 2003
    3. 

  3. Contact:	linux-pci@vger.kernel.org
    4. 

  4. Description:
    5. 

  5. 		Writing a device location to this file will cause
    6. 

  6. 		the driver to attempt to bind to the device found at
    7. 

  7. 		this location.	This is useful for overriding default
    8. 

  8. 		bindings.  The format for the location is: DDDD:BB:DD.F.
    9. 

  9. 		That is Domain:Bus:Device.Function and is the same as
    10. 

  10. 		found in /sys/bus/pci/devices/.  For example:
    11. 

  11. 		# echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/bind
    12. 

  12. 		(Note: kernels before 2.6.28 may require echo -n).
    13. 

  13. 

  14. What:		/sys/bus/pci/drivers/.../unbind
    15. 

  15. Date:		December 2003
    16. 

  16. Contact:	linux-pci@vger.kernel.org
    17. 

  17. Description:
    18. 

  18. 		Writing a device location to this file will cause the
    19. 

  19. 		driver to attempt to unbind from the device found at
    20. 

  20. 		this location.	This may be useful when overriding default
    21. 

  21. 		bindings.  The format for the location is: DDDD:BB:DD.F.
    22. 

  22. 		That is Domain:Bus:Device.Function and is the same as
    23. 

  23. 		found in /sys/bus/pci/devices/. For example:
    24. 

  24. 		# echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/unbind
    25. 

  25. 		(Note: kernels before 2.6.28 may require echo -n).
    26. 

  26. 

  27. What:		/sys/bus/pci/drivers/.../new_id
    28. 

  28. Date:		December 2003
    29. 

  29. Contact:	linux-pci@vger.kernel.org
    30. 

  30. Description:
    31. 

  31. 		Writing a device ID to this file will attempt to
    32. 

  32. 		dynamically add a new device ID to a PCI device driver.
    33. 

  33. 		This may allow the driver to support more hardware than
    34. 

  34. 		was included in the driver's static device ID support
    35. 

  35. 		table at compile time.  The format for the device ID is:
    36. 

  36. 		VVVV DDDD SVVV SDDD CCCC MMMM PPPP.  That is Vendor ID,
    37. 

  37. 		Device ID, Subsystem Vendor ID, Subsystem Device ID,
    38. 

  38. 		Class, Class Mask, and Private Driver Data.  The Vendor ID
    39. 

  39. 		and Device ID fields are required, the rest are optional.
    40. 

  40. 		Upon successfully adding an ID, the driver will probe
    41. 

  41. 		for the device and attempt to bind to it.  For example:
    42. 

  42. 		# echo "8086 10f5" > /sys/bus/pci/drivers/foo/new_id
    43. 

  43. 

  44. What:		/sys/bus/pci/devices/.../vpd
    45. 

  45. Date:		February 2008
    46. 

  46. Contact:	Ben Hutchings <bhutchings@solarflare.com>
    47. 

  47. Description:
    48. 

  48. 		A file named vpd in a device directory will be a
    49. 

  49. 		binary file containing the Vital Product Data for the
    50. 

  50. 		device.  It should follow the VPD format defined in
    51. 

  51. 		PCI Specification 2.1 or 2.2, but users should consider
    52. 

  52. 		that some devices may have malformatted data.  If the
    53. 

  53. 		underlying VPD has a writable section then the
    54. 

  54. 		corresponding section of this file will be writable.
    55.