Re: Exposing ROM's though sysfs

[Jesse Barnes]

On Friday, July 30, 2004 1:41 pm, Martin Mares wrote:
> Hello!
>
> > Reasons for ROMs in sysfs:
>
> Good ones, although I believe than re-initializing cards after resume
> should better be in the kernel.

I don't think anyone wants an x86 emulator builtin to the kernel for this 
purpose.

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

We can get away without caching a copy of the ROM in the kernel if we require 
userspace to cache it before the driver takes control of the card (i.e. at 
POST time).  Otherwise, the kernel will have to take care of it.

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