On 5/6/06, Krzysztof Halasa <[email protected]> wrote:
"Jon Smirl" <[email protected]> writes: > Substitute vga with the name of whatever class of device you are > working on and build it a minimal driver for it. The technique is > generic. The card in question _has_ a driver. I, for example, just need a way to write EEPROM data to it (vendor/device ID etc). The card has to be selected by PCI bus and slot (device) number, not by device class and/or IDs, because it can contain garbage and/or some generic IDs with generic device class.
Hardware like you describe violates the PCI spec and it should not be expected that Linux will support it in the general case. It sounds like this is some kind of prototype hardware. I would probably handle this by writing an unbound device driver that exposes a sysfs file for bus:slot. When you write the bus:slot to the file it would then bind to the appropriate hardware and enable it. The newly bound driver would support the driver firmware loader interface as a means of getting your data in.
I'm not against the additional driver but it has to be able to work with any specified card (as setpci does). But if it's that simple then why not do that in the PCI code instead (holding some device file open isn't a problem)? -- Krzysztof Halasa
-- Jon Smirl [email protected] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- Re: Add a "enable" sysfs attribute to the pci devices to allow userspace (Xorg) to enable devices without doing foul direct access
- From: Martin Mares <[email protected]>
- Re: Add a "enable" sysfs attribute to the pci devices to allow userspace (Xorg) to enable devices without doing foul direct access
- From: Greg KH <[email protected]>
- Re: Add a "enable" sysfs attribute to the pci devices to allow userspace (Xorg) to enable devices without doing foul direct access
- From: "Jon Smirl" <[email protected]>
- Re: Add a "enable" sysfs attribute to the pci devices to allow userspace (Xorg) to enable devices without doing foul direct access
- From: Greg KH <[email protected]>
- Re: Add a "enable" sysfs attribute to the pci devices to allow userspace (Xorg) to enable devices without doing foul direct access
- From: "Jon Smirl" <[email protected]>
- Re: Add a "enable" sysfs attribute to the pci devices to allow userspace (Xorg) to enable devices without doing foul direct access
- From: "Dave Airlie" <[email protected]>
- Re: Add a "enable" sysfs attribute to the pci devices to allow userspace (Xorg) to enable devices without doing foul direct access
- From: "Jon Smirl" <[email protected]>
- Re: Add a "enable" sysfs attribute to the pci devices to allow userspace (Xorg) to enable devices without doing foul direct access
- From: Krzysztof Halasa <[email protected]>
- Re: Add a "enable" sysfs attribute to the pci devices to allow userspace (Xorg) to enable devices without doing foul direct access
- From: "Jon Smirl" <[email protected]>
- Re: Add a "enable" sysfs attribute to the pci devices to allow userspace (Xorg) to enable devices without doing foul direct access
- From: Krzysztof Halasa <[email protected]>
- Re: Add a "enable" sysfs attribute to the pci devices to allow userspace (Xorg) to enable devices without doing foul direct access
- Prev by Date: Re: High load average on disk I/O on 2.6.17-rc3
- Next by Date: Re: [PATCH 8/14] random: Remove SA_SAMPLE_RANDOM from USB gadget drivers
- Previous by thread: Re: Add a "enable" sysfs attribute to the pci devices to allow userspace (Xorg) to enable devices without doing foul direct access
- Next by thread: Re: Add a "enable" sysfs attribute to the pci devices to allow userspace (Xorg) to enable devices without doing foul direct access
- Index(es):
 |