[PATCH u-boot 0/1] RFC: How to configure boot options?

Rick Altherr raltherr at google.com
Tue Jul 25 04:19:52 AEST 2017

The current bootcmd script is there to provide backward compatibility for
pre-FIT ramdisks.  That can probably be removed but we now want fallback
behavior for images that still use a ramdisk.

On Fri, Jul 21, 2017 at 3:33 PM, Patrick Williams <patrick at stwcx.xyz> wrote:

> As part of the change-over from an initramfs-based boot sequence to a
> direct rootfs boot, we need to change some of the boot options for
> u-boot.  I expect these to change a few times in the near future as we
> also transition to UBI-managed volumes and we figure out how to set
> u-boot environment options to switch between different UBI kernels and
> rootfses.
> This is really independent from the current ast-*-defconfigs, in that
> those currently select between different network options.  I suspect
> we do not N*M combinations of defconfigs for network*image-structure.
> I plan to make a MACHINE_FEATURE (or DISTRO_FEATURE) in bitbake to
> control this, but looking for feedback on how we should change u-boot.
> Ideally, to me, this would have been passed in via the config file and
> we could have used config-snippets in Yocto like we do for the kernel.
> Due to the way u-boot builds, I could not find a simple way to even
> change this option from a include/config/ast-common.h #define into a
> machine_config driven option.
> Anyone have ideas?
> Patrick Williams (1):
>   config/ast-common: hack bootopts
>  include/configs/ast-common.h | 6 ++++++
>  1 file changed, 6 insertions(+)
> --
> 2.13.0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20170724/cad741e8/attachment-0001.html>

More information about the openbmc mailing list