[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #17651] pci config space access from userspace

From: anonymous
Subject: [bug #17651] pci config space access from userspace
Date: Fri, 8 Sep 2006 13:34:03 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20060406 Firefox/ (Debian-1.5.dfsg+


                 Summary: pci config space access from userspace
                 Project: The GNU Hurd
            Submitted by: None
            Submitted on: Friday 09/08/2006 at 13:34 UTC
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: Matthew Wilcox
        Originator Email: matthew@wil.cx
             Open/Closed: Open
         Reproducibility: Every Time
              Size (loc): None
         Planned Release: None
                  Effort: 0.00



The HURD needs to provide interfaces to let tools such as lspci and setpci
access PCI configuration space.  The current pciutils backends for the hurd
support only reading a dump file and access through i386 ports (0xcf8 et al).
 This has the following problems:
 - non-i386 architectures do not work in this way
 - this mechanism doesn't support access to extended pci config space (bytes
256-4095) as found on PCI-X 2.0 and PCI Express cards.
 - this mechanism doesn't support PCI domains/segments which are increasingly
commonly found on workstation i386 machines as well as other architectures and
large i386 servers

Feel free to ask me about the Linux implementations of accessing PCI config
space; I propose you come up with an abstraction somewhat like sysfs (ie you
have a directory per PCI device named something like 0001:04:02.3 and a file
inside that called 'config'), but I'm interested in discussing other
mechanisms that you might come up with.


Carbon-Copy List:

CC Address                          | Comment
Available only the item webpage     | Originator Email


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]