From: Xi Ruoyao <xry111@xry111.site>
To: 李宇鹏 <liyupeng@zbhlos.com>
Cc: chenhuacai <chenhuacai@kernel.org>, kernel <kernel@xen0n.name>,
"jiaxun.yang" <jiaxun.yang@flygoat.com>,
loongarch <loongarch@lists.linux.dev>,
linux-kernel <linux-kernel@vger.kernel.org>,
caizp2008 <caizp2008@163.com>
Subject: Re: [PATCH 1/1] LoongArch: Fixed loongarch kernel csr_xxx implicit declaration.
Date: Wed, 31 Aug 2022 19:09:47 +0800 [thread overview]
Message-ID: <eb77b42f8ec4b67c1554dfac4a8efdfd8a4168c6.camel@xry111.site> (raw)
In-Reply-To: <AGcAvgDYFKf5CnvlznsCy4ok.3.1661932466929.Hmail.liyupeng@zbhlos.com>
On Wed, 2022-08-31 at 15:54 +0800, 李宇鹏 wrote:
>
> thank you for your reply。
> I used the latest gcc tool on the official website of loongson,gcc-
> 8.3.0.
> http://www.loongnix.cn/zh/toolchain/GNU/
Vanilla kernel cannot work with Loongnix:
1. In Loongnix, GRUB loads pass the essential information to the kernel
following "Loongson Firmware-Kernel Interface Specification". Vanilla
kernel does not support it and will never support it.
2. In Loongnix, the syscall numbers are different and the layout of some
data structures used in kernel UAPI is different. Any Loongnix
application invoking a syscall will likely blow up immediately on a
vanilla kernel.
These two problems are very difficult. There is some plan to insert
compatibility layers to work around them, but not even one line of code
has been written AFAIK.
So if you want to build a kernel for Loongnix, don't use the vanilla
kernel. If you just want to build a vanilla kernel with a pre-built
cross toolchain, use the toolchain from
https://kernel.org/pub/tools/crosstool/.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-08-31 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 6:14 Yupeng Li
2022-08-31 6:50 ` Xi Ruoyao
[not found] ` <AGcAvgDYFKf5CnvlznsCy4ok.3.1661932466929.Hmail.liyupeng@zbhlos.com>
2022-08-31 11:09 ` Xi Ruoyao [this message]
2022-08-31 14:49 ` 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=eb77b42f8ec4b67c1554dfac4a8efdfd8a4168c6.camel@xry111.site \
--to=xry111@xry111.site \
--cc=caizp2008@163.com \
--cc=chenhuacai@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=liyupeng@zbhlos.com \
--cc=loongarch@lists.linux.dev \
/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®