From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: Marek Vasut <marek.vasut@mailbox.org>,
U-Boot Mailing List <u-boot@lists.denx.de>,
Fabio Estevam <festevam@gmail.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: [PATCH v2 00/22] Deal with exfat versus byteorder
Date: Thu, 1 May 2025 09:35:17 -0600 [thread overview]
Message-ID: <20250501153517.GI1261075@bill-the-cat> (raw)
In-Reply-To: <CAFLszTi2mHGGO+wXBfKc1j3c3Hh4kzoOdyOgbmySYow7LgZYXQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4768 bytes --]
On Thu, May 01, 2025 at 09:03:18AM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Thu, 1 May 2025 at 08:17, Tom Rini <trini@konsulko.com> wrote:
> >
> > On Thu, May 01, 2025 at 06:07:15AM -0600, Simon Glass wrote:
> > > Hi Marek,
> > >
> > > On Wed, 30 Apr 2025 at 20:02, Marek Vasut <marek.vasut@mailbox.org> wrote:
> > > >
> > > > On 5/1/25 3:04 AM, Simon Glass wrote:
> > > > > Since exfat has its own byteorder functions we need to be careful about
> > > > > including the normal U-Boot byteorder headers in code included by exfat.
> > > >
> > > > ...
> > > >
> > > > > net: Use a forward declaration for cmd_tbl in net-common.h
> > > > > congatec: Include env.h to permit reading the environment
> > > > > dhelectronics: Include env.h to permit reading the environment
> > > > > imx8ulp_evk: Include env.h to permit reading the environment
> > > > > venice: Include env.h to permit reading the environment
> > > > > phytec: Include env.h to permit reading the environment
> > > > > ronetix: Include env.h to permit reading the environment
> > > > > toradex: Include env.h to permit reading the environment
> > > > > advantech: Include env.h in imx8qm_dmsse20_a1
> > > > > tegra: Include env.h to permit reading the environment
> > > > > synology: Include env.h to permit reading the environment
> > > > > amlogic: Include env.h to permit reading the environment
> > > > > freescale: Include env.h to permit reading the environment
> > > > > google: Include env.h to permit reading the environment
> > > > > liebherr: Include env.h to permit reading the environment
> > > > > technexion: Include env.h to permit reading the environment
> > > > > elf: Only use network environment-variables if net enabled
> > > > > net: Include byteorder in net6.h
> > > > > net: Include string.h in net-legacy.h
> > > > > net: Include env.h in pcap.c
> > > > > net: dc2114x: Include env.h to permit reading the environment
> > > > > net: Move env_get_ip() out of the header file
> > > > >
> > > > > arch/arm/mach-tegra/dt-setup.c | 1 +
> > > > > board/Synology/ds414/ds414.c | 1 +
> > > > > .../imx8qm_dmsse20_a1/imx8qm_dmsse20_a1.c | 1 +
> > > > > board/amlogic/jethub-j100/jethub-j100.c | 1 +
> > > > > board/congatec/cgtqmx8/cgtqmx8.c | 3 +-
> > > > > board/dhelectronics/common/dh_common.c | 1 +
> > > > > board/freescale/imx8ulp_evk/imx8ulp_evk.c | 1 +
> > > > > board/freescale/mx7dsabresd/mx7dsabresd.c | 1 +
> > > > > board/gateworks/venice/venice.c | 1 +
> > > > > board/google/chameleonv3/board.c | 2 +
> > > > > board/liebherr/xea/xea.c | 1 +
> > > > > .../common/phytec_som_detection_blocks.c | 1 +
> > > > > board/ronetix/imx8mq-cm/imx8mq_cm.c | 1 +
> > > > > board/technexion/pico-imx7d/pico-imx7d.c | 1 +
> > > > > board/toradex/colibri_imx7/colibri_imx7.c | 1 +
> > > > > board/toradex/verdin-imx8mm/verdin-imx8mm.c | 2 +-
> > > > > cmd/elf.c | 41 ++++++++++---------
> > > > > drivers/net/dc2114x.c | 1 +
> > > > > include/net-common.h | 9 ++--
> > > > > include/net-legacy.h | 1 +
> > > > > include/net6.h | 1 +
> > > > > net/net-common.c | 6 +++
> > > > > net/pcap.c | 1 +
> > > > > 23 files changed, 53 insertions(+), 27 deletions(-)
> > > > There are no fs changes in this series , what does this series have to
> > > > do with exfat ?
> > >
> > > I found that in some situations, the exfat code includes
> > > linux/byteorder.h instead of its own local byteorder, which is
> > > implemented differently. This then causes build errors in the exfat
> > > code. One way to trigger it is by adding '#include net.h' to
> > > include/efi.h
> >
> > Setting aside if it's a good idea to have efi.h include net.h, we should
> > unwind what the heck is going on. The build error is on CLUSTER_INVALID
> > somehow becoming weird. Looking harder at this, the problem I see is
> > that include/fs.h includes <rtc.h> (which in turn pulls in many things)
> > when it only needs <rtc_defs.h> for struct rtc_time. This however
> > exposes some other implicit includes. I'll go and take a look at hunting
> > these all down.
>
> OK. I wonder if we could drop the special byteorder macros in exfat?
Potentially. I'll leave it to Marek to comment on how much pain and
future pain that might cause.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2025-05-01 15:35 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 1:04 [PATCH v2 00/22] Deal with exfat versus byteorder Simon Glass
2025-05-01 1:04 ` [PATCH v2 01/22] net: Use a forward declaration for cmd_tbl in net-common.h Simon Glass
2025-05-01 1:04 ` [PATCH v2 02/22] congatec: Include env.h to permit reading the environment Simon Glass
2025-05-01 14:06 ` Tom Rini
2025-05-01 15:04 ` Simon Glass
2025-05-01 15:33 ` Tom Rini
2025-05-02 13:11 ` Simon Glass
2025-05-02 14:06 ` Tom Rini
2025-05-02 14:52 ` Simon Glass
2025-05-02 15:04 ` Tom Rini
2025-05-03 2:10 ` Simon Glass
2025-05-03 16:30 ` Tom Rini
2025-05-03 16:37 ` Tom Rini
2025-05-03 21:27 ` Simon Glass
2025-05-05 14:43 ` Tom Rini
2025-05-01 1:04 ` [PATCH v2 03/22] dhelectronics: " Simon Glass
2025-05-01 1:04 ` [PATCH v2 04/22] imx8ulp_evk: " Simon Glass
2025-05-01 1:04 ` [PATCH v2 05/22] venice: " Simon Glass
2025-05-01 1:04 ` [PATCH v2 06/22] phytec: " Simon Glass
2025-05-01 1:04 ` [PATCH v2 07/22] ronetix: " Simon Glass
2025-05-01 1:04 ` [PATCH v2 08/22] toradex: " Simon Glass
2025-05-01 1:04 ` [PATCH v2 09/22] advantech: Include env.h in imx8qm_dmsse20_a1 Simon Glass
2025-05-08 10:27 ` Oliver Graute
2025-05-01 1:04 ` [PATCH v2 10/22] tegra: Include env.h to permit reading the environment Simon Glass
2025-05-01 1:04 ` [PATCH v2 11/22] synology: " Simon Glass
2025-05-01 3:21 ` Tony Dinh
2025-05-02 8:17 ` Stefan Roese
2025-05-01 1:04 ` [PATCH v2 12/22] amlogic: " Simon Glass
2025-05-08 16:18 ` Viacheslav
2025-05-01 1:04 ` [PATCH v2 13/22] freescale: " Simon Glass
2025-05-01 1:04 ` [PATCH v2 14/22] google: " Simon Glass
2025-05-01 1:04 ` [PATCH v2 15/22] liebherr: " Simon Glass
2025-05-01 6:17 ` Lukasz Majewski
2025-05-01 1:04 ` [PATCH v2 16/22] technexion: " Simon Glass
2025-05-01 1:04 ` [PATCH v2 17/22] elf: Only use network environment-variables if net enabled Simon Glass
2025-05-05 12:37 ` Jerome Forissier
2025-05-01 1:04 ` [PATCH v2 18/22] net: Include byteorder in net6.h Simon Glass
2025-05-01 1:04 ` [PATCH v2 19/22] net: Include string.h in net-legacy.h Simon Glass
2025-05-05 12:38 ` Jerome Forissier
2025-05-01 1:04 ` [PATCH v2 20/22] net: Include env.h in pcap.c Simon Glass
2025-05-01 1:04 ` [PATCH v2 21/22] net: dc2114x: Include env.h to permit reading the environment Simon Glass
2025-05-01 1:04 ` [PATCH v2 22/22] net: Move env_get_ip() out of the header file Simon Glass
2025-05-01 2:02 ` [PATCH v2 00/22] Deal with exfat versus byteorder Marek Vasut
2025-05-01 12:07 ` Simon Glass
2025-05-01 14:17 ` Tom Rini
2025-05-01 15:03 ` Simon Glass
2025-05-01 15:35 ` Tom Rini [this message]
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=20250501153517.GI1261075@bill-the-cat \
--to=trini@konsulko.com \
--cc=festevam@gmail.com \
--cc=marek.vasut@mailbox.org \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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 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.