public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: sbabic@denx.de
To: Francesco Dolcini <francesco.dolcini@toradex.com>,u-boot@lists.denx.de
Subject: [PATCH v1 2/2] colibri-imx7: improve env badblock management
Date: Sat,  5 Feb 2022 17:43:30 +0100 (CET)	[thread overview]
Message-ID: <20220205164333.76C8583CBE@phobos.denx.de> (raw)
In-Reply-To: <20210901074803.49785-3-francesco.dolcini@toradex.com>

> Use the complete 512kb (4 blocks) nand partition reserved for u-boot
> environment instead of just the first block, this allows the module
> to have a working environment even if 3 blocks are bad.
> Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
Applied to u-boot-imx, master, thanks !

Best regards,
Stefano Babic

-- 
=====================================================================
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================

  reply	other threads:[~2022-02-05 16:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01  7:48 [PATCH v1 0/2] board: toradex: improve env badblock management for NAND variant boards Francesco Dolcini
2021-09-01  7:48 ` [PATCH v1 1/2] colibri-imx6ull: improve env badblock management Francesco Dolcini
2021-09-01  7:48 ` [PATCH v1 2/2] colibri-imx7: " Francesco Dolcini
2022-02-05 16:43   ` sbabic [this message]
2021-10-21 10:16 ` [PATCH v1 0/2] board: toradex: improve env badblock management for NAND variant boards Stefano Babic
2021-10-21 11:08   ` Francesco Dolcini
2021-10-22  7:59     ` Francesco Dolcini
2021-10-22  8:04       ` Stefano Babic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220205164333.76C8583CBE@phobos.denx.de \
    --to=sbabic@denx.de \
    --cc=francesco.dolcini@toradex.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox