> Ummmmm.... That's really easy. 1st case: change the kernel license to
> disallow commercial drivers. 2nd case: change the module code to only
> load drivers containing the right string in the right place. That
> string would of course be a protected certification mark. These are
> sort of ugly and rude. Can anyone think of something nicer?
This is not really needed. Inclusion of OSD-compiance in USD-certification
will be enough :-) Since "Big Boss" (who will sign checks :-) is aware that
certified driver is "Good Thing" while non-certified driver is "Bad Thing"
(even if he is not aware what's driver is in first place :-)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/