From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] boot/uboot: add config option for uboot environment padding byte
Date: Tue, 12 Dec 2017 11:40:02 +0100 [thread overview]
Message-ID: <20171212114002.6f48877f@windsurf> (raw)
In-Reply-To: <CAMbDF3+bn0hyNGLz42r-kXXS+6BL2Wig-ZHxhG7fOFyEhTQS7g@mail.gmail.com>
Hello,
On Tue, 12 Dec 2017 10:04:38 +0100, Johannes Schmitz wrote:
> I find it definitely useful for debugging. I wouldn't have been able to
> isolate the issue with the size and CRC without this option because if you
> want to compare with hexdump you want everything to exactly match to see
> what's wrong. Without this, the next person might go down the same way like
> myself. The default of uboot when saving the environment is 0x00 and the
> default of mkenvimage is 0xFF. My idea is to make it the same to (0x00) to
> make the developers life easier. My experience is that any of these details
> takes some amount of your time to sort out so a less confusing default can
> safe time for everyone. On the other hand people might want to deliberately
> set it to 0xFF to exactly check the boarders of the env partition on the SD
> card, especially during development of genimage.cfg. Furthermore it makes
> you understand quicker what happens during env image generation. If you
> hide the option from the user/platform developer again makes life harder. I
> am speaking from the point of view of a buildroot newcomer. Now of course I
> now what's going on but would that option have been there it would have
> saved me one afternoon.
Hm, ok. I'm still not super convinced, but the code/complexity isn't
big enough to really argue more than that :)
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-12 10:40 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 [this message]
2017-12-13 18:23 ` Yann E. MORIN
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
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
[not found] <1512924220-32621-1-git-send-email-johannes.schmitz1@gmail.com>
2017-12-10 16:59 ` Yann E. MORIN
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=20171212114002.6f48877f@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--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.