Dear Chris,
In message
you wrote:
>
> What I think might be the best path forward is being able to supply
> defaults via a file at run time. That way we can have a generic fw_setenv
> but supply board specific defaults via a config file.
This would indeed make sense (though I would not call
Hi Wolfgang,
On Tue, 18 Aug 2020, 10:27 PM Wolfgang Denk, wrote:
> Dear Chris Packham,
>
> In message <20200813013727.8186-1-judge.pack...@gmail.com> you wrote:
> > When building envtools via tools-only_defconfig the builtin defaults
> > are based on options in the defconfig. For example:
> >
>
On Tue, 18 Aug 2020, 11:02 PM Stefano Babic, wrote:
> Hi Chris,
>
> On 13.08.20 03:37, Chris Packham wrote:
> > When building envtools via tools-only_defconfig the builtin defaults
> > are based on options in the defconfig. For example:
> >
> > bootcmd=bootp; setenv bootargs root=/dev/nfs
>
Hi Chris,
On 13.08.20 03:37, Chris Packham wrote:
> When building envtools via tools-only_defconfig the builtin defaults
> are based on options in the defconfig. For example:
>
> bootcmd=bootp; setenv bootargs root=/dev/nfs
> nfsroot=${serverip}:${rootpath}
>
Dear Chris Packham,
In message <20200813013727.8186-1-judge.pack...@gmail.com> you wrote:
> When building envtools via tools-only_defconfig the builtin defaults
> are based on options in the defconfig. For example:
>
> bootcmd=bootp; setenv bootargs root=/dev/nfs
>
On Wed, Aug 12, 2020 at 8:37 PM Chris Packham wrote:
>
> When building envtools via tools-only_defconfig the builtin defaults
> are based on options in the defconfig. For example:
>
> bootcmd=bootp; setenv bootargs root=/dev/nfs
> nfsroot=${serverip}:${rootpath}
>
When building envtools via tools-only_defconfig the builtin defaults
are based on options in the defconfig. For example:
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath}
ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=2
7 matches
Mail list logo
