[PATCH] add PCI ROMs to sysfs

From: Jesse Barnes (jbarnes_at_engr.sgi.com)
Date: 07/30/04

  • Next message: Jesse Barnes: "Re: Exposing ROM's though sysfs" 
    To: linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz, Jon Smirl <jonsmirl@yahoo.com>
Date:	Fri, 30 Jul 2004 14:09:05 -0700

    Per a big thread earlier today, this patch adds a 'rom' file to sysfs in the
    same place where we currently have 'config', 'irq', etc.

    Note that the ROM is *not* cached, so userspace will have to save the ROM when
    a device is first detected if the card doesn't support address cycles to ROM
    space at the same time as other memory accesses. (I'm still open to changing
    this if people feel strongly, but as it stands, the 'rom' file is only
    slightly more dangerous than the 'config' file.)

    Jon, am I missing something or is it possible for us to cache the ROM in
    userspace when it receives the hotplug event? I saw your DRM code, and for
    the case of ROMs at a nonstandard address, we can fixup the address for
    pci_dev->resource[PCI_ROM_RESOURCE] in pci-quirks, can't we?

    Thoughts? I've tried to add cleanup code, but I'm not sure how acceptable it
    is and I don't have any way of testing it.

    Thanks,
    Jesse

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Jesse Barnes: "Re: Exposing ROM's though sysfs"

    Relevant Pages