Openembedded for Dabba2 (Atom platform)The Dabba2 OE adoptation is built on the earlier work done for Dabba1. A local overlay is created and a base OE snapshot is used, in this case snapshot is from early May, 2010.
First stop is at creating the machine configuration for the platform D510MO.
In tune-atom.inc defined
TARGET_CC_ARCH = "-march=atom -mtune=atom"
This, of course, assumes a 4.5.x gcc compiler.
Then following the OpenMoko task/image styling, would like to chase the Dabba2 target with the following image milestones. Each of the milestone builds ont the previous one, so that we get the right context to build and test the new functionality.
- dabba2-minimal-image : A basic kernel and a busybox login prompt
- dabba2-initrd-image : Initrd setup for bootsplash
- dabba2-ivtv-image : ivtv driver testing with mplayer
- dabba2-db-image : MySQL
- dabba2-x11-image : X with the matchbox window manager
- dabba2-mythtv-image : Basic mythtv installation
Openembedded for Dabba1 (Via platform)An embedded distirbution will bring greater robustness to a project like Dabba1 and OpenEmbedded is mature enough to build a distribution for a complex application like mythtv. Though I had prior experience in dealing with buildroot (SnapGear) , DSLinux , OpenEmbedded does have a steep learning curve.
The Dabba1 Via platform looks and feels more like an embedded platform: headless, no easy access other than the network and limited storage/RAM and pathetic CPU power. One problem with natively hosted distribution like gentoo or RH for Dabba1 is that any root file system corruption or major system-wide misconfiguration can render the system not bootable. Of course, backups should be taken and can be restore, but that is not the same as simply re-generating the distribution.
The OE allows a local overlay to be created and the components defined in the overlay can override the ones in the main meta-distribution. So in the local overlay we will maintain the top-level components needed for Dabba1 and tweak them for our purpose. The local overlay is version controlled.Following are the overlay members for Dabba1:
For the initrd/bootsplash:
WinTV PVR 350 support:
Making life little easy is the fact that the VIA epia architecture is already supported by the OE :
machine (generic) ==> epia.conf
gcc tuning ==> conf/machine/include/tune-c3.inc
Initially toyed with Red Hat 7.3 (2.4.19 kernel) on the Dabba1 platform (VIA EPIA 500) and quickly gave up as I felt it was too unwieldy for the Dabba project. This was followed by Gentoo experiment.Started with the 2006.1 stage3 installation on the VIA platform and then emerged the needed components one by one. This was finally concluded with a manual build of mythtv-0.20.2.
One thing that stood out in this whole process was the painful comilation times on VIA platform. This alone should motivate to look for other methods or distributions.
For the build following config was used: (/etc/make.conf)
CFLAGS="-Os -march=c3 -m3dnow -pipe -fomit-frame-pointer" CHOST="i586-pc-linux-gnu"