From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Huacai Chen <chenhc@lemote.com>,
Ralf Baechle <ralf@linux-mips.org>,
James Hogan <jhogan@kernel.org>
Cc: Paul Burton <paul.burton@mips.com>,
Paul Burton <paulburton@kernel.org>,
linux-mips@linux-mips.org, linux-mips@vger.kernel.org,
Fuxin Zhang <zhangfx@lemote.com>,
Zhangjin Wu <wuzhangjin@gmail.com>,
Huacai Chen <chenhuacai@gmail.com>
Subject: Re: [PATCH V2] MIPS: Loongson: Add board_ebase_setup() support
Date: Thu, 7 Nov 2019 19:47:07 +0800 [thread overview]
Message-ID: <6f6ce0de-bad9-d1c4-f8d6-244b11eef0b1@flygoat.com> (raw)
In-Reply-To: <1572847781-21652-1-git-send-email-chenhc@lemote.com>
在 2019/11/4 下午2:09, Huacai Chen 写道:
> Old processors before Loongson-3A2000 have a 32bit ebase register and
> have no WG bit, new processors since Loongson-3A2000 have a 64bit ebase
> register and do have the WG bit. Unfortunately, Loongson processors
> which have the WG bit are slightly different from MIPS R2. This makes
> the generic ebase setup not suitable for every scenarios.
>
> To make Loongson's kernel be more robust, we add a board_ebase_setup()
> hook to ensure that CKSEG0 is always used for ebase. This is also useful
> on platforms where BIOS doesn't initialise an appropriate ebase.
>
> Signed-off-by: Huacai Chen <chenhc@lemote.com>
> ---
Acked-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
This patch is essential as most Loongson boards with Tianocore based
UEFI firmware didn't set their ebase correctly.
Should we backport it to stable?
--
Jiaxun Yang
next prev parent reply other threads:[~2019-11-07 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 6:09 [PATCH V2] MIPS: Loongson: Add board_ebase_setup() support Huacai Chen
2019-11-07 11:47 ` Jiaxun Yang [this message]
2019-11-08 1:21 ` Huacai Chen
2019-11-08 19:11 ` Paul Burton
2019-11-09 11:02 ` Huacai Chen
2019-11-15 8:22 ` Huacai Chen
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=6f6ce0de-bad9-d1c4-f8d6-244b11eef0b1@flygoat.com \
--to=jiaxun.yang@flygoat.com \
--cc=chenhc@lemote.com \
--cc=chenhuacai@gmail.com \
--cc=jhogan@kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=paulburton@kernel.org \
--cc=ralf@linux-mips.org \
--cc=wuzhangjin@gmail.com \
--cc=zhangfx@lemote.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 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.