On 10/31/06, Uwe Hermann <[EMAIL PROTECTED]> wrote:
Those public docs, once so helpful, are now mostly useless. The important content is not there.
This is why I tell people, 'Don't get tricky'. Tell Intel from the beginning what you are doing, and that you intend to release code, and do it in writing. make sure there is no confusion. Get permission.
Then there are no surprises or bad feelings at either end.
thanks
ron
Is it common that you need more documentation than that for Intel
chipsets? Are they usually missing important bits?
Those public docs, once so helpful, are now mostly useless. The important content is not there.
As for the example code - I'm not sure whether it's a good idea to get
code from them (even worse, under NDA), as that would probably "taint"
any contributed (GPL'd) code we might later include into LinuxBIOS.
The Intel lawyers could always argue that we illegally distributed/modified
their code or whatever...
This is why I tell people, 'Don't get tricky'. Tell Intel from the beginning what you are doing, and that you intend to release code, and do it in writing. make sure there is no confusion. Get permission.
Then there are no surprises or bad feelings at either end.
thanks
ron
-- linuxbios mailing list [email protected] http://www.openbios.org/mailman/listinfo/linuxbios
