BeagleBoard Demo Image

In an effort to build an SDCard image for BeagleBoard with
Angstrom/Kernel 3.0 using the OE-core build system, the following
packages have been included in a demo image available for download [3]
and work is in progress to add more:

* gnome
* systemd
* pulseaudio
* alsa
* midori
* gedit
* gstreamer plugins base
* BeagleBoard Test scripts for flashing
* Kernel 3.0.3 including BeagleBoard support and uLCD display patches

Still a very minimal set, but the idea is to get the image out for
users to try out and contribute to.

The image can be downloaded at [3]

Once downloaded, prepare your SDCard by running:
zcat demo-beagleboard-sd-4GiB-r1.img.gz | dd of=/dev/mmcblk0 bs=10M

I have sent several patches to OE-core importing recipes from OE
classic, so any help in that direction is appreciated. The main
recipes for the image are at [1] and [2]

Rebuild Instructions:

You can rebuild the image by following instructions at [4]

With the following differences:
1. Edit layers.txt with:
meta-openembedded,git://github.com/joelagnel/meta-openembedded.git,master,HEAD
meta-angstrom,git://github.com/joelagnel/meta-angstrom.git,master,HEAD

2. Build filesystem using Embedded by running the command:
bitbake beagleboard-validation-gnome-image

3. Using the resultant tar and ubifs found in deploy/ directory, run
this script [5] to build an SDCard image

That should be it.

Looking forward to any feedback and contributions,

Thanks,
Joel

[1] https://github.com/joelagnel/meta-angstrom/blob/master/recipes-angstrom/images/beagleboard-gnome-image.bb
[2] https://github.com/joelagnel/meta-angstrom/blob/master/recipes-angstrom/images/beagleboard-image.bb
[3] http://www.beagleboard.org/~joelf/images/beagleboard-demo/demo-beagleboard-sd-4GiB-r1.img.gz
[4] http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/plain/README
[5] https://github.com/joelagnel/validation-scripts/blob/master/sdcard-build-scripts/sdcard-create.sh

Why aren't you creating the SD images as part of image post processing inside OE? Computers are made for automation, you know.

Oh I didn't know that!

I am excited to add that functionality to OE itself, but at this point
I think a bigger problem are the functional gaps.

Do you think posting a list of missing packages in oe-core/beagle MLs
will get some attention? and/or maintaining a tree like
"gst-ti-import" for specific features and requesting interested
developers to contribute

Thanks,
Joel

In an effort to build an SDCard image for BeagleBoard with
Angstrom/Kernel 3.0 using the OE-core build system, the following
packages have been included in a demo image available for download [3]
and work is in progress to add more:

* gnome
* systemd
* pulseaudio
* alsa
* midori
* gedit
* gstreamer plugins base
* BeagleBoard Test scripts for flashing
* Kernel 3.0.3 including BeagleBoard support and uLCD display patches

Still a very minimal set, but the idea is to get the image out for
users to try out and contribute to.

The image can be downloaded at [3]

Once downloaded, prepare your SDCard by running:
zcat demo-beagleboard-sd-4GiB-r1.img.gz | dd of=/dev/mmcblk0 bs=10M

I have sent several patches to OE-core importing recipes from OE
classic, so any help in that direction is appreciated. The main
recipes for the image are at [1] and [2]

Rebuild Instructions:

You can rebuild the image by following instructions at [4]

With the following differences:
1. Edit layers.txt with:
meta-openembedded,git://github.com/joelagnel/meta-openembedded.git,master,HEAD
meta-angstrom,git://github.com/joelagnel/meta-angstrom.git,master,HEAD

2. Build filesystem using Embedded by running the command:
bitbake beagleboard-validation-gnome-image

3. Using the resultant tar and ubifs found in deploy/ directory, run
this script [5] to build an SDCard image

Why aren't you creating the SD images as part of image post processing inside OE? Computers are made for automation, you know.

Oh I didn't know that!

I am excited to add that functionality to OE itself, but at this point
I think a bigger problem are the functional gaps.

Solve the build issues so that we are all on the same page and we can work the functional issues together. Agile even.

Do you think posting a list of missing packages in oe-core/beagle MLs
will get some attention? and/or maintaining a tree like
"gst-ti-import" for specific features and requesting interested
developers to contribute

Not as much attention as putting an image that is easy to setup in people's hands that does something cool, in this case boot really fast and run a really recent kernel. Then you'll start getting those "I wish this had X" messages.