Updated the READMEs

diff --git a/README b/README
index 32f5fa2f784e9af88d4dd3e4a12209c09d6f07ac..dbb9890d8c09e730579463a9ae96e5154173c4d2 100644 (file)
--- a/README
+++ b/README
@@ -1,6 +1,6 @@
 This package contains the PCI Utilities, version @VERSION@.
 
-Copyright (c) 1997--2012 Martin Mares <mj@ucw.cz>
+Copyright (c) 1997--2014 Martin Mares <mj@ucw.cz>
 
 All files in this package can be freely distributed and used according
 to the terms of the GNU General Public License, either version 2 or
@@ -22,7 +22,7 @@ In runs on the following systems:
        Solaris/i386    (direct port access)
        Aix             (via /dev/pci and odmget)
        GNU Hurd        (direct port access)
-       Windows         (direct port access)
+       Windows         (direct port access, see README.Windows for caveats)
        CYGWIN          (direct port access)
        BeOS            (via syscalls)
        Haiku           (via /dev/misc/poke)
@@ -100,6 +100,9 @@ for new entries via network.
 
 The pci.ids file is also mirrored at http://pciids.sourceforge.net/
 
+On Linux systems with a recent enough version of libudev, UDEV's HWDB
+database is consulted when pci.ids lacks the device.
+
 
 4. Getting new versions
 ~~~~~~~~~~~~~~~~~~~~~~~
@@ -111,7 +114,6 @@ The tarball can be downloaded at the following places:
 
        ftp://atrey.karlin.mff.cuni.cz/pub/linux/pci/
        ftp://ftp.kernel.org/pub/software/utils/pciutils/ (expect a couple of hours delay)
-       ftp://metalab.unc.edu/pub/Linux/hardware/ (expect a couple of days delay)
 
 There is also a public GIT tree at:
 

diff --git a/README.Windows b/README.Windows
index 7a85fdaa3ef3a86f2ecb8731798a58aeff28438d..5f73dd41e7163dbbf2720456a625bdaca48014db 100644 (file)
--- a/README.Windows
+++ b/README.Windows
@@ -9,3 +9,13 @@ from http://www.internals.com/.
 
 However, you need to use win32/config.{h,mk} instead of the automatically
 generated lib/config.{h,mk} as lib/configure does not run on Windows.
+
+================================================================================
+BEWARE: The current implementation pokes I/O ports to access the PCI devices
+directly. This leads to several problems: some devices are invisible, extended
+PCIe configuration space is not available, and there are many potential race
+conditions. Instead, libpci should use the proper Windows drivers.
+
+Unfortunately, the Windows port currently lacks a maintainer. If you are willing
+to step up and fix the issues, please let me know.  -- Martin Mares
+================================================================================