[U-Boot] IMX51 EVK Splash Screen

Hi folks -

I had posted last week.  I was able to get basic Splash Screen going on EVK,
through using patches I found from googling around.  At the end of this email,
the patch set that shows the differences from the U-Boot I pulled on
12/24/2010.  I am not sure I have the right patch set, but in this case,
what I have does seem to work; U-Boot does output to LCD display on the
second Display Interface.

Through some of the archives, this one specifically:

http://www.mail-archive.com/u-boot@lists.denx.de/msg41664.html

There seems to have been a discussion on lcd_setmem().  Has this been
resolved, and I missed it?  You'll see from patch set that I just put a
very large buffer in place (hard coded hack).  U-Boot hung on boot before
I put this in, and based on what I see on mailing list, this seems to be
an issue of not having the display information available early on in boot.

At any rate, I got it to boot, and see that the LCD shows display on
startup.  Yet, I lose the console on this; the serial port is read, but
the output goes to LCD.

I have still not displayed a bit map image, but with IPU working, not
horribly concerned.

In an ideal world, what I would like is to not loose the console.  I want
stdin/stdout to remain on serial port, while I toss a bit map out on LCD.
Any comments on how to do this?  End game is that I toss a splash screen
up on LCD on EVK, while having U-Boot information still on the console.

So, a couple of things:

1. Do I have correct patch work for this version of U-Boot, or is there a
newer version of U-Boot to pull?  I pulled both mainline and IMX tree
yesterday, don't see the MX51 EVK in them.

2. How to configure so that I get console while LCD is available for display.

3. What is current status on lcd_setmem() thing.

If this patch set that I have is workable, then I am going to move forward
to put in support for DVI interface on EVK, and figure out how to use
U-Boot Environment Variables to specify which DIU to use.

I might have missed a few things along the way folks; I am not the sharpest
tool in the shed.  Please let me know if I missed patch sets on lcd_setmem(),
and help me understand how to make sure console works with Splash Screen.

Thanks,

tom


 	struct mxcfb_info *mxcfbi;
@@ -550,11 +550,14 @@
 		mxcfbi->blank = FB_BLANK_POWERDOWN;
 	}

-	mxcfbi->ipu_di = 0;
+	mxcfbi->ipu_di = ipu_di;

 	ipu_disp_set_global_alpha(mxcfbi->ipu_ch, 1, 0x80);
 	ipu_disp_set_color_key(mxcfbi->ipu_ch, 0, 0);
-	strcpy(fbi->fix.id, "DISP3 BG");
+        if (ipu_di == 0)
+                strcpy(fbi->fix.id, "DISP3 BG");
+        else if (ipu_di == 1)
+                strcpy(fbi->fix.id, "DISP3 BG - DI1");

 	g_dp_in_use = 1;

@@ -625,9 +628,10 @@
 	memset(lcdbase, 0, mem_len);
 }

-int mx51_fb_init(struct fb_videomode *mode)
+int mx51_fb_init(struct fb_videomode *mode, u32 ipu_di, u32 bppix)
 {
 	int ret;
+	uint32_t pixfmt = 0;

 	ret = ipu_probe();
 	if (ret)
@@ -635,8 +639,24 @@

 	lcd_base += 56;

+        switch (bppix) {
+        case 32:
+                pixfmt = IPU_PIX_FMT_BGR32;
+                break;
+        case 24:
+                pixfmt = IPU_PIX_FMT_BGR24;
+                break;
+        case 18:
+                pixfmt = IPU_PIX_FMT_RGB666;
+                break;
+        case 16:
+                pixfmt = IPU_PIX_FMT_RGB565;
+                break;
+        }
+
+
 	debug("Framebuffer at 0x%x\n", (unsigned int)lcd_base);
-	ret = mxcfb_probe(IPU_PIX_FMT_RGB666, mode);
+	ret = mxcfb_probe(pixfmt, mode, ipu_di);

 	return ret;
 }

On 01/20/2011 03:06 AM, Thomas Besemer wrote:
> Hi folks -
> 
> I had posted last week.  I was able to get basic Splash Screen going on EVK,
> through using patches I found from googling around.  At the end of this email,
> the patch set that shows the differences from the U-Boot I pulled on
> 12/24/2010.  I am not sure I have the right patch set, but in this case,
> what I have does seem to work; U-Boot does output to LCD display on the
> second Display Interface.

There is no correct patchset. As I already stated, patches sent
sometimes ago to ML (and that you reuse) require some rework to be
merged into the mainline.

> There seems to have been a discussion on lcd_setmem().  Has this been
> resolved, and I missed it?

No, someone should fix it. The result of the discussion suggested by
Wolfgang is to use the same interface Linux uses, that is with a
video-mode=" variable with something such as 1024x768@60. U-Boot has
already a videomodes.c, but it uses an ancient syntax for videomode (see
the code). Feel free to fix it.

>  You'll see from patch set that I just put a
> very large buffer in place (hard coded hack).

Of course it can work, but this cannot go to mainline...

>  U-Boot hung on boot before
> I put this in, and based on what I see on mailing list, this seems to be
> an issue of not having the display information available early on in boot.

Right. This is an open issue.

> At any rate, I got it to boot, and see that the LCD shows display on
> startup.  Yet, I lose the console on this; the serial port is read, but
> the output goes to LCD.

Fine.

> In an ideal world, what I would like is to not loose the console.

Console remains on UART if you do not change the behavior.

>  I want
> stdin/stdout to remain on serial port, while I toss a bit map out on LCD.
> Any comments on how to do this?  End game is that I toss a splash screen
> up on LCD on EVK, while having U-Boot information still on the console.

