From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anatolij Gustschin <agust@denx.de>
Date: Tue, 17 Sep 2019 23:42:25 +0200
Subject: [U-Boot] [PATCH 09/17] mx6sabresd: convert to DM_VIDEO
In-Reply-To: <CAOMZO5ATT2iAXRibLcgLrxyiXijiCqy7cUOTRSkJBzF8apniGg@mail.gmail.com>
References: <20190318222947.7148-1-agust@denx.de>
 <20190318222947.7148-10-agust@denx.de>
 <CAOMZO5AdkHrthDkN8musen_=4jVN18WeiQaZHUT_W-ex+BGEbQ@mail.gmail.com>
 <20190916212138.1d269cb9@crub>
 <CAOMZO5ATT2iAXRibLcgLrxyiXijiCqy7cUOTRSkJBzF8apniGg@mail.gmail.com>
Message-ID: <20190917234225.02c84c7c@crub>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Fabio,

On Tue, 17 Sep 2019 09:32:37 -0300
Fabio Estevam festevam at gmail.com wrote:

> Hi Anatolij,
> 
> On Mon, Sep 16, 2019 at 4:21 PM Anatolij Gustschin <agust@denx.de> wrote:
> 
> > Most probably this is because there was no user of the video
> > device when booting and therefore the video driver was not
> > probed/bound. Please try do display some bitmap with bmp
> > command or try to switch to the video console by command
> > "setenv stdout vidconsole0". Then, the video device will be
> > probed and you should see the LVDS output.  
> 
> Here is what I tried:
> 
> => setenv stdout vidconsole0  
> ## Error inserting "stdout" variable, errno=22
> 
> Then I see garbage on the LVDS panel.
> 
> Any ideas as to why setting "stdout" failed?

Does "setenv stdout vidconsole" work? I think I've suggested
wrong command, sorry. "vidconsole0" is the driver instance name
for the first video console, "vidconsole" is the correct name
for console device on framebuffer.

--
Anatolij