All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 2/2] env: add CONFIG_ENV_SECT_SIZE_AUTO
Date: Thu, 24 Sep 2020 12:54:36 +0200	[thread overview]
Message-ID: <4015025.1600944876@gemini.denx.de> (raw)
In-Reply-To: <125344f4-2b69-1c7a-0f5a-6d27ab312487@prevas.dk>

Dear Rasmus,

In message <125344f4-2b69-1c7a-0f5a-6d27ab312487@prevas.dk> you wrote:
> > 
> > On our newer boards with the 4K erase size, saving the environment now
> > takes 0.080 seconds instead of 0.53 seconds, which directly translates
> > to that much faster boot time since our logic always causes the
> > environment to be written during boot.

Is this your way of implementing scheduled obsolescence? 

Automatically writing the environment on every boot is always a
really bad idea. Never ever do that.

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 the bosses talk about improving  productivity,  they  are  never
talking about themselves.

  reply	other threads:[~2020-09-24 10:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06  8:46 [PATCH 0/2] add CONFIG_ENV_SECT_SIZE_AUTO Rasmus Villemoes
2020-05-06  8:47 ` [PATCH 1/2] env/sf.c: use a variable to hold the sector size Rasmus Villemoes
2020-09-18  8:16   ` Rasmus Villemoes
2020-09-18 14:49     ` Tom Rini
2020-05-06  8:47 ` [PATCH 2/2] env: add CONFIG_ENV_SECT_SIZE_AUTO Rasmus Villemoes
2020-05-06  8:59   ` Joakim Tjernlund
2020-05-06  9:11     ` Rasmus Villemoes
2020-05-06  9:21       ` Joakim Tjernlund
2020-05-06  9:37         ` Rasmus Villemoes
2020-05-06 10:00           ` Joakim Tjernlund
2020-05-06 10:15             ` Rasmus Villemoes
2020-05-06 10:22               ` Joakim Tjernlund
2020-05-06 10:18             ` Joakim Tjernlund
2020-05-06 10:47               ` Rasmus Villemoes
2020-05-06 11:06                 ` Joakim Tjernlund
2020-05-06 11:08                   ` Joakim Tjernlund
2020-09-18  8:17   ` Rasmus Villemoes
2020-09-24 10:54     ` Wolfgang Denk [this message]
     [not found]       ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.f435d534-2cba-4875-b180-3df85765465d@emailsignatures365.codetwo.com>
2020-09-24 11:08       ` Rasmus Villemoes
2020-09-24 11:35         ` Mike Looijmans
2020-09-24 11:58           ` Rasmus Villemoes

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=4015025.1600944876@gemini.denx.de \
    --to=wd@denx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.