From: "Pali Rohár" <pali@kernel.org>
To: Simon Glass <sjg@chromium.org>
Cc: Anatolij Gustschin <agust@denx.de>, 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: Sun, 6 Mar 2022 16:25:40 +0100 [thread overview]
Message-ID: <20220306152540.nom7dernmwqctbdd@pali> (raw)
In-Reply-To: <CAPnjgZ268NWJqz4p8Eg0KkZ32p=MPCATMUw8uPCbHv06EyZc5Q@mail.gmail.com>
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.
> 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'.
next prev parent reply other threads:[~2022-03-06 15:25 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 [this message]
2022-03-06 18:44 ` Simon Glass
2022-03-09 19:44 ` Pali Rohár
2022-03-09 22:20 ` Anatolij Gustschin
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=20220306152540.nom7dernmwqctbdd@pali \
--to=pali@kernel.org \
--cc=agust@denx.de \
--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