27 Sep, 2006

2 commits

  • Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     
  • Export the PCI_BUS_FLAGS_NO_MSI flag of a PCI bus in the sysfs files
    of its parent device and make it writable. Could be used to:
    * disable MSI on a device which has not been blacklisted yet
    * allow MSI when some setpci hacks enable MSI support (for instance
    on the ServerWorks HT2000 chipset where the MSI HT cap is disabled
    by default).
    Architecture where some bus have no parent chipset cannot use this
    strategy to change MSI support.

    If the chipset does not have a subordinate bus, its 'bus_msi' file
    is empty.

    Also document and warn about the possible danger of changing the flag.

    Signed-off-by: Brice Goglin
    Signed-off-by: Greg Kroah-Hartman

    Brice Goglin
     

01 Jul, 2006

1 commit


28 Jun, 2006

1 commit


22 Jun, 2006

2 commits

  • From: Doug Thompson

    This patch adds the 'broken_parity_status' sysfs attribute file to a PCI device.
    Reading this attribute a userland program can determine if PCI device provides false
    positives (value of 1) in its generation of PCI Parity status, or not (value of 0).
    As PCI devices are found to be 'bad' in this regard, userland programs can also set
    the appropriate value (root access only) of a faulty device. This per device
    information will be used in the EDAC PCI Parity scanner code in a future patch once
    this interface becomes available.

    Signed-off-by: Doug Thompson
    Signed-off-by: Greg Kroah-Hartman

    Doug Thompson
     
  • …e (Xorg) to enable devices without doing foul direct access

    This patch adds an "enable" sysfs attribute to each PCI device. When read it
    shows the "enabled-ness" of the device, but you can write a "0" into it to
    disable a device, and a "1" to enable it.

    This later is needed for X and other cases where userspace wants to enable
    the BARs on a device (typical example: to run the video bios on a secundary
    head). Right now X does all this "by hand" via bitbanging, that's just evil.
    This allows X to no longer do that but to just let the kernel do this.

    Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
    CC: Peter Jones <pjones@redhat.com>
    Acked-by: Dave Airlie <airlied@linux.ie>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

    Arjan van de Ven
     

24 Mar, 2006

1 commit


29 Oct, 2005

1 commit

  • Some PCI adapters (eg. ipr scsi adapters) have an exposure today in that they
    issue BIST to the adapter to reset the card. If, during the time it takes to
    complete BIST, userspace attempts to access PCI config space, the host bus
    bridge will master abort the access since the ipr adapter does not respond on
    the PCI bus for a brief period of time when running BIST. On PPC64 hardware,
    this master abort results in the host PCI bridge isolating that PCI device
    from the rest of the system, making the device unusable until Linux is
    rebooted. This patch is an attempt to close that exposure by introducing some
    blocking code in the PCI code. When blocked, writes will be humored and reads
    will return the cached value. Ben Herrenschmidt has also mentioned that he
    plans to use this in PPC power management.

    Signed-off-by: Brian King
    Cc: Benjamin Herrenschmidt
    Signed-off-by: Andrew Morton
    Signed-off-by: Greg Kroah-Hartman

    drivers/pci/access.c | 89 ++++++++++++++++++++++++++++++++++++++++++++++++
    drivers/pci/pci-sysfs.c | 20 +++++-----
    drivers/pci/pci.h | 7 +++
    drivers/pci/proc.c | 28 +++++++--------
    drivers/pci/syscall.c | 14 +++----
    include/linux/pci.h | 7 +++
    6 files changed, 134 insertions(+), 31 deletions(-)

    Brian King
     

22 Sep, 2005

1 commit


11 Sep, 2005

1 commit


28 Jun, 2005

1 commit

  • This is an updated version of Ben's fix-pci-mmap-on-ppc-and-ppc64.patch
    which is in 2.6.12-rc4-mm1.

    It fixes the patch to work on PPC iSeries, removes some debug printks
    at Ben's request, and incorporates your
    fix-pci-mmap-on-ppc-and-ppc64-fix.patch also.

    Originally from Benjamin Herrenschmidt

    This patch was discussed at length on linux-pci and so far, the last
    iteration of it didn't raise any comment. It's effect is a nop on
    architecture that don't define the new pci_resource_to_user() callback
    anyway. It allows architecture like ppc who put weird things inside of
    PCI resource structures to convert to some different value for user
    visible ones. It also fixes mmap'ing of IO space on those archs.

    Signed-off-by: Benjamin Herrenschmidt
    Signed-off-by: Michael Ellerman
    Signed-off-by: Andrew Morton
    Signed-off-by: Greg Kroah-Hartman

    Michael Ellerman
     

21 Jun, 2005

3 commits


18 May, 2005

1 commit


04 May, 2005

1 commit


17 Apr, 2005

1 commit

  • Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds