[meta-intel] Crown Bay : EMGD CED, splash screens and Yocto work flow

[Kamble, Nitin A]

> -----Original Message-----
> From: Chad Bishop [mailto:Chad.Bishop at ravenind.com]
> Sent: Tuesday, November 26, 2013 4:33 PM
> To: meta-intel at yoctoproject.org
> Cc: Kamble, Nitin A
> Subject: Crown Bay : EMGD CED, splash screens and Yocto work flow
> 
> Hello meta-intel team,
> 
> I have run into the issue that was summarized here :
> 
> https://lists.yoctoproject.org/pipermail/meta-intel/2013-
> January/000247.html
> 
> > I find that there is no FB device at boot time and hence no splash
> > screen. I will put the VESA FB config for emgd based devices back in my
> commits to restore the splash screen.
> 
> > Thanks,
> > Nitin
> 
> We are trying to prepare a product for market and would like to make the
> boot process a bit prettier for consumer (farmer) consumption.
> 
> No fb0 when EMGD is configured is proving troublesome.  We use EMGD for
> accelerated OpenGL features.
> 
> We have used Intel EMGD CED to configure driver stacks for other Linux
> distros as well as windows.  We can use it to generate a package that includes
> a splash screen.
> 
> My question to you is twofold :
> 
> First, should we be using CED to incorporate the splash screen when using
> EMGD or is there a prescribed method to do it with Yocto and the meta-intel
> layer.
> 


1st I am surprised by this. The splash screen is already enabled for crownbay BSPs.
So you should be seeing the splash screen with the default crownbay BSPs.

And yes it is possible to customize the splash screen as per your needs.
Check the psplash recipe and it's sources for more details.

> Second, if we are to use CED, how do you envision the resulting package
> being shoehorned into a Yocto build?

The psplash should give you what you want. So I think there is no need to find a new
solution here.

Thanks,
Nitin

> 
> Thank you for your time,
> Chad Bishop
> Raven Industries, Inc.
> 
> 
> 
> 
> 
> 
> This message and attachment(s) may contain confidential and/or privileged
> information.  Access, disclosure, copying, distribution or reliance on any
> content of this message by anyone other than the addressee is prohibited.  If
> received in error, please advise the sender immediately by reply e-mail and
> delete this message.
>