From: Tom Rini <trini@konsulko.com>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: Simon Glass <sjg@chromium.org>,
Jagan Teki <jagan@amarulasolutions.com>,
Andre Przywara <andre.przywara@arm.com>,
Hans de Goede <hdegoede@redhat.com>,
Mario Six <mario.six@gdsys.cc>,
Stefano Babic <sbabic@nabladev.com>,
Fabio Estevam <festevam@gmail.com>,
"NXP i.MX U-Boot Team" <uboot-imx@nxp.com>,
"Ying-Chun Liu (PaulLiu)" <paul.liu@linaro.org>,
Roger Quadros <rogerq@kernel.org>,
Bajjuri Praneeth <praneeth@ti.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
u-boot@lists.denx.de,
Mattijs Korpershoek <mkorpershoek@kernel.org>
Subject: Re: [PATCH v3 00/20] Convert extension support to UCLASS and adds its support to boot flows
Date: Mon, 20 Oct 2025 11:17:07 -0600 [thread overview]
Message-ID: <20251020171707.GA6688@bill-the-cat> (raw)
In-Reply-To: <20251020190854.4b318829@kmaincent-XPS-13-7390>
[-- Attachment #1: Type: text/plain, Size: 3934 bytes --]
On Mon, Oct 20, 2025 at 07:08:54PM +0200, Kory Maincent wrote:
> On Mon, 20 Oct 2025 10:05:27 -0600
> Tom Rini <trini@konsulko.com> wrote:
>
> > On Mon, Oct 20, 2025 at 05:23:45PM +0200, Kory Maincent wrote:
> > > On Mon, 20 Oct 2025 08:37:29 -0600
> > > Tom Rini <trini@konsulko.com> wrote:
> > >
> > > > On Mon, Oct 20, 2025 at 08:15:48AM -0600, Tom Rini wrote:
> > > > > On Mon, Oct 20, 2025 at 11:50:09AM +0200, Kory Maincent wrote:
> > > > > > On Sun, 19 Oct 2025 10:48:37 -0600
> > > > > > Tom Rini <trini@konsulko.com> wrote:
> > > > > >
> > > > > > > On Sun, Oct 19, 2025 at 02:05:51PM +0100, Simon Glass wrote:
> > > > > > > > Hi Kory,
> > > > > > > >
> > > > > > > > On Mon, 13 Oct 2025 at 14:32, Kory Maincent (TI.com)
> > > > > > > > <kory.maincent@bootlin.com> wrote:
> > > > > > > > >
> > > > > > > > > This series converts the extension board framework to use
> > > > > > > > > UCLASS as requested by Simon Glass, then adds extension support
> > > > > > > > > to pxe_utils and bootmeth_efi (not tested) to enable extension
> > > > > > > > > boards devicetree load in the standard boot process.
> > > > > > > > >
> > > > > > > > > I can't test the imx8 extension scan enabled by the
> > > > > > > > > imx8mm-cl-iot-gate_defconfig as I don't have this board.
> > > > > > > > > I also can't test the efi bootmeth change as I don't have such
> > > > > > > > > board.
> > > > > > > >
> > > > > > > > You can test this with sandbox, using one of the bootmeth tests,
> > > > > > > > perhaps. Let me know if you need help with this.
> > > > > > >
> > > > > > > But the question is, does the real hardware platform work
> > > > > > > before/after this, not does the sandbox test still work
> > > > > > > before/after this.
> > > > > >
> > > > > > It seems the bootlflow scan is not working on the sandbox on next
> > > > > > branch. Is this issue known?
> > > > >
> > > > > Is it fine on master? The next branch will be out of date until it
> > > > > re-opens with -rc2 being released (2 weeks from today).
> > > >
> > > > ... out of sync local calendar, 3 weeks from today, not 2.
> > >
> > > bootstd test suit is not working on master with the sandbox_defconfig:
> > > https://termbin.com/un0p
> > >
> > > Noticeable things are;
> > > test/boot/bootdev.c:160, bootdev_test_any(): 0 == bootdev_find_by_any(seq,
> > > &dev, &mflags): Expected 0x0 (0), got 0xffffffed (-19) Test:
> > > bootdev_test_any: bootdev.c (flat tree) test/boot/bootdev.c:160,
> > > bootdev_test_any(): 0 == bootdev_find_by_any(seq, &dev, &mflags): Expected
> > > 0x0 (0), got 0xffffffed (-19) Test 'bootdev_test_any' failed 2 times
> > >
> > > And a nice segfault:
> > > Test: bootflow_set_arg: bootflow.c
> > > Test: bootflow_system: bootflow.c
> > > [3] 569337 segmentation fault (core dumped) ./u-boot
> > >
> > > Maybe things are missing to run sandbox_defconfig on my computer?
> > > With the sandbox64_defconfig there is not core dump anymore but there is
> > > still the failed line:
> > > Test 'bootdev_test_bootable' failed 2 times
> > >
> > > And the uboot is reboot infinitely during the bootflow test:
> > > ./u-boot -T -c "ut bootstd"
> > > https://termbin.com/alu5
> >
> > I see the same thing you do when running them outside of pytest, but
> > they're also fine within pytest.
> > https://docs.u-boot.org/en/latest/develop/pytest/usage.html should help
> > get you started, and you can just run all of the ut tests under that.
>
> Weird I got errors also within pytest.
> See the html test log attached generated by the following command:
> ./test/py/test.py --bd sandbox -k bootstd
Same. There's some implicit dependencies around I believe. Doing "-k ut"
should work, as I tried that (via my wrapper around all this) as well as
just running all the tests (which is longer).
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-10-20 17:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 13:32 [PATCH v3 00/20] Convert extension support to UCLASS and adds its support to boot flows Kory Maincent (TI.com)
2025-10-13 13:32 ` [PATCH v3 01/20] MAINTAINERS: Add maintainer for extension board support Kory Maincent (TI.com)
2025-10-13 13:32 ` [PATCH v3 02/20] board: ti: Exclude cape detection from XPL builds Kory Maincent (TI.com)
2025-10-13 13:32 ` [PATCH v3 03/20] board: ti: Fix CAPE_EEPROM_BUS_NUM Kconfig dependency Kory Maincent (TI.com)
2025-10-13 13:32 ` [PATCH v3 04/20] board: sunxi: Exclude DIP detection from XPL builds Kory Maincent (TI.com)
2025-10-13 13:32 ` [PATCH v3 05/20] board: compulab: Exclude compulab extension board " Kory Maincent (TI.com)
2025-10-13 13:32 ` [PATCH v3 06/20] include: extension_board: Document the extension structure Kory Maincent (TI.com)
2025-10-13 13:32 ` [PATCH v3 07/20] boot: Move extension board support from cmd/ to boot/ Kory Maincent (TI.com)
2025-10-13 13:32 ` [PATCH v3 08/20] boot: Add UCLASS support for extension boards Kory Maincent (TI.com)
2025-10-19 13:05 ` Simon Glass
2025-10-13 13:32 ` [PATCH v3 09/20] board: ti: Refactor cape detection code for readability Kory Maincent (TI.com)
2025-10-13 13:32 ` [PATCH v3 10/20] board: ti: Convert cape detection to use UCLASS framework Kory Maincent (TI.com)
2025-10-13 13:32 ` [PATCH v3 11/20] board: sunxi: Refactor CHIP board extension code Kory Maincent (TI.com)
2025-10-13 13:32 ` [PATCH v3 12/20] board: sunxi: Convert extension support to UCLASS framework Kory Maincent (TI.com)
2025-10-13 13:32 ` [PATCH v3 13/20] board: sandbox: Improve extension board scan implementation Kory Maincent (TI.com)
2025-10-13 13:32 ` [PATCH v3 14/20] board: sandbox: Convert extension support to UCLASS framework Kory Maincent (TI.com)
2025-10-19 13:06 ` Simon Glass
2025-10-13 13:32 ` [PATCH v3 15/20] board: compulab: Convert imx8mm-cl-iot-gate to UCLASS extension framework Kory Maincent (TI.com)
2025-10-13 13:32 ` [PATCH v3 16/20] boot: Remove legacy extension board support Kory Maincent (TI.com)
2025-10-13 13:32 ` [PATCH v3 17/20] boot: extension: Move overlay apply custom logic to command level Kory Maincent (TI.com)
2025-10-13 13:32 ` [PATCH v3 18/20] boot: pxe_utils: Add extension board devicetree overlay support Kory Maincent (TI.com)
2025-10-13 13:32 ` [PATCH v3 19/20] boot: bootmeth_efi: Refactor distro_efi_try_bootflow_files return logic Kory Maincent (TI.com)
2025-10-13 13:32 ` [PATCH v3 20/20] boot: bootmeth_efi: Add extension board devicetree overlay support Kory Maincent (TI.com)
2025-10-19 13:05 ` [PATCH v3 00/20] Convert extension support to UCLASS and adds its support to boot flows Simon Glass
2025-10-19 16:48 ` Tom Rini
2025-10-20 9:50 ` Kory Maincent
2025-10-20 14:15 ` Tom Rini
2025-10-20 14:37 ` Tom Rini
2025-10-20 15:23 ` Kory Maincent
2025-10-20 16:05 ` Tom Rini
2025-10-20 17:08 ` Kory Maincent
2025-10-20 17:17 ` Tom Rini [this message]
2025-10-21 7:40 ` Mattijs Korpershoek
[not found] ` <20251021110225.2d94a13b@kmaincent-XPS-13-7390>
2025-10-21 9:52 ` Simon Glass
2025-10-21 12:44 ` Kory Maincent
2025-10-21 13:49 ` Tom Rini
2025-10-21 14:29 ` Kory Maincent
2025-10-21 14:36 ` Tom Rini
2025-10-21 16:54 ` Kory Maincent
2025-10-21 17:29 ` Tom Rini
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=20251020171707.GA6688@bill-the-cat \
--to=trini@konsulko.com \
--cc=andre.przywara@arm.com \
--cc=festevam@gmail.com \
--cc=hdegoede@redhat.com \
--cc=jagan@amarulasolutions.com \
--cc=kory.maincent@bootlin.com \
--cc=mario.six@gdsys.cc \
--cc=mkorpershoek@kernel.org \
--cc=paul.liu@linaro.org \
--cc=praneeth@ti.com \
--cc=rogerq@kernel.org \
--cc=sbabic@nabladev.com \
--cc=sjg@chromium.org \
--cc=thomas.petazzoni@bootlin.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.