On Sun, Dec 10, 2017 at 10:53:43PM -0200, Otavio Salvador wrote:
> On Sat, Dec 9, 2017 at 12:45 AM, Kevin Hao <[email protected]> wrote:
> > Some firmwares are critical for the basic functions of the board, and may
> > be used by the bootloader. Due to the license issue, we can't integrate
> > it. But we do need it when creating a booting image by using WIC.
> > So add the support for the WIC to download a raw file from http
> > server and write it to a specific part. In order to restrict the
> > downloading behaviour, we introduce a "WKS_ALLOW_DOWNLOAD" variable and
> > only do the downloading when this variable is set.
> >
> > Signed-off-by: Kevin Hao <[email protected]>
> 
> This does not make much sense.
> 
> It does not allow to be downloaded? so build system can download it
> and use it as a normal artifact. 

In some cases, it doesn't make sense to do so. Because:
a) These firmwares are just raw binary files, they don't need any build or
   process. They are only useful when we try to create a bootable image.
b) There firmwares may be licensed under a proprietary license. We may not
   integrate them to a fully open source build system. But we do want to provide
   an easy way for the customer to build a bootable image.

Thanks,
Kevin

>Adding another source way seems
> controversial.
> 
> -- 
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Attachment: signature.asc
Description: PGP signature

-- 
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to