[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] qemu-system-sh4 vs qemu-system-arm/i386 default behavio

From: Thomas Huth
Subject: Re: [Qemu-devel] qemu-system-sh4 vs qemu-system-arm/i386 default behavior
Date: Wed, 30 Nov 2016 08:33:02 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0

On 30.11.2016 02:01, Tom Rini wrote:
> Hey all,
> I'm trying to make use of the r2d platform for U-Boot testing via QEMU.
> After applying a series[1] I can use the kernel.org sh4 toolchain to get
> a u-boot.bin that runs, mostly.  I say mostly as first of all I have to
> pass "-monitor null -serial null -serial stdio -nographic" to
> qemu-system-sh4 and in that order for me to get output from U-Boot on
> the prompt.  On other platforms such as arm and vexpress or i386 and the
> 'pc' machine I do not need to do this.  Does anyone have any idea why
> this might be and where to start poking in the code to fix this?

The "-serial" parameter is related to the serial_hds[] array in the
code, so you could search for that one.

The following line in hw/sh4/r2d.c looks somewhat suspicious:

    sm501_init(address_space_mem, 0x10000000, SM501_VRAM_SIZE,
               irq[SM501], serial_hds[2]);

Why is this machine always using serial_hds[2] and not a lower index?
... Maybe the maintainer of the board (Magnus) knows the answer here...


Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]