From: Shin-ichiro KAWASAKI <kawasaki@juno.dti.ne.jp>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-system-sh4 broken again.
Date: Tue, 11 May 2010 23:08:51 +0900 [thread overview]
Message-ID: <4BE964F3.6080907@juno.dti.ne.jp> (raw)
In-Reply-To: <4BE82AE8.3080705@aurel32.net>
Hello, Aurelian,
Thank you for clarification. I've understood the situation.
My comment is not the solution for Rob's problem.
Best Regards,
Shin-ichiro KAWASAKI
(2010/05/11 0:48), Aurelien Jarno wrote:
> Shin-ichiro KAWASAKI a écrit :
>> Hello, Rob,
>>
>> This mail might be too late, but I want to report you that I
>> encountered similar trouble.
>>
>> Using the linux kernel after the following commit, the qemu-sh
>> serial console shows no output.
>>
>> cd5f107628ab89c5dec5ad923f1c27f4cba41972
>>
>> This trouble was discussed in sh-linux ML.
>>
>> http://marc.info/?l=linux-sh&m=127183863325672&w=2
>>
>> To avoid this,
>>
>> - add "earlyprintk=sh-sci.1" to kernel command line, and
>> - modify CONFIG_SERIAL_SH_SCI_NR_UARTS valud from 1 to 2,
>>
>> in kernel configuration menu.
>>
>> I hope that this is the trouble you see.
>>
>
> The main problem here is that QEMU emulates both SCI channels as serial
> port, while the real board has one of the two channel configured as a
> SPI bus (for the RTC clock), and the other as a serial port.
>
next prev parent reply other threads:[~2010-05-11 14:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-13 7:51 [Qemu-devel] qemu-system-sh4 broken again Rob Landley
2010-03-13 8:54 ` Roy Tam
2010-03-13 10:26 ` Aurelien Jarno
2010-03-13 21:11 ` Rob Landley
2010-03-13 23:11 ` Rob Landley
2010-03-14 21:28 ` Aurelien Jarno
2010-03-15 0:08 ` Rob Landley
2010-05-10 14:42 ` Shin-ichiro KAWASAKI
2010-05-10 15:48 ` Aurelien Jarno
2010-05-11 14:08 ` Shin-ichiro KAWASAKI [this message]
2010-03-15 2:04 ` Jamie Lokier
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=4BE964F3.6080907@juno.dti.ne.jp \
--to=kawasaki@juno.dti.ne.jp \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.