From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
U-Boot Custodians <u-boot-custodians@lists.denx.de>
Subject: Re: xPL Proposal
Date: Fri, 21 Feb 2025 13:25:56 -0600 [thread overview]
Message-ID: <20250221192556.GP1233568@bill-the-cat> (raw)
In-Reply-To: <20250221141940.GG1233568@bill-the-cat>
[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]
On Fri, Feb 21, 2025 at 08:19:40AM -0600, Tom Rini wrote:
> On Thu, Feb 20, 2025 at 06:30:18PM -0700, Simon Glass wrote:
> > Hi Tom,
> >
> > On Thu, 20 Feb 2025 at 13:40, Tom Rini <trini@konsulko.com> wrote:
> > >
> > > On Thu, Feb 20, 2025 at 11:13:34AM -0700, Simon Glass wrote:
[snip]
> > > I will look at "splg4" once it's somewhere on source.denx.de and I can
> > > look at it, and refrain from otherwise assuming how it solves the
> > > problems I had seen previously.
> >
> > I pushed an updated version to dm/splg-working but it is not very
> > updated. Still needs more work.
>
> Thanks.
So, after doing the remaining CONFIG_TEXT_BASE -> CONFIG_PPL_TEXT_BASE
changes, here's another example of the problem with your approach. What
stops xilinx_zynqmp_kria from building in splg-working is that
BUTTON was missing from scripts/conf_nospl. Annoyingly, a mrproper (or
since I always use O=, rm -rf) is needed for changes there to be picked
up, but that's maybe just a missing Makefile dependency line. But that
just makes it easier to see the next problem, which I don't see the
answer to. For PPL, we can build drivers/spi/zynqmp_gqspi.o just fine.
For SPL however:
CC spl/drivers/spi/zynqmp_gqspi.o
/home/trini/work/u-boot/u-boot/drivers/spi/zynqmp_gqspi.c: In function 'zynqmp_qspi_of_to_plat':
/home/trini/work/u-boot/u-boot/drivers/spi/zynqmp_gqspi.c:203:22: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
203 | plat->regs = (struct zynqmp_qspi_regs *)(dev_read_addr(bus) +
| ^
/home/trini/work/u-boot/u-boot/drivers/spi/zynqmp_gqspi.c:205:26: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
205 | plat->dma_regs = (struct zynqmp_qspi_dma_regs *)
| ^
And I don't see, really, what's even getting us down this error path.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-02-21 19:26 UTC|newest]
Thread overview: 112+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 15:03 xPL Proposal Simon Glass
2025-02-11 21:22 ` Tom Rini
2025-02-11 22:54 ` Simon Glass
2025-02-12 16:40 ` Tom Rini
2025-02-12 17:41 ` Simon Glass
2025-02-12 18:35 ` Tom Rini
2025-02-12 20:05 ` Simon Glass
2025-02-12 22:58 ` Tom Rini
2025-02-13 12:50 ` Simon Glass
2025-02-13 18:03 ` Tom Rini
2025-02-13 21:57 ` Simon Glass
2025-02-13 22:59 ` Tom Rini
2025-02-14 0:09 ` Simon Glass
2025-02-14 14:39 ` Tom Rini
2025-02-14 19:48 ` Simon Glass
2025-02-14 21:16 ` Tom Rini
2025-02-14 22:46 ` Simon Glass
2025-02-14 23:43 ` Tom Rini
2025-02-14 23:52 ` Simon Glass
2025-02-15 1:14 ` Tom Rini
2025-02-15 1:43 ` Simon Glass
2025-02-17 13:16 ` Simon Glass
2025-02-17 14:19 ` Tom Rini
2025-02-17 15:08 ` Simon Glass
2025-02-17 15:59 ` Tom Rini
2025-02-17 18:03 ` Simon Glass
2025-02-17 19:18 ` Tom Rini
2025-02-13 15:03 ` Generic U-Boot (was: Re: xPL Proposal) Caleb Connolly
2025-02-13 15:10 ` Generic U-Boot Caleb Connolly
2025-02-13 23:42 ` Tom Rini
2025-02-13 23:42 ` Generic U-Boot (was: Re: xPL Proposal) Tom Rini
2025-02-17 18:50 ` xPL Proposal Tom Rini
2025-02-17 19:11 ` Simon Glass
2025-02-17 19:21 ` Tom Rini
2025-02-17 19:34 ` Simon Glass
2025-02-17 19:47 ` Tom Rini
2025-02-17 20:17 ` Tom Rini
2025-02-17 20:39 ` Simon Glass
2025-02-18 0:40 ` Tom Rini
2025-02-18 12:08 ` Simon Glass
2025-02-18 14:46 ` Tom Rini
2025-02-19 0:03 ` Simon Glass
2025-02-19 1:07 ` Tom Rini
2025-02-19 14:48 ` Simon Glass
2025-02-19 20:34 ` Tom Rini
2025-02-20 13:19 ` Simon Glass
2025-02-20 15:16 ` Tom Rini
2025-02-20 16:43 ` Simon Glass
2025-02-20 17:40 ` Tom Rini
2025-02-20 18:13 ` Simon Glass
2025-02-20 20:40 ` Tom Rini
2025-02-21 1:30 ` Simon Glass
2025-02-21 13:56 ` Simon Glass
2025-02-21 14:19 ` Tom Rini
2025-02-21 14:19 ` Tom Rini
2025-02-21 15:03 ` Simon Glass
2025-02-21 17:53 ` Tom Rini
2025-02-21 18:10 ` Rate of change in the project (Was: Re: xPL Proposal) Tom Rini
2025-02-23 0:00 ` Simon Glass
2025-02-24 23:23 ` Tom Rini
2025-03-04 13:13 ` Rate of innovation in the project (Was: Re: Rate of change in the project) Simon Glass
2025-03-04 15:29 ` Tom Rini
2025-03-05 14:19 ` Simon Glass
2025-03-05 16:22 ` Tom Rini
2025-03-06 16:10 ` Simon Glass
2025-03-07 14:46 ` Tom Rini
2025-03-10 15:53 ` Tom Rini
2025-03-28 23:42 ` Simon Glass
2025-03-31 15:51 ` Tom Rini
2025-04-01 15:45 ` Simon Glass
2025-04-01 17:18 ` Tom Rini
2025-04-02 9:32 ` Mattijs Korpershoek
2025-04-02 19:22 ` Simon Glass
2025-04-02 22:35 ` Tom Rini
2025-04-02 23:55 ` Simon Glass
2025-04-03 14:27 ` Tom Rini
2025-04-06 21:15 ` Simon Glass
2025-04-06 22:53 ` Tom Rini
2025-04-07 10:45 ` Simon Glass
2025-04-07 19:10 ` Tom Rini
2025-02-21 19:25 ` Tom Rini [this message]
2025-02-21 22:54 ` xPL Proposal Simon Glass
2025-02-21 23:20 ` Tom Rini
2025-02-21 23:35 ` Simon Glass
2025-02-22 0:03 ` Tom Rini
2025-02-22 0:24 ` Simon Glass
2025-02-22 1:06 ` Tom Rini
2025-02-22 2:07 ` Simon Glass
2025-02-24 16:00 ` Tom Rini
2025-02-24 23:38 ` Simon Glass
2025-02-25 14:02 ` Tom Rini
2025-02-25 21:33 ` Simon Glass
2025-02-25 21:51 ` Tom Rini
2025-02-26 2:51 ` Simon Glass
2025-02-26 14:52 ` Tom Rini
2025-02-27 16:24 ` Simon Glass
2025-02-27 17:17 ` Tom Rini
2025-02-27 19:32 ` Simon Glass
2025-02-27 20:30 ` Tom Rini
2025-03-04 15:35 ` Simon Glass
2025-03-04 16:25 ` Tom Rini
2025-03-05 14:17 ` Simon Glass
2025-03-05 15:49 ` Tom Rini
2025-03-05 16:53 ` Simon Glass
2025-02-12 1:32 ` Marek Vasut
2025-02-12 13:37 ` Simon Glass
2025-02-13 14:15 ` Tom Rini
2025-02-13 14:33 ` Simon Glass
2025-02-13 15:59 ` Tom Rini
2025-02-13 19:56 ` Jonas Karlman
2025-02-13 18:02 ` Tom Rini
2025-02-17 15:03 ` 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=20250221192556.GP1233568@bill-the-cat \
--to=trini@konsulko.com \
--cc=sjg@chromium.org \
--cc=u-boot-custodians@lists.denx.de \
--cc=u-boot@lists.denx.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