Re: Add a "enable" sysfs attribute to the pci devices to allow userspace (Xorg) to enable devices without doing foul direct access

[Krzysztof Halasa <khc@pm.waw.pl>]

"Jon Smirl" <jonsmirl@gmail.com> writes:

>> 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

What exactly does it violate?

> 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.

No. Just one of the final steps of production, or in-system update.

> 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.

What is also needed is that end users perform this task from time to
time. They generally don't want to have to compile the kernel :-)

You know, even now it can be done (entirely in userspace), and only
enabling the device seems a bit dangerous.
-- 
Krzysztof Halasa
-
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/