From: "Pali Rohár" <pali@kernel.org>
To: Samuel Holland <samuel@sholland.org>
Cc: u-boot@lists.denx.de, "Jagan Teki" <jagan@amarulasolutions.com>,
"Andre Przywara" <andre.przywara@arm.com>,
"AKASHI Takahiro" <takahiro.akashi@linaro.org>,
"Alexandru Gagniuc" <mr.nuke.me@gmail.com>,
"Baruch Siach" <baruch@tkos.co.il>,
"Bharat Gooty" <bharat.gooty@broadcom.com>,
"Chris Packham" <judge.packham@gmail.com>,
"Fabio Estevam" <festevam@gmail.com>,
"Frieder Schrempf" <frieder.schrempf@kontron.de>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Marek Behún" <marek.behun@nic.cz>,
"NXP i.MX U-Boot Team" <uboot-imx@nxp.com>,
"Naoki Hayama" <naoki.hayama@lineo.co.jp>,
"Patrick Delaunay" <patrick.delaunay@foss.st.com>,
"Priyanka Jain" <priyanka.jain@nxp.com>,
"Rayagonda Kokatanur" <rayagonda.kokatanur@broadcom.com>,
"Simon Glass" <sjg@chromium.org>, "Stefan Roese" <sr@denx.de>,
"Stefano Babic" <sbabic@denx.de>,
"Sughosh Ganu" <sughosh.ganu@linaro.org>,
"Trevor Woerner" <twoerner@gmail.com>,
lauri.hintsala@silabs.com
Subject: Re: [PATCH v2 2/4] tools: mkimage: Add Allwinner TOC0 support
Date: Sun, 22 Aug 2021 19:51:55 +0200 [thread overview]
Message-ID: <20210822175155.gkfreikcgl37iyje@pali> (raw)
In-Reply-To: <c4b8273e-4ddd-4a09-1405-53704b3d86b7@sholland.org>
On Sunday 22 August 2021 12:44:05 Samuel Holland wrote:
> >> +struct toc0_main_info {
> >> + uint8_t name[8];
> >> + __le32 magic;
> >> + __le32 checksum;
> >> + __le32 serial;
> >> + __le32 status;
> >> + __le32 num_items;
> >> + __le32 length;
> >> + uint8_t platform[4];
> >> + uint8_t reserved[8];
> >> + uint8_t end[4];
> >> +};
> >> +
> >> +#define TOC0_MAIN_INFO_NAME "TOC0.GLH"
> >> +#define TOC0_MAIN_INFO_MAGIC 0x89119800
> >> +#define TOC0_MAIN_INFO_END "MIE;"
> >> +
> >> +struct toc0_item_info {
> >> + __le32 name;
> >> + __le32 offset;
> >> + __le32 length;
> >> + __le32 status;
> >> + __le32 type;
> >> + __le32 load_addr;
> >> + uint8_t reserved[4];
> >> + uint8_t end[4];
> >> +};
> >
> > These structures are raw image structures, right? Therefore they should
> > be marked as __packed?
>
> I'm not sure why I would want to do that? The structures do not have any
> padding to start with, and the layout of the image format implies that
> they will be naturally aligned (and in fact the boot ROM assumes this).
> Marking them as packed would only cause GCC to generate less efficient code.
Because this code is running on the build machine, not on target
hardware where is the boot ROM. It is compiled by host compiler and
build machine may have totally different padding / layout schematics and
C compiler is free in this case to put any padding between any two
members in that structure.
And if GCC generates different or less efficient code, it means that
__packed is really needed here.
next prev parent reply other threads:[~2021-08-22 17:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 4:46 [PATCH v2 0/4] sunxi: TOC0 image type support Samuel Holland
2021-08-22 4:46 ` [PATCH v2 1/4] tools: Separate image types which depend on OpenSSL Samuel Holland
2021-08-22 9:58 ` Pali Rohár
2021-08-22 17:32 ` Samuel Holland
2021-08-24 0:51 ` Andre Przywara
2021-08-22 4:46 ` [PATCH v2 2/4] tools: mkimage: Add Allwinner TOC0 support Samuel Holland
2021-08-22 10:07 ` Pali Rohár
2021-08-22 17:44 ` Samuel Holland
2021-08-22 17:51 ` Pali Rohár [this message]
2021-09-06 0:29 ` Andre Przywara
2021-08-22 4:46 ` [PATCH v2 3/4] sunxi: Support SPL in both eGON and TOC0 images Samuel Holland
2021-09-06 0:30 ` Andre Przywara
2021-08-22 4:46 ` [PATCH v2 4/4] sunxi: Support building a SPL as a TOC0 image Samuel Holland
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=20210822175155.gkfreikcgl37iyje@pali \
--to=pali@kernel.org \
--cc=andre.przywara@arm.com \
--cc=baruch@tkos.co.il \
--cc=bharat.gooty@broadcom.com \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=jagan@amarulasolutions.com \
--cc=jernej.skrabec@gmail.com \
--cc=judge.packham@gmail.com \
--cc=lauri.hintsala@silabs.com \
--cc=marek.behun@nic.cz \
--cc=mr.nuke.me@gmail.com \
--cc=naoki.hayama@lineo.co.jp \
--cc=patrick.delaunay@foss.st.com \
--cc=priyanka.jain@nxp.com \
--cc=rayagonda.kokatanur@broadcom.com \
--cc=samuel@sholland.org \
--cc=sbabic@denx.de \
--cc=sjg@chromium.org \
--cc=sr@denx.de \
--cc=sughosh.ganu@linaro.org \
--cc=takahiro.akashi@linaro.org \
--cc=twoerner@gmail.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.com \
/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.