[PATCH 01/18] bootm: netbds: Drop passing of arguments

[Tom Rini]

On Tue, Dec 05, 2023 at 08:53:58PM -0700, Simon Glass wrote:
> Hi,
> 
> I am replying to this email since it still has the context below.
> 
> On Mon, 4 Dec 2023 at 03:48, Mark Kettenis <mark.kettenis at xs4all.nl> wrote:
> >
> > > From: Simon Glass <sjg at chromium.org>
> > > Date: Sun,  3 Dec 2023 17:26:17 -0700
> >
> > Hi Simon,
> >
> > There is a typo in first line of the commit message: s/netbds/netbsd/.
> >
> > > It isn't clear how useful it is to pass the arguments of bootm to the
> > > OS. For example, if "bootm 1000 2000 3000" is used, the three arguments
> > > at the end are passed to the OS. This seems like a strange approach,
> > > since the argument have already been parsed by U-Boot and processed.
> > >
> > > Rely instead on the "bootargs" mechanism, which is the standard
> > > approach.
> >
> > It is a very Linuxy approach though.
> >
> > I suspect this feature was added to pass kernel arguments for
> > "one-off" boots.  For example
> >
> >     bootm -s
> 
> Martin says that this is used with NetBSD. So do we rely on U-Boot
> parsing the '-s' as 0 and then using loadaddr as the default?
> 
> I wonder if we could come up with another mechanism? Perhaps 'bootm --
> args go here' ? Or define that if the first arg starts with '-' then
> the args are not parsed?
> 
> Martin, would it be possible to send a patch to doc/ describing how to
> boot NetBSD?

A patch describing how booting is done today, especially including some
of the potentially less common but still valid usages would be much
appreciated. We can go from there to decide what changes if any to make
to what's exposed to the user in this case as I am loathe to change
things like this which amount of an ABI.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20231209/50f9cb99/attachment.sig>