From: Guenter Roeck <linux@roeck-us.net>
To: gxt@mprc.pku.edu.cn
Cc: linux-kernel@vger.kernel.org, gxt@pku.edu.cn,
gang.chen.5i5j@gmail.com, Qin Rui <qinrui@pku.edu.cn>
Subject: Re: [PATCH 1/4] unicore32-oldabi: add CONFIG_UNICORE32_OLDABI for distinguishing two ABIs
Date: Mon, 15 Sep 2014 13:08:20 -0700 [thread overview]
Message-ID: <20140915200820.GD18175@roeck-us.net> (raw)
In-Reply-To: <1b5cc90293670926b5a1e5a06995e527442f8bde.1410502415.git.gxt@mprc.pku.edu.cn>
On Fri, Sep 12, 2014 at 02:41:43PM +0800, gxt@mprc.pku.edu.cn wrote:
> From: Guan Xuetao <gxt@mprc.pku.edu.cn>
>
> Signed-off-by: Guan Xuetao <gxt@mprc.pku.edu.cn>
> Signed-off-by: Qin Rui <qinrui@pku.edu.cn>
This series lets me build and run an initramfs with the published toolchain,
after adding the patch 'unicore32: Add ocd console and qemu-defconfig
to support qemu simulator' as well to get console output. So feel free
to add
Tested-by: Guenter Roeck <linux@roeck-us.net>
to the series.
I have a couple of questions:
- After adding the patch 'unicore32: Add ocd console and qemu-defconfig
to support qemu simulator', I only get console output, but no input.
Is there a way (for example with a qemu command line option) to get
input as well ?
- Is it possible to connect a console to a serial device in qemu (in other
words to run the image in qemu without the ocd console patch) ?
- Is there a working description on how to create a toolchain for the _new_
ABI ? Alternatively, would it be possible to publish such a toolchain ?
Thanks a lot,
Guenter
> ---
> arch/unicore32/Kconfig | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/arch/unicore32/Kconfig b/arch/unicore32/Kconfig
> index 928237a..e5d25b4 100644
> --- a/arch/unicore32/Kconfig
> +++ b/arch/unicore32/Kconfig
> @@ -72,6 +72,17 @@ source "kernel/Kconfig.freezer"
>
> menu "System Type"
>
> +config UNICORE32_OLDABI
> + bool "Allow old ABI binaries to run with this kernel"
> + default y
> + help
> + This option preserves the old syscall interface instead of the
> + asm-generic one. It also provides a compatibility layer to
> + intercept syscalls that have structure arguments which layout
> + in memory differs between the asm-generic ABI and this old one.
> +
> + If in doubt, say Y.
> +
> config MMU
> def_bool y
>
> --
> 2.0.0.GIT
>
prev parent reply other threads:[~2014-09-15 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 6:41 gxt
2014-09-12 6:41 ` [PATCH 2/4] unicore32-oldabi: add stat.h support for UNICORE32_OLDABI gxt
2014-09-12 6:41 ` [PATCH 3/4] unicore32-oldabi: add sigcontext.h " gxt
2014-09-12 6:41 ` [PATCH 4/4] unicore32-oldabi: add oldabi syscall interface gxt
2014-09-15 20:08 ` Guenter Roeck [this message]
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=20140915200820.GD18175@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gang.chen.5i5j@gmail.com \
--cc=gxt@mprc.pku.edu.cn \
--cc=gxt@pku.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=qinrui@pku.edu.cn \
/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