Re: [PATCH 1/4] unicore32-oldabi: add CONFIG_UNICORE32_OLDABI for distinguishing two ABIs
From: Guenter Roeck
Date: Mon Sep 15 2014 - 16:09:16 EST
On Fri, Sep 12, 2014 at 02:41:43PM +0800, gxt@xxxxxxxxxxxxxxx wrote:
> From: Guan Xuetao <gxt@xxxxxxxxxxxxxxx>
>
> Signed-off-by: Guan Xuetao <gxt@xxxxxxxxxxxxxxx>
> Signed-off-by: Qin Rui <qinrui@xxxxxxxxxx>
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@xxxxxxxxxxxx>
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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/