From: "Pali Rohár" <pali@kernel.org>
To: 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:55:52 +0200 [thread overview]
Message-ID: <20230716195552.kcvjhowowxdbhyyt@pali> (raw)
In-Reply-To: <ZLRJaiIfPtqEB9Vb@aurel32.net>
On Sunday 16 July 2023 21:47:54 Aurelien Jarno wrote:
> 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.
Yes, I have it with default configuration. And I really do not know why
it is happening, I just described observations and that dtc -@ fixes
this issue. Note that this is about 1b rev1 (the first revision); so the
older HW, so maybe this can be a reason?
> 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.
Well, that is why I asked, if it is something for stable or not.
> Regards
> Aurelien
>
> --
> Aurelien Jarno GPG: 4096R/1DDD8C9B
> aurelien@aurel32.net http://aurel32.net
prev parent reply other threads:[~2023-07-16 19:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 16:24 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
2023-07-16 19:55 ` Pali Rohár [this message]
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=20230716195552.kcvjhowowxdbhyyt@pali \
--to=pali@kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®