From: Roger Quadros <rogerq@kernel.org>
To: Tom Rini <trini@konsulko.com>
Cc: sjg@chromium.org, vigneshr@ti.com, nm@ti.com, praneeth@ti.com,
u-boot@lists.denx.de
Subject: Re: [u-boot PATCH 2/3] tools/fdtgrep: Include __symbols__ table
Date: Sat, 11 Jun 2022 11:43:48 +0300 [thread overview]
Message-ID: <75f9f20a-53ae-683e-5597-57cb5e8fa7fa@kernel.org> (raw)
In-Reply-To: <20220610134251.GA784066@bill-the-cat>
On 10/06/2022 16:42, Tom Rini wrote:
> On Mon, May 09, 2022 at 10:29:35AM +0300, Roger Quadros wrote:
>
>> This is required for overlays to work at SPL.
>>
>> Signed-off-by: Roger Quadros <rogerq@kernel.org>
>
> This breaks booting my dra7xx_evm and I get no output in SPL.
>
Thanks for checking. I'll try to debug what's wrong using beagle_x15.
Is SPL size increase to blame?
Maybe we should enable this only based on some config symbol?
cheers,
-roger
next prev parent reply other threads:[~2022-06-11 8:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 7:29 [u-boot PATCH 0/3] k3-am642-evm-u-boot: Use binman to generate u-boot.img and tispl.bin Roger Quadros
2022-05-09 7:29 ` [u-boot PATCH 1/3] tools: binman: add ti-secure entry type Roger Quadros
2022-05-09 7:29 ` [u-boot PATCH 2/3] tools/fdtgrep: Include __symbols__ table Roger Quadros
2022-06-10 13:42 ` Tom Rini
2022-06-11 8:43 ` Roger Quadros [this message]
2022-06-11 13:26 ` Tom Rini
2022-05-09 7:29 ` [u-boot PATCH 3/3] k3-am642-evm-u-boot: Use binman to generate u-boot.img and tispl.bin Roger Quadros
2022-05-24 22:03 ` Andrew Davis
2022-05-25 8:30 ` Roger Quadros
2022-05-25 15:14 ` Andrew Davis
2022-05-26 7:28 ` Roger Quadros
2022-05-26 14:15 ` Tom Rini
2022-05-27 17:50 ` Alper Nebi Yasak
2022-05-31 5:06 ` Roger Quadros
2022-05-31 14:15 ` Andrew Davis
2022-06-02 17:34 ` Alper Nebi Yasak
2022-05-09 13:39 ` [u-boot PATCH 0/3] " 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=75f9f20a-53ae-683e-5597-57cb5e8fa7fa@kernel.org \
--to=rogerq@kernel.org \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.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