Am 2014-03-25 05:36, schrieb Stefan Reinauer:
Is there any single BSD licensed payload out there? That's using
libpayload? The work around of stuffing drivers into depthcharge is
really, really unfortunate because it causes unnecessary duplication
I think I (and you) ported some libpayload code
* mrnuke mr.nuke...@gmail.com [140320 23:57]:
Proposal:
* Share these drivers between coreboot and libpayload.
* libpayload is BSD. Have a [ ] Enable GPL features config option which
unlocks the GPL'd drivers from coreboot.
* libpayload core remains BSD.
* coreboot drivers are
* Patrick Georgi patr...@georgi-clan.de [140321 18:38]:
Am Donnerstag, den 20.03.2014, 17:57 -0500 schrieb mrnuke:
* Share these drivers between coreboot and libpayload.
Make them BSD-l, like cbfs-core.
* libpayload core remains BSD.
with strings attached - I'd like to avoid that.
Nice
Am Donnerstag, den 20.03.2014, 17:57 -0500 schrieb mrnuke:
* Share these drivers between coreboot and libpayload.
Make them BSD-l, like cbfs-core.
* libpayload core remains BSD.
with strings attached - I'd like to avoid that.
If you need SoC drivers, the *BSDs have their share of drivers,
I'll try to be short.
* Usually, ARM payloands need to use SoC specific drivers to access storage
devices.
* Sometimes coreboot implements the same drivers.
Proposal:
* Share these drivers between coreboot and libpayload.
* libpayload is BSD. Have a [ ] Enable GPL features config
mrnuke wrote:
* Share these drivers between coreboot and libpayload.
* libpayload is BSD. Have a [ ] Enable GPL features config option which
unlocks the GPL'd drivers from coreboot.
* libpayload core remains BSD.
The other way around would also be possible.
//Peter
--
coreboot
On Friday, March 21, 2014 01:13:59 AM Peter Stuge wrote:
mrnuke wrote:
* Share these drivers between coreboot and libpayload.
* libpayload is BSD. Have a [ ] Enable GPL features config option which
unlocks the GPL'd drivers from coreboot.
* libpayload core remains BSD.
The
7 matches
Mail list logo