On Mon, Sep 22, 2014 at 06:35:30AM +0530, Chauhan, Himanshu wrote:
On Monday, September 22, 2014, Peter Stuge peter@stuge.se wrote:
Paul Menzel wrote:
`libpayload: Add Virtio layer and storage device support`
..
Some of the files are taken from SeaBIOS and are licensed under the GNU LGPLv3. Is that allowed/wanted to be in libpayload?
I for one think it would be good to keep libpayload BSD-licensed.
Chauhan, Himanshu wrote:
In that case would it make sense to put it in FILO which is GPL?
Yes, I think that's a very good idea.
But to my understanding, it would convert FILO from GPLv2 to GPLv3. Isn't it?
The virtio code in SeaBIOS was relicensed to LGPLv3 so that it could be distributed with SeaBIOS. I would reach out to the authors of that virtio code to see if they are okay with a different license.
-Kevin
Le 23/09/2014 17:29, Kevin O'Connor a écrit :
On Mon, Sep 22, 2014 at 06:35:30AM +0530, Chauhan, Himanshu wrote:
On Monday, September 22, 2014, Peter Stuge peter@stuge.se wrote:
Paul Menzel wrote:
`libpayload: Add Virtio layer and storage device support`
..
Some of the files are taken from SeaBIOS and are licensed under the GNU LGPLv3. Is that allowed/wanted to be in libpayload?
I for one think it would be good to keep libpayload BSD-licensed.
Chauhan, Himanshu wrote:
In that case would it make sense to put it in FILO which is GPL?
Yes, I think that's a very good idea.
But to my understanding, it would convert FILO from GPLv2 to GPLv3. Isn't it?
The virtio code in SeaBIOS was relicensed to LGPLv3 so that it could be distributed with SeaBIOS. I would reach out to the authors of that virtio code to see if they are okay with a different license.
Kevin,
for my part, I don't care of the license : you can relicense my work as you want.
Regards, Laurent