[meta-freescale] IMAGE_BOOTLOADER vs. PREFERRED_PROVIDER_virtual/bootloader
otavio at ossystems.com.br
Tue Apr 22 13:09:46 PDT 2014
On Tue, Apr 22, 2014 at 4:59 PM, Mario Domenech Goulart <
mario at ossystems.com.br> wrote:
> On Sun, 20 Apr 2014 16:44:15 -0300 Otavio Salvador <
> otavio at ossystems.com.br> wrote:
> > On Tue, Apr 15, 2014 at 3:23 PM, Mario Domenech Goulart
> > <mario at ossystems.com.br> wrote:
> >> I'm making a script to extract data out of bitbake's cache metadata and
> >> stumbled upon IMAGE_BOOTLOADER.
> >> Is there any special reason to use IMAGE_BOOTLOADER instead of
> >> PREFERRED_PROVIDER_virtual/bootloader?
> > Very good point. I think when I did the class, for SD card
> > generation, we hadn't this around (or I missed it).
> > Looking at it, this should indeed be dropped but it is going to need
> > some work as we need to provide a u-boot-dummy for the cases when we
> > don't need a bootloader in the SD card image, as it is the case for
> > Nitrogen boards for example.
> > We can discuss how to address it for 1.7 later.
> There are also boards which set PREFERRED_PROVIDER_u-boot. As far as I
> understand, PREFERRED_PROVIDER_virtual/bootloader would do the trick for
> those cases too.
Yes; but for example in Nitrogen case we need to have a 'u-boot-dummy'
which does nothing and the class know this is a 'nop' bootloader. That's
why I said it must to be worked in 1.7.
Otavio Salvador O.S. Systems
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the meta-freescale