Re: Linux Hardware Quality Labs (was: Linux in a binary world... a doomsday scenario)

[Felix Oxley <lkml@oxley.org>]

> 1)Lets say there is a small licence fee.
> 50% to the developer that writes/intergrates the code into the kernel,
> 50% to the Org that provides the database/legal backup...
>
> or to get things going
> 2)no fees, just providing a certain level of docs
> such that a driver with full hardware support can be created.
> This enables the company to add the "Linux" sticker to their boxes.

If the OEM wants to stick the logo on the box when the hardware ships  
then _they_ will have to write the driver (they can of course  
subcontract to a maintainer if they like).

If they choose to rely on the system where the driver is written by  
somebody who wants to use the hardware themselves then the OEM still  
has to provide the necessary documentation.
And of course they would not be able to use the logo until such time  
as the driver was available.

Documentation must be available for on going maintenance as well as  
initial coding. This would be a requirement for the logo.
Therefore by far the best solution is that the documentation is put  
into the public domain.

If the OEM has a problem with releasing the documentation then they  
would have to enter into some sort of ongoing agreement with the  
certification body to give confidence that the driver was  
maintainable (i.e. ongoing NDA agreement). Without this the hardware  
could not be certified.

I don't know how many drivers are currently provided by the OEM  
rather than written by A. Random Developer, but this process should  
encourage the OEM to provide the driver themselves.
This should reduce the kernel exposure to patent attacks (??). (IANAL)

regards,
Felix
-
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/