Linux-Rockchip Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Anatolij Gustschin <agust-ynQEQJNshbs@public.gmane.org>
To: Jagan Teki <jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
Cc: U-Boot-Denx <u-boot-0aAXYlwwYIKGBzrmiIFOJg@public.gmane.org>,
	Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
	Philipp Tomsich
	<philipp.tomsich-SN7IsUiht6C/RdPyistoZJqQE7yCjDx5@public.gmane.org>,
	Kever Yang <kever.yang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [U-Boot] rk3288: HDMI out causing boot hang
Date: Fri, 13 Sep 2019 16:01:29 +0200	[thread overview]
Message-ID: <20190913160129.0cc8bc99@crub> (raw)
In-Reply-To: <CAMty3ZDo6Hk9swGcaZ0RNC-4KeQ=EJS9gu_-+ewmM618GHhO+w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi Jagan,

On Fri, 13 Sep 2019 08:19:47 +0530
Jagan Teki jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org wrote:
...
> Any inputs?

Try to input "setenv stdout serial" command on the serial console.
There might be a chance that stdout/stdin has switched to the
video console and the output proceeds there. If the HDMI display
shows nothing, it appears like a hang.
 
--
Anatolij

  parent reply	other threads:[~2019-09-13 14:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-13  2:49 rk3288: HDMI out causing boot hang Jagan Teki
     [not found] ` <CAMty3ZDo6Hk9swGcaZ0RNC-4KeQ=EJS9gu_-+ewmM618GHhO+w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-09-13  3:21   ` [U-Boot] " Tony McKahan
2019-09-13 14:01   ` Anatolij Gustschin [this message]
2019-09-13 14:02     ` Michael Nazzareno Trimarchi
2019-09-13 15:02       ` Michael Nazzareno Trimarchi
2019-09-13 15:05         ` Michael Nazzareno Trimarchi
2019-09-13 21:21     ` [U-Boot] " Jagan Teki

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=20190913160129.0cc8bc99@crub \
    --to=agust-ynqeqjnshbs@public.gmane.org \
    --cc=jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org \
    --cc=kever.yang-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
    --cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=philipp.tomsich-SN7IsUiht6C/RdPyistoZJqQE7yCjDx5@public.gmane.org \
    --cc=sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
    --cc=u-boot-0aAXYlwwYIKGBzrmiIFOJg@public.gmane.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