From: Conor Dooley <conor@kernel.org>
To: Tom Rini <trini@konsulko.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
Simon Glass <sjg@chromium.org>,
U-Boot Mailing List <u-boot@lists.denx.de>,
Raymond Mao <raymond.mao@linaro.org>, Marek Vasut <marex@denx.de>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Andre Przywara <andre.przywara@arm.com>,
Baruch Siach <baruch@tkos.co.il>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Jerry Van Baren <vanbaren@cideas.com>,
Johan Jonker <jbx6244@gmail.com>,
Kever Yang <kever.yang@rock-chips.com>,
Samuel Holland <samuel@sholland.org>,
Shiji Yang <yangshiji66@outlook.com>
Subject: Re: [PATCH v7] fdt: Allow the devicetree to come from a bloblist
Date: Mon, 22 Jan 2024 18:55:01 +0000 [thread overview]
Message-ID: <20240122-finicky-ancient-797ba048f927@spud> (raw)
In-Reply-To: <20240122184717.GQ3652023@bill-the-cat>
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
On Mon, Jan 22, 2024 at 01:47:17PM -0500, Tom Rini wrote:
> On Mon, Jan 22, 2024 at 06:36:31PM +0000, Conor Dooley wrote:
> > Hey,
> >
> > On Tue, Jan 16, 2024 at 01:48:06PM +0000, Conor Dooley wrote:
> > > Yo,
> > >
> > > On Wed, Jan 03, 2024 at 06:49:19PM -0700, Simon Glass wrote:
> > > > Standard passage provides for a bloblist to be passed from one firmware
> > > > phase to the next. That can be used to pass the devicetree along as well.
> > > > Add an option to support this.
> > > >
> > > > Tests for this will be added as part of the Universal Payload work.
> > > >
> > > > Signed-off-by: Simon Glass <sjg@chromium.org>
> > >
> > > Since this was merged into master, U-Boot is no longer booting on my
> > > icicle kit (At least that's what my bisection tells me). This is a
> > > RISC-V board and U-Boot for it is built from
> > > microchip_mpfs_icicle_defconfig.
> > >
> > > There's zero output on the console from U-Boot at all, the last thing
> > > that I see is OpenSBI before things grind to a halt.
> >
> > Just wondering if there's anything I can do to help this one along?
> > Got a red CI complaining at me every morning about it :|
>
> Well, can you please look in to what part of this is causing the
> failure? I don't really see what would have changed on
> microchip_mpfs_icicle_defconfig from this as BLOBLIST isn't set before
> nor after this change.
Sure. I'll try to look into it more tomorrow.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-01-22 18:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 1:49 [PATCH v7] fdt: Allow the devicetree to come from a bloblist Simon Glass
2024-01-04 13:51 ` Tom Rini
2024-01-04 14:24 ` Ilias Apalodimas
2024-01-08 0:16 ` Simon Glass
2024-01-16 13:48 ` Conor Dooley
2024-01-22 18:36 ` Conor Dooley
2024-01-22 18:47 ` Tom Rini
2024-01-22 18:55 ` Conor Dooley [this message]
2024-01-23 11:27 ` Conor Dooley
2024-01-23 18:03 ` Tom Rini
2024-02-06 17:20 ` Conor Dooley
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=20240122-finicky-ancient-797ba048f927@spud \
--to=conor@kernel.org \
--cc=andre.przywara@arm.com \
--cc=baruch@tkos.co.il \
--cc=conor.dooley@microchip.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jbx6244@gmail.com \
--cc=kever.yang@rock-chips.com \
--cc=marex@denx.de \
--cc=raymond.mao@linaro.org \
--cc=samuel@sholland.org \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vanbaren@cideas.com \
--cc=xypron.glpk@gmx.de \
--cc=yangshiji66@outlook.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox