On 08/25/2010 03:50 PM, Samuel Thibault wrote:
quoted text
> H. Peter Anvin, le Wed 25 Aug 2010 14:19:55 -0700, a écrit :
>> At that point I'd almost prefer doing something like a BIOS signature
>> check if we can't do anything better.
> 
> Well, there will be several versions of the BIOS signature, which the
> constructor is not likely to provide.
> 

Then we'll gather them up, or something.

quoted text
> Just to make sure there's no misunderstanding: it was never planned that
> this driver be loaded unless some manual intervention, like explicitly
> loadling the module or setting some parameter, so that if bad effects
> happen on the machine, the user can only get angry at himself for having
> loaded by hand a random module without reading the documentation that
> explicitly says (twice) it's only for a particular kind of hardware.
> 
> I however now realize that I don't find a way to force a driver to be
> compiled only as a module.  If there isn't, I guess we can just add
> a module parameter to enable/disable the driver, so that it won't be
> active by default even compiled-in?

There is, but that is hardly a reasonable solution.

What other forms of enumerable hardware is on this machine?  PCI?

	-hpa
--
unsubscribe notice
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/