From: Magnus Damm <magnus.damm@gmail.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh-sci: Extend sh-sci driver with early console V2
Date: Thu, 22 Apr 2010 06:11:41 +0000 [thread overview]
Message-ID: <w2vaec7e5c31004212311i860c8699vc646d436967e94d1@mail.gmail.com> (raw)
In-Reply-To: <20091214102442.13038.43809.sendpatchset@rxone.opensource.se>
Hi Alexandre,
On Thu, Apr 22, 2010 at 2:54 PM, Alexandre Courbot
<alex@dcl.info.waseda.ac.jp> wrote:
> Hello everybody,
>
>> > I'm in trouble with qemu-sh serial console. Don't you have any
>> > guide on this trouble?
>>
>> Yes, I think the defconfig is missing one thing. Please try setting
>> CONFIG_SERIAL_SH_SCI_NR_UARTS=2. See below.
>
> Indeed, I ran into the same problem as Kawasaki-san and got it fixed
> by setting CONFIG_SERIAL_SH_SCI_NR_UARTS to 2 instead of 1. With this
> value, I am able to boot correctly by using the "earlyprintk=sh-sci.1
> console=ttySC1" kernel parameters. FYI, my qemu command-line is:
>
> qemu-system-sh4 -M r2d -kernel arch/sh/boot/zImage -serial null
> -serial stdio -append "earlyprintk=sh-sci.1 console=ttySC1"
Thanks for sharing this information.
> Also, the r2dplus configuration file sets
> CONFIG_SERIAL_SH_SCI_NR_UARTS to 1 currently - here is a patch that
> fixes that. It is possible that other targets need this.
Cool, thanks. It's very similar to the patch I just posted. =)
> We are also trying to get the latest Linux to run on the SH2007
> platform, and since the new serial driver boot fails during SCIF
> intialization. I have attached a boot log of what is sent to the
> serial line. The output gets cut right in the middle of displaying
> status for sh-sci.1. Any clue on that issue would be greatly
> appreciated.
Is the SH2007 board based on sh7780? Perhaps it's a clock issue.
Cheers,
/ magnus
next prev parent reply other threads:[~2010-04-22 6:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 10:24 [PATCH] sh-sci: Extend sh-sci driver with early console V2 Magnus Damm
2009-12-15 3:37 ` Paul Mundt
2010-04-11 7:40 ` Shin-ichiro KAWASAKI
2010-04-21 8:30 ` Magnus Damm
2010-04-22 5:54 ` Alexandre Courbot
2010-04-22 6:11 ` Magnus Damm [this message]
2010-04-22 6:22 ` Alexandre Courbot
2010-04-22 6:30 ` Paul Mundt
2010-04-22 7:09 ` Magnus Damm
2010-04-23 6:25 ` Alexandre Courbot
2010-04-23 7:26 ` Paul Mundt
2010-04-23 11:16 ` Alexandre Courbot
2010-04-25 12:30 ` Shin-ichiro KAWASAKI
2010-04-26 7:03 ` Paul Mundt
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=w2vaec7e5c31004212311i860c8699vc646d436967e94d1@mail.gmail.com \
--to=magnus.damm@gmail.com \
--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).