> I don't see why the necessarity of a kernel stub driver is a killer > argument. The chip internals, which companies might want to protect are > certainly not in the interrupt registers.
So they can go off and write themselves a driver. Without putting junk in the kernel "just in case", and if the driver and the user space code using it are closely interdependant I'd suggest they look up the *legal* definition of derivative work. - 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/