> 
> == Minutes ==
> 
>  * Quick mention of what Linaro is for Robert
>  * Grant working on defining a boot architecture
>    * Telling manufacturers what firmware should be doing, where it stops
>    * Not trying to cover the whole world, but more the fairly common case
>    * Predictable set of interfaces
>  * Barebox updates
>    * Sascha Hauer main maintainer
>    * Biggest problem was u-boot's architecture; old, full of ifdefs, not well 
> designed structure
>    * Pengutronix making a lot of bootloaders for industrial systems
>    * Trying to be a mini-kernel, with the same coding style, modules etc. BUT 
> trying to keep it to a minimum
>   * Why not evolve u-boot instead of forking?
>     * Wolfgang pushed back when introducing Kconfig, modules etc.
yeah I was pushed everytime I try to do it
>     * Not much feedback on the new ideas
>     * Upstream policy would prevent breakage of old boards; but priority was 
> fixing the architecture rather than keeping support for hundreds of boards 
> which they didn't have access to
yeah I remember when I try to put the initcall
>     * Was a bad idea to use the new u-boot
>   * Is Barebox trying to replace u-boot, or will the two exist together?
>     * Pengutronix using it because they see it as useful
>     * Presented at conferences, trying to gain more community around the 
> project
And really more friendly
as example with Menu Framework
>   * Why not strip down the kernel down to be a bootloader?
>     * Some SH4 people do this
SH4 on barebox now :)
>     * Problem is that it takes longer to boot the kernel
agree
>     * Will likely remain too slow and too large to be a production 
> bootloader, since drivers rely on too much functionality
>     * If the kernel is the bootloader, no need for two sets of drivers
>   * Need to communicate on upgrade risks in the field, more than how the 
> bootloader is laid out
>   * Trying to write common device drivers
>     * Is there effort to be 100% compatible at the source level with the 
> kernel drivers?
>       * Problem is getting rid off the possibility of running user programs?
I'm currently re-writing the application support for barebox
>  * Current kexecbooting needs some way of loading the initial kernel from 
> NAND or whatever
>  * U-Boot and Barebox don't ship in production; why?
>    * Pengutronix has industry and automotive customers, and they do ship 
> Barebox
I put it also
>  * Good idea to allow upgrading the device tree and the kernel, but not 
> exposing the bootloader
>  * Would be nice to unify into a common tree the first and second stage 
> bootloader
yes I did it
>  * Is it possible to build a single barebox which supports multiple boards?  
> Is it relocatable?
>    * Might be some limitations, Sascha would know
yes I did and multiple soc

Best Regards,
J.

_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Reply via email to