On Friday, September 11th, 2026 at 8:53 PM, Tom Rini <[email protected]> wrote:

> On Fri, Sep 11, 2026 at 08:46:30PM +0200, Marek Vasut wrote:
> > On 9/11/26 8:39 PM, phodina wrote:
> > > On Friday, September 11th, 2026 at 8:30 PM, Marek Vasut 
> > > <[email protected]> wrote:
> > > 
> > > > On 9/11/26 8:18 PM, Petr Hodina via B4 Relay wrote:
> > > > > From: Petr Hodina <[email protected]>
> > > > > 
> > > > > Add a new utility library for parsing command line parameters in
> > > > > key=value format.
> > > > Is this reinventing environment or UPL ?
> > > > 
> > > 
> > > The target is a chainloaded environment. In this case u-boot running on 
> > > Android devices where you unfortunately don't have the possibility to use 
> > > UPL.
> > > 
> > > As stated above it's purpose is to simplify the operations on the command 
> > > line arguments from the previous stage and pass them to the next.
> > > 
> > > Typical example is to remove the skip initramfs or extract the value for 
> > > the panel to pick the right dtb (not part of this patch series)
> > 
> > Is this something you could do in an U-Boot script using setexpr sub/gsub
> > instead ?
> 

Well that should be possible as the C strings are messy.

However, the intention is to be used from SPL where
the setexpr sub/gsub would not be available.

> Yes, I would like to see how this gets used in implementation too, as
> I'm wondering if we shouldn't just be also saving off something like
> "prev_bl_bootargs" and leaving the rest to the board code to deal with.
> Maybe we should also add the android-specific helpers in a new file
> under an Android-related Kconfig as well.
> 
> -- 
> Tom

Will send the example in another patch series with detailed description.

TLDR; The boot.img contains as the main target the SPL u-boot build with 
barebone dts. Qcom has a thing called SMEM which can be used in runtime to 
detect the board and based on that we pick the correct dtb and jump to normal 
u-boot.

Also thanks for the good idea to place the helper under Android Kconfig.

Reply via email to