From: "Xuetao Guan " <gxt@pku.edu.cn>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org, Guan Xuetao <gxt@mprc.pku.edu.cn>,
Chen Gang <gang.chen.5i5j@gmail.com>,
Grant Likely <grant.likely@linaro.org>
Subject: 回复: Status of 'unicore32' architecture in Linux kernel
Date: Tue, 2 Sep 2014 22:03:48 +0800 (CST) [thread overview]
Message-ID: <1418547425.30923.1409666628661.JavaMail.root@bj-mail03.pku.edu.cn> (raw)
In-Reply-To: <20140831235115.GA6248@roeck-us.net>
Sorry for late reply.
----- Guenter Roeck <linux@roeck-us.net> 写道:
> 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.
Great. And there's a lot of work to do for unicore32.
>
> Guenter
>
> ---------------------
> Toolchain used was from [1]. I did not attempt to build my own toolchain.
>
> 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.
Thanks. I'll apply it in my repo.
>
> ----------------
> 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.
Yes. And these patches need to be reviewed and reconsidered.
I'll try to do that in this month.
>
> 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.
Do you mean there's the same/similar code in QEMU.
>
> 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
>
> Caveats:
> - The use of -nographic instead of -curses causes a qemu crash
Yes, since qemu curses code was modified to meet the simple OCD console requirement.
> - The qemu emulation only accepts a built-in initramfs.
Yes, github version only support built-in initramfs.
NFS+LFS could be also supported, and puv3-pci sim should be added at first.
> - 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.
Sorry for that. That should be fixed.
> - 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.
Yes, exactly.
Thanks Guenter.
>
> ------------------------
> [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
next prev parent reply other threads:[~2014-09-02 14:04 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
2014-09-02 14:03 ` Xuetao Guan [this message]
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=1418547425.30923.1409666628661.JavaMail.root@bj-mail03.pku.edu.cn \
--to=gxt@pku.edu.cn \
--cc=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).