ubldr question

[Ian Lepore]

On Mon, 2017-12-18 at 08:34 -0800, Russell Haley wrote:
> Sorry for the top post.
> 
> So it's just a matter of updating the define/variable noted below to
> restore that functionality on previously supported platforms?
> 
> Russ
> 

Yes, just do:

 setenv fdtfile yourfilename.dtb
 saveenv

-- Ian

> SentfrommyBlackBerry10smartphoneontheVirginMobilenetwork.
>  Original Message 
> From: Emmanuel Vadot
> Sent: Monday, December 18, 2017 1:48 AM
> To: Ian Lepore
> Cc: freebsd-arm at freebsd.org
> Subject: Re: ubldr question
> 
> On Sun, 17 Dec 2017 10:02:05 -0700
> Ian Lepore <ian at freebsd.org> wrote:
> 
> > 
> > On Sun, 2017-12-17 at 17:03 +0200, Daniel Braniss wrote:
> > > 
> > > Hi,
> > > in the past there was CONFIG.TXT and/or UENV.TXT where I could
> > > override the
> > > default .dtb file set by uboot, but now it seems these files are
> > > either not read, or the
> > > command has changed.
> > > 
> > > So, apart from stoping the loader, and typing ?env set fdtfile
> > > xxx.dtb?
> > > is there another way?
> > > 
> > > cheers,
> > > danny
> > > 
> > You should be able to "saveenv" after making your change.
> > 
> > The uEnv.txt that used to be supported was to make it possible to
> > programatically change the boot behavior from freebsd userland.
> > That
> > feature got lost when the uboot ports were all rewritten to use a
> > default environment (boot scripts and all) for freebsd that is
> > basically identical to what linux uses. It's a lot less work for
> > the
> > port maintainers, but we lost some functionality along the way.
> > 
> > -- Ian
> We currently use the default for the boards for the env, the default
> value for most of the board is to put the env in the mmc (in the
> space
> reserved for u-boot) and not in the fat. There is some discussion to
> move the env in the fat by default for allwinner boards as u-boot is
> getting too big now.
> One of the reason I didn't put back ENV_IS_IN_FAT is that our u-boot
> port is currently lacking of a proper way to customize the defconfigs
> (I'm currently working on this part) and I don't want to have too
> many
> patches (one for each board/soc).
> As of functionality, I'm not sure we lost something, one can still
> create a u-boot script (u-boot.scr) and do everything he needs for a
> custom boot. (Also setenv/saveenv works as Ian said).
>