Date: Mon, 18 Dec 2017 08:34:09 -0800 From: Russell Haley <russ.haley@gmail.com> To: Emmanuel Vadot <manu@bidouilliste.com>, Ian Lepore <ian@freebsd.org> Cc: freebsd-arm@freebsd.org Subject: Re: ubldr question Message-ID: <20171218163409.6914130.29031.36691@gmail.com> In-Reply-To: <20171218104824.a4e656687a9121aa256b094c@bidouilliste.com> References: <0844C635-7FA6-4684-92F5-4C1AAC8EFB95@cs.huji.ac.il> <1513530125.95072.27.camel@freebsd.org> <20171218104824.a4e656687a9121aa256b094c@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry for the top post. So it's just a matter of updating the define/variable noted below=E2=80=8E = to restore that functionality on previously supported platforms? Russ Sent=C2=A0from=C2=A0my=C2=A0BlackBerry=C2=A010=C2=A0smartphone=C2=A0on=C2= =A0the=C2=A0Virgin=C2=A0Mobile=C2=A0network. =C2=A0 Original Message =C2=A0 From: Emmanuel Vadot Sent: Monday, December 18, 2017 1:48 AM To: Ian Lepore Cc: freebsd-arm@freebsd.org Subject: Re: ubldr question On Sun, 17 Dec 2017 10:02:05 -0700 Ian Lepore <ian@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. > >=20 > > So, apart from stoping the loader, and typing ?env set fdtfile > > xxx.dtb? > > is there another way? > >=20 > > cheers, > > danny > >=20 >=20 > You should be able to "saveenv" after making your change. >=20 > The uEnv.txt that used to be supported was to make it possible to > programatically change the boot behavior from freebsd userland. =C2=A0That > 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. =C2=A0It's a lot less work for the > port maintainers, but we lost some functionality along the way. >=20 > -- 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). --=20 Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org> _______________________________________________ freebsd-arm@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171218163409.6914130.29031.36691>