From: Wolfgang Denk Date: Tue, 21 Jan 2020 18:49:06 +0100 Subject: [RFC PATCH] Provide mechanism for build-time default env entries In-Reply-To: References: <20200119073738.29189-1-mrjoel@lixil.net> <20200120165119.4A25224004C@gemini.denx.de> <7cac871967a1317cea251e78d67a30ac@lixil.net> <20200120185921.197E224009F@gemini.denx.de> Message-ID: <20200121174906.49773240638@gemini.denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Joel, In message you wrote: > > > I think you are following a wrong approach. Such user specific > > settings should IMHO loaded separately, either over serial like > > (should be fast enough for a few hundred bytes) or from external > > storage. "env import" is your friend. > > I'm intentionally trying to have no persistent environment separate from > boot image. In which way does this prevent you from following my suggestion? such a separate environment block (in any format, either as plain ASCII text, or binary, or as checksummed blob) can easily be attached to the U-Boot image and handled as a combined unit. Then you just import the additional environment from this well-known address. This gives you all the possibilities you have for handling the environment, conflict free. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de When a woman marries again it is because she detested her first hus- band. When a man marries again, it is because he adored his first wife. -- Oscar Wilde