pci: move doc to readme

br2

@@ -14,6 +14,7 @@ BR2_TARGET_ROOTFS_EXT2_SIZE="512M"
 # remove the init.d file for now.
 #BR2_PACKAGE_IFUPDOWN_SCRIPTS=n
 
+# Misc
 BR2_CCACHE=y
 # Otherwise our precious debug would break!
 BR2_CCACHE_USE_BASEDIR=n
@@ -25,6 +26,7 @@ BR2_PACKAGE_BUSYBOX_CONFIG_FRAGMENT_FILES="../busybox_config_fragment"
 BR2_PACKAGE_DHRYSTONE=y
 BR2_PACKAGE_FILE=y
 BR2_PACKAGE_OVERRIDE_FILE="../buildroot_override"
+BR2_PACKAGE_PCIUTILS=y
 # For qemu-ga on guest. TODO: do something with it, and document it.
 BR2_PACKAGE_QEMU=y
 BR2_PACKAGE_STRACE=y
@@ -66,33 +68,3 @@ BR2_PACKAGE_TRACE_CMD=y
 BR2_PACKAGE_DTC=y
 BR2_PACKAGE_DTC_PROGRAMS=y
 BR2_PACKAGE_HOST_DTC=y
-
-# Provides setpci and a lspci more advanced than Busybox's
-#
-# setpci can read and write to PCI configuration registers.
-#
-# Read is possible from Linux with:
-#
-#     hexdump /sys/bus/pci/devices/0000:00:05.0/config
-#
-# and /dev/mem can of course do both reads and writes,
-# but setpci provies nice human readable register names, e.g.:
-#
-#     setpci --dumpregs
-#
-# then and then get the values with either bus or device id:
-#
-#     setpci -s 0000:00:05.0 BASE_ADDRESS_0
-#     setpci -d 1234:11e9 BASE_ADDRESS_0
-#
-# Note however that BASE_ADDRESS_0 also appears when you do:
-#
-#     lspci -v
-#
-# Then you can try messing with that address with:
-#
-#     devmem2 0xfeb52000 w 0x12345678
-#
-# which for our pci_min device fires interrupts.
-#
-BR2_PACKAGE_PCIUTILS=y