From: "Bjørn Mork" <bjorn@mork.no>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Jiaxun Yang <jiaxun.yang@flygoat.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
linux-kernel@vger.kernel.org,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] MIPS: fw: Gracefully handle unknown firmware protocols
Date: Sun, 25 Aug 2024 17:47:47 +0200 [thread overview]
Message-ID: <87jzg4y57g.fsf@miraculix.mork.no> (raw)
In-Reply-To: <alpine.DEB.2.21.2408251612500.30766@angie.orcam.me.uk> (Maciej W. Rozycki's message of "Sun, 25 Aug 2024 16:18:19 +0100 (BST)")
"Maciej W. Rozycki" <macro@orcam.me.uk> writes:
> On Sun, 25 Aug 2024, Bjørn Mork wrote:
>
>> But I can't make that match what U-Boot does. AFAICS,
>> u-boot/arch/mips/lib/bootm.c doesn't care about 32 or 64 bit, and simply
>> does:
>
> U-Boot isn't the only firmware used with MIPS systems, and in fact it's
> quite a recent addition; e.g. DEC REX and SGI ARCS firmware goes back at
> least to 1990 and we continue supporting these systems. There's also CFE,
> PMON, YAMON, etc.
I know. That's what I'm trying to make us support :-)
We can't blindly assume that all those firmwares implement the exact
same command line and environment protocol as U-Boot. Yamon obviously
uses something similar enough. But what about the others?
As mentioned, we're currently failing to boot from Bootware because of
the relaxed checking here. Something needs to be done about that.
Bjørn
next prev parent reply other threads:[~2024-08-25 15:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-24 14:41 [PATCH] MIPS: fw: Gracefully handle unknown firmware protocols Bjørn Mork
2024-08-25 12:50 ` Jiaxun Yang
2024-08-25 13:56 ` Maciej W. Rozycki
2024-08-25 14:44 ` Bjørn Mork
2024-08-25 15:18 ` Maciej W. Rozycki
2024-08-25 15:47 ` Bjørn Mork [this message]
2024-08-25 19:59 ` Maciej W. Rozycki
2024-08-26 8:52 ` Bjørn Mork
2024-08-26 13:17 ` Jiaxun Yang
2024-08-28 22:15 ` kernel test robot
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=87jzg4y57g.fsf@miraculix.mork.no \
--to=bjorn@mork.no \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=stable@vger.kernel.org \
--cc=tsbogend@alpha.franken.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