SUPERH platform development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: Can't boot kernel v4.0-rc2 on Koelsch
Date: Wed, 11 Mar 2015 06:45:32 +0000	[thread overview]
Message-ID: <1619020.aeDtHYVxJ4@avalon> (raw)
In-Reply-To: <2263226.JPOqZgiCRj@avalon>

Hi Geert,

On Tuesday 10 March 2015 12:32:59 Geert Uytterhoeven wrote:
> On Tue, Mar 10, 2015 at 10:03 AM, Cao Minh Hiep <cm-hiep@jinso.co.jp> wrote:
> > On 2015年03月10日 17:05, Nobuhiro Iwamatsu wrote:
> >> This is user land issue.
> >> Hiep, if you have not changed ttySCX in inittab, you will need to change.
> >> Could you check your inittab?
> >> 
> >> --- a/inittab    2015-03-10 15:01:58.986609389 +0900
> >> +++ b/inittab    2015-03-10 15:00:32.132094877 +0900
> >> @@ -28,7 +28,7 @@
> >> 
> >>   l6:6:wait:/etc/init.d/rc 6
> >>   # Normally not reached, but fallthrough in case of emergency.
> >>   z6:6:respawn:/sbin/sulogin
> >> 
> >> -SC6:12345:respawn:/sbin/getty -L 38400 ttySC6
> >> +SC0:12345:respawn:/sbin/getty -L 38400 ttySC0
> >> 
> >>   # /sbin/getty invocations for the runlevels.
> >>   #
> >>   # The "id" field MUST be the same as the last
> > 
> > There is no inittab file in Linaro userland that I am using.
> 
> I'm not familiar with the Linaro userland.
> 
> Is there any other configuration file that contains the string "ttySC6"?
> Or does the Linaro userland derive it from the kernel command line?
> If yes, perhaps there's a newer version that does look at stdout-path
> instead?
> 
> The goal of the stdout-path support was to have a better description in DT
> and automate things. So I don't think reverting the change is the proper way
> forward.
> 
> If you can't get it to work, I think we should bring it up with the DT
> people first, some of which work for Linaro.

I quite agree with that, but how should userspace know which device node in 
/dev corresponds to the console specified in stdout-path ?

-- 
Regards,

Laurent Pinchart


  parent reply	other threads:[~2015-03-11  6:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09  7:06 Can't boot kernel v4.0-rc2 on Koelsch Laurent Pinchart
2015-03-09  9:43 ` Cao Minh Hiep
2015-03-09 23:49 ` Laurent Pinchart
2015-03-10  1:14 ` Simon Horman
2015-03-10  1:53 ` Cao Minh Hiep
2015-03-10  4:14 ` Simon Horman
2015-03-10  8:05 ` Nobuhiro Iwamatsu
2015-03-10  8:38 ` Cao Minh Hiep
2015-03-10  9:03 ` Cao Minh Hiep
2015-03-10 11:32 ` Geert Uytterhoeven
2015-03-11  0:01 ` Simon Horman
2015-03-11  4:51 ` Cao Minh Hiep
2015-03-11  6:45 ` Laurent Pinchart [this message]
2015-03-11 15:56 ` Ben Hutchings

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=1619020.aeDtHYVxJ4@avalon \
    --to=laurent.pinchart@ideasonboard.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