From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Tue, 3 Sep 2019 10:36:08 -0400 Subject: [U-Boot] [PATCH] mx53loco: Fix U-Boot corruption after saving the environment In-Reply-To: References: <20190830165829.23016-1-festevam@gmail.com> <20190830181441.GN26850@bill-the-cat> Message-ID: <20190903143608.GF26850@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Mon, Sep 02, 2019 at 01:40:27PM -0300, Fabio Estevam wrote: > Hi Tom, > > On Fri, Aug 30, 2019 at 3:14 PM Tom Rini wrote: > > > Are there more i.mx platforms that are not setting BOARD_SIZE_LIMIT > > today? I assume there are, sadly. Can you audit and catch the rest of > > Yes, only a very few i.MX boards set BOARD_SIZE_LIMIT currently. > > > these likely problems, and add limits so we won't repeat this again. > > Yes, I can audit this, but this task requires more time and I can do > that after 2019.10 is released. > > Could this one that fixes mx53qsb be applied for 2019.10? As some is better than none, yes, we should fix and detect this for this platform. But I am a little frustrated in that this is not a new problem and the hook to check for this problem was put in back in June, so I had hoped for more preemptive conversions. It's also on me for having not reminded folks about that too. So please, can we make sure to get this covered ASAP? I think the kludge patch I've posted and linked to before (http://patchwork.ozlabs.org/patch/790476/) can be used here to get a current value calculated and spit out. Moving the question to Kconfig would then make it easier still to: 1. sync all configs 2. loop over appending value to defconfigs 3. re-sync all defconfigs 4. drop first patch, squash next approximately anyhow. Thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: