From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] boot/uboot: add config option for uboot environment padding byte
Date: Wed, 13 Dec 2017 19:23:32 +0100 [thread overview]
Message-ID: <20171213182332.GB7364@scaer> (raw)
In-Reply-To: <20171212062751.3e1eb993@windsurf.png.is.keysight.com>
Thomas, Johannes, All,
On 2017-12-12 06:27 +0100, Thomas Petazzoni spake thusly:
> On Mon, 11 Dec 2017 19:47:08 +0100, Johannes Schmitz wrote:
[--SNIP--]
> > +config BR2_TARGET_UBOOT_ENVIMAGE_PADDING_BYTE
> > + hex "Padding byte"
> > + default 0x00
> > + help
> > + The byte used for padding at the end of the environment image.
>
> I'm still not sure what is the point of customizing the padding byte.
> Does someone has a use-case for that ? If not, I'm not sure it makes
> sense to add a Buildroot option for it.
As far as I understand, this is because the U-Boot on Johannes' board
would expect the padding byte to be 0x00 when the default for mkenvimage
is 0xFF.
I have no idea why U-Boot expects 0x00 in Johannes' case, though. The
only thing I can think of is that the 'default' byte value on flash
after a page-erase depends on the technology: for NOR, the value after
erase ix 0x00, while for NAND, it is 0xFF. So maybe that's the reason...
But any case, as you said in a further reply, adding that new option
does not add much complexity.
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-12-13 18:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 18:47 [Buildroot] [PATCH 1/1] boot/uboot: add config option for uboot environment padding byte Johannes Schmitz
2017-12-12 5:27 ` Thomas Petazzoni
2017-12-12 9:04 ` Johannes Schmitz
2017-12-12 10:40 ` Thomas Petazzoni
2017-12-13 18:23 ` Yann E. MORIN [this message]
2017-12-13 19:57 ` Johannes Schmitz
2017-12-14 6:13 ` Thomas Petazzoni
[not found] ` <CAMbDF3J=j94Ze6LVJWnA7N453JMOP60-SzjLBdrB6n5s_aSkPw@mail.gmail.com>
2017-12-14 7:06 ` Johannes Schmitz
2017-12-14 7:21 ` Thomas Petazzoni
2018-02-03 21:01 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2017-12-10 17:10 Johannes Schmitz
2017-12-10 17:09 Johannes Schmitz
[not found] <1512924220-32621-1-git-send-email-johannes.schmitz1@gmail.com>
2017-12-10 16:59 ` Yann E. MORIN
2017-12-10 16:59 Johannes Schmitz
2017-12-11 6:18 ` Thomas Petazzoni
2017-12-11 6:48 ` Johannes Schmitz
2017-12-11 7:15 ` Thomas Petazzoni
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=20171213182332.GB7364@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.