From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=53137 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OBq8v-0003uO-BA
	for qemu-devel@nongnu.org; Tue, 11 May 2010 10:09:10 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <kawasaki@juno.dti.ne.jp>) id 1OBq8t-0002fx-LX
	for qemu-devel@nongnu.org; Tue, 11 May 2010 10:09:05 -0400
Received: from vsmtp05.dti.ne.jp ([202.216.231.140]:51423)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <kawasaki@juno.dti.ne.jp>) id 1OBq8t-0002fO-7F
	for qemu-devel@nongnu.org; Tue, 11 May 2010 10:09:03 -0400
Message-ID: <4BE964F3.6080907@juno.dti.ne.jp>
Date: Tue, 11 May 2010 23:08:51 +0900
From: Shin-ichiro KAWASAKI <kawasaki@juno.dti.ne.jp>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] qemu-system-sh4 broken again.
References: <201003130151.36065.rob@landley.net>
	<201003131711.44849.rob@landley.net>
	<20100314212832.GE2381@hall.aurel32.net>
	<201003141908.41360.rob@landley.net>
	<4BE81B39.1040101@juno.dti.ne.jp> <4BE82AE8.3080705@aurel32.net>
In-Reply-To: <4BE82AE8.3080705@aurel32.net>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: quoted-printable
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org

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 =E9crit :
>> 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=3Dlinux-sh&m=3D127183863325672&w=3D2
>>
>> To avoid this,
>>
>>     - add "earlyprintk=3Dsh-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.
>