public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Anatolij Gustschin <agust@denx.de>
To: "Pali Rohár" <pali@kernel.org>
Cc: Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>,
	U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH] WIP: Nokia RX-51: Convert to CONFIG_DM_VIDEO
Date: Wed, 9 Mar 2022 23:20:11 +0100	[thread overview]
Message-ID: <20220309232011.01982cec@crub> (raw)
In-Reply-To: <20220309194450.ilqjv44lx7jbkmyl@pali>

Hi Pali,

On Wed, 9 Mar 2022 20:44:50 +0100
Pali Rohár pali@kernel.org wrote:

> On Sunday 06 March 2022 11:44:22 Simon Glass wrote:
> > Hi Pali,
> > 
> > On Sun, 6 Mar 2022 at 08:25, Pali Rohár <pali@kernel.org> wrote:  
> > >
> > > On Sunday 06 March 2022 07:42:03 Simon Glass wrote:  
> > > > Yes let's go with that.  
> > >
> > > Done, I sent final version of the patch.
> > >  
> > > > > > > > > > Second thing is that CONFIG_VIDEO_LOGO is broken and does not work even it
> > > > > > > > > > is enabled in config file. I do not know why too.
> > > > > > > > > >
> > > > > > > > > > Any idea?  
> > > > > > > > >
> > > > > > > > > Not yet. There were some logo related changes recently, but if I
> > > > > > > > > remember correctly, I tested them on wandboard and nitrogen6q
> > > > > > > > > targets and with sandbox, and logo drawing worked there.  
> > > > > >
> > > > > > Can you be more specific than 'broken'? What is broken about it?  
> > > > >
> > > > > Does not work, logo is not drown on the screen.  
> > > >
> > > > See video_bmp_display()  - I wonder if the particular depth you are
> > > > using is not supported?  
> > >
> > > Depth is 16bit which should be supported.  
> > 
> > But apparently isn't , at least in this case :-)  
> 
> Yea, something is broken there.
> 
> > >  
> > > > Anyway you should be able to debug it there or
> > > > using the bmp command. The file is drivers/video/u_boot_logo.bmp  
> > >
> > > CONFIG_CMD_BMP=y is broken too. When I enable it then U-Boot freeze
> > > after the line 'Loading Environment from <NULL>... OK'.  
> > 
> > OK I'm not sure why, but please investigate if you have time.  
> 
> I have looked at it and do not know. But probably it is because I
> somehow have not caught how this new video code works...
> 
> Anyway, I sent documentation update how to run u-boot for n900 in qemu:
> https://patchwork.ozlabs.org/project/uboot/patch/20220308175956.4522-1-pali@kernel.org/
> 
> So it could help other people to look at issues which do not work
> correctly in n900's u-boot without need to have n900 hardware.

I've tested your v2 patches, and logo drawing works, but the logo
appears for short time. Then it is later overwritten by boot menu.

--
Anatolij

  reply	other threads:[~2022-03-09 22:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 20:42 [PATCH] WIP: Nokia RX-51: Convert to CONFIG_DM_VIDEO Pali Rohár
2022-02-17  8:53 ` Anatolij Gustschin
2022-02-17 12:20   ` Pali Rohár
2022-03-06 11:51     ` Pali Rohár
2022-03-06 12:51       ` Simon Glass
2022-03-06 14:17         ` Pali Rohár
2022-03-06 14:42           ` Simon Glass
2022-03-06 15:25             ` Pali Rohár
2022-03-06 18:44               ` Simon Glass
2022-03-09 19:44                 ` Pali Rohár
2022-03-09 22:20                   ` Anatolij Gustschin [this message]
2022-03-11 18:58                     ` Pali Rohár
2022-03-12  5:02                       ` Simon Glass
2022-03-13 11:06                         ` Pali Rohár
2022-03-06 15:08 ` [PATCH] " Pali Rohár
2022-03-06 18:43   ` Simon Glass
2022-03-09 19:37     ` Pali Rohár
2022-03-09 19:46 ` [PATCH v2 1/2] video: Allow drivers to allocate the frame buffer themselves Pali Rohár
2022-03-09 19:46   ` [PATCH v2 2/2] Nokia RX-51: Convert to CONFIG_DM_VIDEO Pali Rohár
2022-03-14 22:42     ` Anatolij Gustschin
2022-03-12  2:43   ` [PATCH v2 1/2] video: Allow drivers to allocate the frame buffer themselves Simon Glass
2022-03-14 22:41   ` 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=20220309232011.01982cec@crub \
    --to=agust@denx.de \
    --cc=pali@kernel.org \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --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