From: Aurelien Jarno <aurelien@aurel32.net>
To: "Pali Rohár" <pali@kernel.org>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Backporting commits for generating rpi dtb symbols to stable
Date: Sun, 16 Jul 2023 21:47:54 +0200 [thread overview]
Message-ID: <ZLRJaiIfPtqEB9Vb@aurel32.net> (raw)
In-Reply-To: <20230716162444.zzvkm4rh7s7lu37x@pali>
Hi,
On 2023-07-16 18:24, Pali Rohár wrote:
> Hello,
>
> I see that raspberry pi bootloader throws ton of warnings when supplied
> DTB file does not contain /__symbols__/ node.
>
> On RPI 1B rev1 it looks like this:
>
> dterror: no symbols found
> dterror: no symbols found
> dterror: no symbols found
> dterror: no symbols found
> dterror: no symbols found
> dterror: no symbols found
> dterror: no symbols found
> dterror: no symbols found
> dterror: no symbols found
> dterror: no symbols found
Do you have those errors with the default configuration? On a RPI 4,
this only happens when setting uart_2ndstage to 1 in config.txt.
According to the documentation, this option enables diagnostic
information from the main firmware.
Unless this is different on RPI 1B, this means we are talking about a
warning that happens when enabling diagnostic information, so I am not
sure it warrants a change to stable kernels.
Regards
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://aurel32.net
next prev parent reply other threads:[~2023-07-16 20:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 16:24 Backporting commits for generating rpi dtb symbols to stable Pali Rohár
2023-07-16 16:32 ` Greg KH
2023-07-16 16:38 ` Pali Rohár
2023-07-16 19:08 ` Greg KH
2023-07-16 19:51 ` Pali Rohár
2023-07-17 10:38 ` Florian Fainelli
2023-07-16 19:47 ` Aurelien Jarno [this message]
2023-07-16 19:55 ` Pali Rohár
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=ZLRJaiIfPtqEB9Vb@aurel32.net \
--to=aurelien@aurel32.net \
--cc=florian.fainelli@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pali@kernel.org \
--cc=stable@vger.kernel.org \
/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.