On Mon, Nov 08, 2010 at 08:23:20AM -0600, Garcia, Jaime wrote:
> 
> From: [email protected] [[email protected]] On Behalf Of 
> Víctor M. Jáquez L. [[email protected]]
> Sent: Sunday, November 07, 2010 3:44 PM
> To: [email protected]
> Subject: [MeeGo-dev] meego in the pandaboard
> 
> >I found that there is a wiki page for this topic [1], which provides a
> >kick-start file for generating the file system, which is more than enough as 
> >a
> >starting point.
> >
> 
> we now have a more recent kickstart file, just testing to release it to 
> community
> 
> >Nevertheless, the kernel did not work for me. Neither the boot.src provides
> >
> >the correct kernel parameters for the video subsystem. Hence, I borrowed what
> >currently works: the x-loader, u-boot and kernel of the Ubuntu Maverick
> >Meerkat for the Panda.
> 
> Sure, for now it looks like the current kernel in wiki only gives you a
> prompt shell, we're updating our wiki to point to the kernel that actually
> works!
> 
> >For the x-loader and the u-boot I just copied the binaries from the Ubuntu
> >SD. The boot.src I got rid of the initrd fanciness. And for the kernel, I
> >grabbed the latest Ubuntu’s kernel from its git repository and using the
> >config file also from the SD.
> >
> >My first approach was to have GLX/EGL through the SGX kernel module, which
> >also comes in the Ubuntu image. You can find the kernel module and the
> >proprietary libraries in the OMAP4 PPA [3].
> >
> >This approach failed though: The Meego’s compositor (mcompositor) could not
> >render correctly in both monitors where I tested the result.
> 
> right now we are actually working to bring up GFX

Great! Is there a place where I can grab the latest sources/binaries?

> 
> >So, my alternative approach was get rid of the compositor and launch directly
> >the duihome, the window manager. In order to do that, you must change the 
> >file
> >/etc/sysconfig/uxlaunch, with
> >
> >[snip]
> >-session=/usr/bin/mcompositor
> >+session= /usr/bin/duihome -software -show-cursor
> >[snip]
> >
> >The -software parameter request to use software rendering, not
> >accelerated. The -show-cursor requests for a mouse pointer. Those options are
> >consumed by meegotouch library. Nevertheless, each application must be
> >launched explicitly with them.
> >
> >In order to circumvent this issue, there is already an environment variable
> >for the -software: M_USE_SOFTWARE_RENDERING=1. But for the -show-cursor there
> >is none. Although it is not difficult to implement [4].
> >
> >Et voilà, we have a singing & dancing Meego environment. But still, the UI
> >transitions are really missed.
> 
> we currently going to release a more recent kickstart file (for today) that
> takes care of this configurations, so no more modifications "by hand" needed

That sounds wonderful too, but do you have some repository for it? I think
that my clone repository in gitorious is the right path rather than a file in
the meego's wiki.

> 
> >Next step: Syslink, DOMX and GStreamer.
> 
> It will be great if you can contribute and help, keep going ;)

I'd love to but how? I won't like to duplicate efforts.


vmjl

> 
> >vmjl
> >
> >1.http://wiki.meego.com/ARM/OMAP4_Panda
> >2. http://gitorious.org/~vjaquez/meego-os-base/vjaquez-image-configurations
> >3. https://launchpad.net/~tiomap-dev/+archive/release
> >4. http://people.igalia.com/vjaquez/patches/meegotouch.patch
> 
> Regards,
> Jaime Garcia
> 
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to