From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eugeniu Rosca Date: Tue, 21 May 2019 11:43:57 +0200 Subject: [U-Boot] [PATCH v2 2/2] cmd: Add 'bcb' command to read/modify/write BCB fields In-Reply-To: References: <20190517144503.3275-1-erosca@de.adit-jv.com> <20190517144503.3275-3-erosca@de.adit-jv.com> <20190520072257.GA4084@vmlxhi-102.adit-jv.com> <20190521103659.0a0e084a@jawa> <20190521091352.GA5680@vmlxhi-102.adit-jv.com> Message-ID: <20190521094357.GA6854@vmlxhi-102.adit-jv.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Tue, May 21, 2019 at 10:24:10AM +0100, Alex Kiernan wrote: > On Tue, May 21, 2019 at 10:14 AM Eugeniu Rosca wrote: [..] > > That's a truly constructive suggestion. Nevertheless, I believe this > > would not work in case of CONFIG_ENV_IS_NOWHERE=y, which is how U-Boot > > is built and used by the developers in our organization. > > > > That's how we build/run too, but with with hackery like this in a boot > script to pick pieces out of the legacy world: > > mmc dev ${mmcdev} > mmc read ${loadaddr} 1300 100 > env import -c ${loadaddr} 20000 ethaddr FWIW, we have a cascaded load of boot scripts combined with `env import -t` and/or `source`, which allows to control the boot media by changing one line in a text file. This might be super ugly in terms of vanilla standards, but it works in the development environment and that's what matters the most. -- Best regards, Eugeniu.