public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add splash screen support via loading from flash
Date: Tue, 04 Jun 2013 07:30:38 -0700	[thread overview]
Message-ID: <51ADFA0E.6060603@boundarydevices.com> (raw)
In-Reply-To: <51ADF682.1040305@denx.de>

Hi Stefano,

On 06/04/2013 07:15 AM, Stefano Babic wrote:
> Hi Eric,
>
> On 04/06/2013 15:55, Eric Nelson wrote:
>> Hi Stefano,
>>
>> On 06/04/2013 06:44 AM, Stefano Babic wrote:
>>> Hi Robert,
>>>
>>> On 03/06/2013 18:34, Robert Winkler wrote:
>>>
>>>>> Which is the advantage instead of using the "preboot" variable setting
>>>>> CONFIG_PREBOOT ? It does pretty the same and you can move the whole
>>>>> script outside of board code.
>>>>
>>>> The preboot command is run too late.  It looks like it is run in
>>>> main_loop but U-Boot looks for the splash image
>>>> at the address in the splashimage variable in board_init_r ->
>>>> stdio_init -> drv_lcd_init or drv_video_init (depending on
>>>> whether you have CONFIG_LCD or CONFIG_VIDEO).
>>>
>>> You are describing a bug - then it should be fixed globally, not only
>>> for this board.
>>>
>>
>> What's the bug?
>>      - preboot being called too late, or
>
> preboot is not called too late. The behavior is correct and wanted, as
> the name says, and the variable is evaluated during the main loop before
> booting. My suggestion comes because it is possible to implement a
> splashscreen (even if the name can be misleading..), setting preboot to
> something like "nand read <address> <offset>;bmp display <address>".
> In your case (with a bmp image), it could be:
> 	"preboot=if sf probe ; then " \
> 		"sf read ${splashimage} c2000 ${splashsize} ; bmp display
> ${splashimage}; fi\0"
>
> The behavior is exactly as the subject in the patch, the delay is from
> power-on until main loop is called. It can be on some boards acceptable,
> sometimes not.
>

Gotcha. This method doesn't involve splash_screen_prepare() though.

It also will blink the display since the splash screen will paint
after the the compiled-in logo case.
	http://git.denx.de/u-boot.git/?p=u-boot.git;a=blob;f=common/lcd.c#l1085

>>      - splash_screen_prepare() being called too early
>>
>> It seems that having splash_screen_prepare() called early
>> makes sense, because stdout could be set to include VGA
>> and having access to stdout is very useful in preboot
>> commands.
>
> You mention that it does not work, and then I assume that it is a bug,
> because an image should be displayed. But again, if it does not work,
> the issue is related to the video subsystem and should be fixed there
> and not in board code - this is my point.
>

This works with Robert's latest patch, which implements 
splash_screen_prepare() for boards that use cfb_console.

It just wasn't implemented there.

Regards,


Eric

  reply	other threads:[~2013-06-04 14:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 21:03 [U-Boot] [PATCH] Add splash screen support via loading from flash Robert Winkler
2013-05-30 23:32 ` Wolfgang Denk
2013-05-31  0:01   ` Robert Winkler
2013-05-31  7:49     ` Wolfgang Denk
2013-05-31 17:50       ` Robert Winkler
2013-06-03  7:44 ` Stefano Babic
2013-06-03 16:34   ` Robert Winkler
2013-06-04 13:44     ` Stefano Babic
2013-06-04 13:55       ` Eric Nelson
2013-06-04 14:15         ` Stefano Babic
2013-06-04 14:30           ` Eric Nelson [this message]
2013-06-04 14:57             ` Robert Winkler
2013-06-04 15:08               ` Stefano Babic
2013-06-04 15:05             ` Stefano Babic

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=51ADFA0E.6060603@boundarydevices.com \
    --to=eric.nelson@boundarydevices.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