This is already foreseen. If you checked in IPU code, there is an
overwrite function set for this purpose. You must set
CONFIG_SYS_CONSOLE_OVERWRITE_ROUTINE. Check the setup in the vision2 board.

> 
> So, a couple of things:
> 
> 1. Do I have correct patch work for this version of U-Boot, or is there a
> newer version of U-Boot to pull?  I pulled both mainline and IMX tree
> yesterday, don't see the MX51 EVK in them.

As I stated previously, the patch adding splashscreen to the mx51evk
board need reworking.

> 2. How to configure so that I get console while LCD is available for display.

See my answer before

> 
> 3. What is current status on lcd_setmem() thing.

Awaiting for patches. Do you think you can provide them ?

> I might have missed a few things along the way folks; I am not the sharpest
> tool in the shed.  Please let me know if I missed patch sets on lcd_setmem(),
> and help me understand how to make sure console works with Splash Screen.

Regarding lcd_setmem() there is some clear statements. IMHO I like
Wolfgang's proposal, because we should not reinvent the wheel.

Best regards,
Stefano Babic

On Thursday 20 January 2011 09:07:53 Stefano Babic wrote:
> On 01/20/2011 03:06 AM, Thomas Besemer wrote:
> > Hi folks -
> > 
> > I had posted last week.  I was able to get basic Splash Screen going on
> > EVK, through using patches I found from googling around.  At the end of
> > this email, the patch set that shows the differences from the U-Boot I
> > pulled on 12/24/2010.  I am not sure I have the right patch set, but in
> > this case, what I have does seem to work; U-Boot does output to LCD
> > display on the second Display Interface.
> 
> There is no correct patchset. As I already stated, patches sent
> sometimes ago to ML (and that you reuse) require some rework to be
> merged into the mainline.
> 
> > There seems to have been a discussion on lcd_setmem().  Has this been
> > resolved, and I missed it?
> 
> No, someone should fix it. The result of the discussion suggested by
> Wolfgang is to use the same interface Linux uses, that is with a
> video-mode=" variable with something such as 1024x768@60. U-Boot has
> already a videomodes.c, but it uses an ancient syntax for videomode (see
> the code). Feel free to fix it.
> 
> >  You'll see from patch set that I just put a
> > 
> > very large buffer in place (hard coded hack).
> 
> Of course it can work, but this cannot go to mainline...
> 
> >  U-Boot hung on boot before
> > 
> > I put this in, and based on what I see on mailing list, this seems to be
> > an issue of not having the display information available early on in
> > boot.
> 
> Right. This is an open issue.
> 
> > At any rate, I got it to boot, and see that the LCD shows display on
> > startup.  Yet, I lose the console on this; the serial port is read, but
> > the output goes to LCD.
> 
> Fine.
> 
> > In an ideal world, what I would like is to not loose the console.
> 
> Console remains on UART if you do not change the behavior.
> 
> >  I want
> > 
> > stdin/stdout to remain on serial port, while I toss a bit map out on LCD.
> > Any comments on how to do this?  End game is that I toss a splash screen
> > up on LCD on EVK, while having U-Boot information still on the console.
> 
> This is already foreseen. If you checked in IPU code, there is an
> overwrite function set for this purpose. You must set
> CONFIG_SYS_CONSOLE_OVERWRITE_ROUTINE. Check the setup in the vision2 board.
> 
> > So, a couple of things:
> > 
> > 1. Do I have correct patch work for this version of U-Boot, or is there a
> > newer version of U-Boot to pull?  I pulled both mainline and IMX tree
> > yesterday, don't see the MX51 EVK in them.
> 
> As I stated previously, the patch adding splashscreen to the mx51evk
> board need reworking.
> 
> > 2. How to configure so that I get console while LCD is available for
> > display.
> 
> See my answer before
> 
> > 3. What is current status on lcd_setmem() thing.
> 
> Awaiting for patches. Do you think you can provide them ?
> 
> > I might have missed a few things along the way folks; I am not the
> > sharpest tool in the shed.  Please let me know if I missed patch sets on
> > lcd_setmem(), and help me understand how to make sure console works with
> > Splash Screen.
> 
> Regarding lcd_setmem() there is some clear statements. IMHO I like
> Wolfgang's proposal, because we should not reinvent the wheel.
> 
> Best regards,
> Stefano Babic

Hey guys, any update on this matter ? I'm quite interested :)

On 02/26/2011 07:32 PM, Marek Vasut wrote:

> Hey guys, any update on this matter ? I'm quite interested :)

On my side I am not currently working on this issue...

Best regards,
Stefano Babic

On Sun, Feb 27, 2011 at 5:41 AM, Stefano Babic <sbabic@denx.de> wrote:
>
> On 02/26/2011 07:32 PM, Marek Vasut wrote:
>
> > Hey guys, any update on this matter ? I'm quite interested :)
>
> On my side I am not currently working on this issue...
>
> Best regards,
> Stefano Babic
>

On my end, I had to go back to the FSL SDK version of U-Boot.  Reason
is that they
have an extensive patch set that is not in mainstream U-Boot.  I ran
into some issues
using current U-Boot, such as a slower boot time, but did not investigate.

If I get a chance in next month or so, I am going to migrate all FSL
SDK U-Boot patches
to the top of the U-Boot tree, and stabilize.

I have not back ported the Splash Screen stuff to the SDK version of U-Boot.

In an ideal world, FSL will start working with current U-Boot, and
post their patch sets back
to mailing list.  Would make life easier for all of us.

tom