u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Tim Harvey <tharvey@gateworks.com>
To: Anatolij Gustschin <agust@denx.de>
Cc: Fabio Estevam <festevam@gmail.com>, u-boot <u-boot@lists.denx.de>,
	 Stefano Babic <sbabic@denx.de>
Subject: Re: imx6 DM_VIDEObroken
Date: Thu, 7 Oct 2021 12:50:04 -0700	[thread overview]
Message-ID: <CAJ+vNU37RfFB_sLK+EXyK18E4J8t2EoNsbDmt7nkaVLmrWhNkw@mail.gmail.com> (raw)
In-Reply-To: <20211004154804.6fc1a7f2@crub>

On Mon, Oct 4, 2021 at 6:48 AM Anatolij Gustschin <agust@denx.de> wrote:
>
> On Wed, 29 Sep 2021 09:33:18 -0700
> Tim Harvey tharvey@gateworks.com wrote:
> ...
> > One last question on this. I have never used U-Boot vidconsole before.
> > It does work if I 'setenv stdout serial,videconsole' but if I saveenv
> > and reboot vidconsole is not enabled. Should I expect it to be or is
> > it expected that if you want vidconsole you need to do a setenv in
> > preboot?
>
> if you have
> CONFIG_CONSOLE_MUX=y
> CONFIG_SYS_CONSOLE_IS_IN_ENV=y
>
> and
> # CONFIG_SYS_CONSOLE_OVERWRITE_ROUTINE is not set
>
> then vidconsole should be enabled.

Anatolij,

That is my configuration yet vidconsole does not enable until I
'setenv stdout serial,vidconsole':
Ventana > print stdout
stdout=serial,vidconsole
^^^ see splash, yet no vidconsole
Ventana > setenv stdout serial,vidconsole
^^^ now I see vidconsole

Do you perhaps have another board to check this behavior with on master?

Best regards,

Tim

  reply	other threads:[~2021-10-07 19:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28  0:25 imx6 DM_VIDEObroken Tim Harvey
2021-09-28 12:55 ` Anatolij Gustschin
2021-09-28 17:00   ` Tim Harvey
2021-09-29  1:51     ` Fabio Estevam
2021-09-29 15:55       ` Tim Harvey
2021-09-29 16:33         ` Tim Harvey
2021-10-04 13:48           ` Anatolij Gustschin
2021-10-07 19:50             ` Tim Harvey [this message]
2021-10-07 21:55               ` Anatolij Gustschin

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=CAJ+vNU37RfFB_sLK+EXyK18E4J8t2EoNsbDmt7nkaVLmrWhNkw@mail.gmail.com \
    --to=tharvey@gateworks.com \
    --cc=agust@denx.de \
    --cc=festevam@gmail.com \
    --cc=sbabic@denx.de \
    --cc=u-boot@lists.denx.de \
    /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).