From: Sebastian Muxel <sebastian.muxel@entner-electronics.com>
To: Christian Melki <christian.melki@t2data.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] u-boot: Allow specification of padding byte for custom env images
Date: Fri, 9 Feb 2024 18:23:09 +0100 [thread overview]
Message-ID: <bg4za7epq7darsw64mfkztsv23am23nf2ui4x44yahfbnoiysf@jywfgjag5m4d> (raw)
In-Reply-To: <0e17d7b2-1397-4d8b-93fc-55d50cd64f1f@t2data.com>
>0x0 looks wrong to me w.r.t most flash media. Also not sure I understand
>why 0xff would stop anything from generating a firmware image?
The tooling screams at me when i don't set it up this way. I'm 100%
certain it's a unfortunate requirement i had to comply with.
You could argue that the change is benefitial as it makes the interface
for mkenvimage more complete, even if the usecase is a rather unusual
one but i understand if it's too special of a case.
Regards,
Sebastian
next prev parent reply other threads:[~2024-02-09 17:23 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
2024-02-05 21:07 ` Christian Melki
2024-02-09 17:23 ` Sebastian Muxel [this message]
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=bg4za7epq7darsw64mfkztsv23am23nf2ui4x44yahfbnoiysf@jywfgjag5m4d \
--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