From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>, linux-kernel@vger.kernel.org
Cc: Guan Xuetao <gxt@mprc.pku.edu.cn>,
Grant Likely <grant.likely@linaro.org>
Subject: Re: Status of 'unicore32' architecture in Linux kernel
Date: Mon, 01 Sep 2014 12:00:16 +0800 [thread overview]
Message-ID: <5403EF50.3080706@gmail.com> (raw)
In-Reply-To: <20140831235115.GA6248@roeck-us.net>
Firstly, what you have done encourage me, thanks.
On 9/1/14 7:51, Guenter Roeck wrote:
> Status of 'unicore32' architecture in Linux kernel
> --------------------------------------------------
>
> The idea was to create a working kernel and initramfs for the ongoing Linux
> kernel test project. This summary describes the result of this effort.
>
> Overall, conclusion is that the architecture would need some work
> (both in qemu and the kernel itself) to make it testable with qemu.
>
> Guenter
>
> ---------------------
> Toolchain used was from [1]. I did not attempt to build my own toolchain.
>
I also use it, but for me, hope we can use an open source toolchain for
it, in the future. If possible, I will be glad to join for it (develop
open source unicore32 gcc cross compiler with other related members).
> Configuration:
>
> make ARCH=unicore32 defconfig && make ARCH=unicore32
>
> This configuration currently fails to build in the upstream kernel.
> A patch to fix the problem has been submitted and is pending upstream
> integration [2]. With this patch merged, the 'defconfig' image can
> be built.
>
Thank you for what you have done.
> ----------------
> qemu
>
> Attempts to load the unicore32:defconfig image with qemu failed.
>
> Research points to [3], which includes a working unicore32 linux kernel
> in its linux repository [4], in branch unicore32-working. This branch
> includes a working unicore32 qemu configuration. It also includes
> a critical patch which is not available in the upstream kernel.
>
> unicore32: Add ocd console and qemu-defconfig to support qemu simulator
> This patch adds a primitive OCD console to communicate with qemu.
> The same code is already used for early console support.
>
> With this patch added, and with qemu_defconfig as provided by the same patch,
> it is possible to build and load a unicore32 image in qemu using the following
> qemu command line.
>
> qemu-system-unicore32 -curses -M puv3 -m 512 -kernel arch/unicore32/boot/zImage
>
For me, hope they also can be merged into upstream main line, next.
> Caveats:
> - The use of -nographic instead of -curses causes a qemu crash
> - The qemu emulation only accepts a built-in initramfs.
> - The only working image is arch/unicore32/boot/zImage.
> All other variants, arch/unicore32/boot/Image and vmlinux, cause a crash.
> The same (or a similar) crash is also seen if I don't provide a built-in
> kernel command line and try to load zImage.
> - There is no networking. There is another patch in the github linux
> respository [4] which is not available upstream. The driver was submitted
> for integration back in 2011 [5] but it was never accepted or merged.
>
For me, suggest also Cc to qemu-devel@nongnu.org, and gxt is the related
maintainer for qemu unicore32, too.
In the future (maybe several months later), I am glad to try to analyze
these caveats (but excuse me, at present, I have no enough time resource
on it).
> [1] http://mprc.pku.edu.cn/~guanxuetao/linux/
> [2] https://lkml.org/lkml/2014/8/31/86
> [3] https://github.com/gxt
> [4] git://github.com/gxt/linux.git
> [5] https://lkml.org/lkml/2011/5/27/17
>
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next prev parent reply other threads:[~2014-09-01 3:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-31 23:51 Status of 'unicore32' architecture in Linux kernel Guenter Roeck
2014-09-01 4:00 ` Chen Gang [this message]
2014-09-02 14:03 ` 回复: " Xuetao Guan
2014-09-02 15:58 ` Guenter Roeck
2014-09-03 0:09 ` 回复: " Xuetao Guan
2014-09-03 1:52 ` Guenter Roeck
2014-09-03 3:58 ` Guenter Roeck
2014-09-03 8:32 ` 回复: " Xuetao Guan
2014-09-05 5:52 ` Guenter Roeck
2014-09-05 6:13 ` 回复: " Xuetao Guan
2014-09-06 17:25 ` Guenter Roeck
2014-09-08 12:57 ` 回复: " Xuetao Guan
2014-09-08 13:35 ` Guenter Roeck
2014-09-09 0:58 ` 回复: " Xuetao Guan
2014-09-09 2:06 ` Guenter Roeck
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=5403EF50.3080706@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=grant.likely@linaro.org \
--cc=gxt@mprc.pku.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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;
as well as URLs for NNTP newsgroup(s).