All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shin-ichiro KAWASAKI <kawasaki@juno.dti.ne.jp>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh-sci: Extend sh-sci driver with early console V2
Date: Sun, 25 Apr 2010 12:30:09 +0000	[thread overview]
Message-ID: <4BD435D1.3070000@juno.dti.ne.jp> (raw)
In-Reply-To: <20091214102442.13038.43809.sendpatchset@rxone.opensource.se>

Hi, Magnus-san, and Alex-san,

Thank you very much for your guides.
Setting "CONFIG_SERIAL_SH_SCI_NR_UARTS=2" solved my problem fully.
I find no qemu crash, and happy to see login prompt again.

I tried out these two option with real R2D+ boards and recent sh-2.6 git.
   CONFIG_SERIAL_SH_SCI_NR_UARTS=1  ... no serial output
   CONFIG_SERIAL_SH_SCI_NR_UARTS=2  ... kernel boot log printed in serial output

I hope the patch applied soon :)

Best Regards,
Shin-ichiro KAWASAKI


(2010/04/21 17:30), Magnus Damm wrote:
> Hey Kawasaki-san,
>
> 2010/4/11 Shin-ichiro KAWASAKI<kawasaki@juno.dti.ne.jp>:
>> Hello Magnus,
>>
>> 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.
>
>> With the patch, qemu-sh serial console doesn't work.
>> The emulated device is r2d+.
>>
>>   - no earlyprintk option
>>   ... Qemu carshes with assertion. No kernel boot log printed.
>>       I guess it touches sh-sci.0 registers, which qemu doesn't support.
>
> Hm, I'm not sure why this happens. Did you update the kernel command
> line to use ttySC1?
>
> This commit in linux-2.6 git may be useful:
>
>   cd5f107628ab89c5dec5ad923f1c27f4cba41972
>
>>   - earlyprintk=sh-sci.1
>>   ... Qemu boots up with kernel boot log output,
>>       but the log message stops with
>>       "turn off boot console early_ttySC0' message.
>>       No login prompt appears.
>>   - earlyprintk=sh-sci.1,115200,keep
>>   ... The message "turn off boots up ..." disappears, but no
>>       login prompt appears.
>
> I think this is because CONFIG_SERIAL_SH_SCI_NR_UARTS is set to 1. Or
> perhaps is your user space still using ttySC0 instead of ttySC1?
>
> Does updating CONFIG_SERIAL_SH_SCI_NR_UARTS to 2 solve your issue?
>
> Thanks for the report and sorry about the breakage.
>
> / magnus
>


  parent reply	other threads:[~2010-04-25 12:30 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
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 [this message]
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=4BD435D1.3070000@juno.dti.ne.jp \
    --to=kawasaki@juno.dti.ne.jp \
    --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 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.