Am Samstag, 18. Dezember 2010, um 02:07:50 schrieb Peter Stuge: > But if the released code that is included in coreboot is changed > within coreboot, because the community sees some opportunities to > improve coreboot overall by doing so, then those changes are also > licensed exclusively as GPLv2. This means that those changes can not > be included "back" into the original dual licensed codebase, or into > any derivative which chose to use either the dual license or the BSD > license. It's up to the developer of the change to decide the license of their changes. That is, a change could be added with the explicit statement (eg. in the commit message) that it's licensed both under GPLv2 and BSD-l, and it could be taken for BSD-l only uses (while originating with coreboot). The only thing to keep in mind is that the combined work of coreboot+AGESA will be GPL only - this only affects distributors of coreboot+AGESA binaries who will have to treat their changes to AGESA (as delivered with coreboot) as licensed under GPLv2 only (unless a clean calling interface is defined as described in your mail that would separate coreboot and AGESA sufficiently).
Patrick -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
