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: 回复: Re: 回复: Status of 'unicore32' architecture in Linux kernel
Date: Wed, 3 Sep 2014 08:09:28 +0800 (CST) [thread overview]
Message-ID: <717685015.32253.1409702968099.JavaMail.root@bj-mail03.pku.edu.cn> (raw)
In-Reply-To: <20140902155856.GA16029@roeck-us.net>
[...]
> >
> > >
> > > 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.
> >
> No, I mean that the ocd functions in the linux kernel (such as ocd_putc) are
> used by both earlyprintk and the ocd console code.
Yes. By the way, it's only for qemu and fpga debug.
>
> > >
> > > 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 lack of support for -nographic is a problem for scripted testing.
> The issue is that we have to interpret console output for scripted testing,
> and having to go through curses makes that a bit difficult.
>
> Wonder if '-nographic' can be modeled as '-curses' with no available terminal
> configuration. At least in theory that should work, but executing the above
> command with TERM=dumb yields no output. Wonder how difficult it would be to
> change that.
I see. I'll try to make -nographic work anyway.
>
> > > - 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.
>
> Too bad. Not exactly necessary for our current scope of testing, but it would be
> nice to be able to test networking.
I'll review and submit networking code again. Or, maybe pci-nic function, to support qemu as well.
>
> > Thanks Guenter.
> >
> You are welcome. Thanks for the feedback.
>
> Guenter
Thanks.
Xuetao
next prev parent reply other threads:[~2014-09-03 0:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-31 23:51 Guenter Roeck
2014-09-01 4:00 ` Chen Gang
2014-09-02 14:03 ` 回复: " Xuetao Guan
2014-09-02 15:58 ` Guenter Roeck
2014-09-03 0:09 ` Xuetao Guan [this message]
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=717685015.32253.1409702968099.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
Powered by JetHome