From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-sh@vger.kernel.org
Subject: Re: QEMU serial still broken in -rc1.
Date: Thu, 15 Jun 2017 06:26:08 +0000 [thread overview]
Message-ID: <CAMuHMdUSOkL0Kn=3XitnnBGKvw-XsTeLi9uCSSpmJ_qR6arieQ@mail.gmail.com> (raw)
In-Reply-To: <cdec4797-afe1-11f8-f926-fb5d356da625@landley.net>
Hi Rob,
On Thu, Jun 15, 2017 at 3:07 AM, Rob Landley <rob@landley.net> wrote:
> On 06/14/2017 08:48 AM, John Paul Adrian Glaubitz wrote:
>> On Sun, May 14, 2017 at 09:46:07PM -0500, Rob Landley wrote:
>>> I refer to the previous thread, which is still the case:
>>>
>>> http://www.spinics.net/lists/linux-sh/msg51190.html
>>>
>>> I poked at QEMU's internals to see if there was an easy way to fiddle
>>> with stuff, but A) ttySC1 appears to be the only serial type the board
>>> emulates, B) the ttySC0 instance is broken, dunno why.
>>
>> I gave it a try myself now and I can't get the emulated machine to
>> boot or show any output over the serial console.
>>
>> It hangs here:
>>
>> root@nofan:~/sh4-system> qemu-system-sh4 -M r2d -m 1000M -drive file=sh4-system.img,format=qcow2 -nographic -append "root=/dev/sda1 rw console=ttySC0 earlyprintk=sh-sci.1" -kernel vmlinux-3.18.0-trunk-sh7751r
>> long read to SH7750_WCR1_A7 (0x000000001f800008) ignored
>> long read to SH7750_WCR2_A7 (0x000000001f80000c) ignored
>> long read to SH7750_WCR3_A7 (0x000000001f800010) ignored
>> long read to SH7750_MCR_A7 (0x000000001f800014) ignored
>> long read to SH7750_MCR_A7 (0x000000001f800014) ignored
>>
>> Any ideas?
>
> By default qemu-system-sh4 outputs to the broken first serial port
> (which Linux apparently has no driver for) instead of the second serial
> port that Linux does have a driver for. I have no idea why it does that,
> but you have to add extra command line options to work around it:
The first serial port is a SCI, which should be supported by the sh-sci
driver, too.
Perhaps the issue is that using the first port as a serial console depends
on the bootloader initializing it?
Does it work as a normal serial port from userspace?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2017-06-15 6:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 2:46 QEMU serial still broken in -rc1 Rob Landley
2017-05-15 5:11 ` John Paul Adrian Glaubitz
2017-05-15 5:13 ` John Paul Adrian Glaubitz
2017-05-15 18:11 ` Rob Landley
2017-05-15 18:16 ` Rob Landley
2017-05-15 18:17 ` Rob Landley
2017-06-14 13:48 ` John Paul Adrian Glaubitz
2017-06-14 14:03 ` John Paul Adrian Glaubitz
2017-06-15 1:07 ` Rob Landley
2017-06-15 6:26 ` Geert Uytterhoeven [this message]
2017-06-15 18:00 ` Rob Landley
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='CAMuHMdUSOkL0Kn=3XitnnBGKvw-XsTeLi9uCSSpmJ_qR6arieQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=linux-sh@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).