Re: Exposing ROM's though sysfs

[Martin Mares]

Hello!

> Reasons for ROMs in sysfs:

Good ones, although I believe than re-initializing cards after resume
should better be in the kernel.

> The only time the ROM will get cached is when you load a kernel device
> driver for a card that implements minimalistic PCI decoding (very few
> cards) and the driver asks for it. The driver would ask for caching
> since it knows that the decoder lines aren't complete.

And, even with your list of reasons, it is still very unlikely that anybody
will ever need the cached copy :-)  I still do not see a device which
would have shared decoders AND needed such initialization in userspace.

(Also, while we are speaking about video hardware -- they either have no
kernel driver, so nobody can ask for the copy, or they have one, but in
that case the BIOS mode switching calls and similar things can be accomplished
by the kernel driver with no need of messing with the ROM in the userspace.)

				Have a nice fortnight
-- 
Martin `MJ' Mares   <mj@xxxxxx>   http://atrey.karlin.mff.cuni.cz/~mj/
Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth
How an engineer writes a program: Start by debugging an empty file...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/