Oct 13, 2021 23:39:17 Jim Hall 
<jhall[jh...@freedos.org]@freedos.org[jh...@freedos.org]
>>
> 
> It appears that somewhere along the line, someone (at AMD?) had access
> to the sources, probably in a larger source tree, and ran a batch job
> or script to apply the "AMD" statement to a bunch of source files. And
> that happened to catch these GPL and public domain source files. I
> believe that was done in error. The original public domain and GPL
> declarations trump the latter "AMD" statement.

The only issue I see here is if AMD added any code to the public domain files.

For the GPL files, the AMD violated the existing license by marking them as AMD 
proprietary, whether they added anything or not, and the only way for them to 
come back into compliance is to relicense the code under a GPL compatible 
license. So the GPL files are clean in any circumstance.

For the public domain stuff, they can't claim copyright to anything that 
existed in the files when they received them, but they can claim copyright to 
anything that they added.

If the original files can be traced and it can be demonstrated that AMD added 
nothing more than the copyright notices, then they're clean, otherwise it has 
to be determined what code was added by AMD, and that has to be stripped out.


_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to