mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Sebastian Muxel <sebastian.muxel@entner-electronics.com>
To: ptxdist@pengutronix.de, christian.melki@t2data.com
Subject: Re: [ptxdist] [PATCH] u-boot: Allow specification of padding byte for custom env images
Date: Mon, 5 Feb 2024 21:49:16 +0100	[thread overview]
Message-ID: <3zf2idbmoykcvgqcjdd25hq3q43uui2teou6naqpwxqgxhogn2@lbpoiotzoupu> (raw)
In-Reply-To: <fdfb4e6c-a265-4734-bca8-ffc2b42906aa@t2data.com>

Hello

>Just curious. In what situation would you need to alter the default
>padding bytes? 0xff suits most (if not all) NVM types. Flash transition
>layers usually just give an illusion of the traditional zero:ed block on
>flash to block translation?

I had to tweak it to 0x00 after noticing that the env image generated by
our vendor supplied SDK has specified it in it's make process. Keeping
it at 0xFF wouldn't allow me to generate a firmware image. It could likely
be that it's a hard requirement of their image generation/flashing tool?
I honestly haven't put much further thought into it and assumed it's due
to the way NAND erasure works

Regards,
Sebastian



  reply	other threads:[~2024-02-05 20:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 20:16 Sebastian Muxel
2024-02-05 20:30 ` Christian Melki
2024-02-05 20:49   ` Sebastian Muxel [this message]
2024-02-05 21:07     ` Christian Melki
2024-02-09 17:23       ` Sebastian Muxel
2024-02-15 10:03     ` Alexander Dahl
2024-02-15 10:35       ` [ptxdist] *****POSSIBLE SPAM***** " Sebastian Muxel

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=3zf2idbmoykcvgqcjdd25hq3q43uui2teou6naqpwxqgxhogn2@lbpoiotzoupu \
    --to=sebastian.muxel@entner-electronics.com \
    --cc=christian.melki@t2data.com \
    --cc=ptxdist@pengutronix.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