the proposed recipe for angstrom and a pico projector

i can't test this until i run out and buy a new SD card as all of
mine are currently allocated but, if i grab the most recent
(2.6.28-r17) files from here (ignore the 2.6.29 git builds for now):

  http://www.angstrom-distribution.org/demo/beagleboard/

here's my planned bootargs value to drive my pico:

console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2 rw
  rootfstype=ext3 rootwait omap-dss.def_disp=lcd
  omapfb.video_mode=640x480MR-16@60

does that look about right? should be able to test in an hour or two.

rday

i can't test this until i run out and buy a new SD card as all of
mine are currently allocated but, if i grab the most recent
(2.6.28-r17) files from here (ignore the 2.6.29 git builds for now):

2.6.29 is a huge improvement over .28, so ignoring it would be foolish. And all omap kernels there are built from git.

http://www.angstrom-distribution.org/demo/beagleboard/

here's my planned bootargs value to drive my pico:

console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2 rw
rootfstype=ext3 rootwait omap-dss.def_disp=lcd
omapfb.video_mode=640x480MR-16@60

does that look about right? should be able to test in an hour or two.

2.6.28 and 2.6.29 are configured for the pico projector by default. 2.6.29 has fixes that can even cope with bootloaders that show dogs on the screen.

regards,

Koen

> i can't test this until i run out and buy a new SD card as all of
> mine are currently allocated but, if i grab the most recent
> (2.6.28-r17) files from here (ignore the 2.6.29 git builds for
> now):

2.6.29 is a huge improvement over .28, so ignoring it would be
foolish. And all omap kernels there are built from git.

  will that 2.6.29 git kernel build work with the same pre-built
rootfs at the angstrom download page? that was my only concern. if
it's compatible, then, yes, it would be a no-brainer to go with the
2.6.29 kernel.

  and built from *which* git? the kernel.org linux-omap git here?

http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git

using what config file? "omap3_beagle_defconfig"?

2.6.28 and 2.6.29 are configured for the pico projector by default.
2.6.29 has fixes that can even cope with bootloaders that show dogs
on the screen.

  what do you mean they're "configured?" as in, the kernel
configuration already sets the appropriate omapfb settings? so that
one doesn't need to specify them at all in u-boot bootargs? that's
convenient.

rday

by the way, the info above is exactly the kind of thing that should
be in a README file in that angstrom download directory. even if
people don't want to build their own, it's still handy to know what
the bootargs should be, where the kernels came from, their .config
files and so on.

rday

Yes, you just need to download the appropriate modules tar file and extract it to get linux modules that match the kernel…

Op 29 mei 2009, om 00:25 heeft Robert P. J. Day het volgende geschreven:

i can't test this until i run out and buy a new SD card as all of
mine are currently allocated but, if i grab the most recent
(2.6.28-r17) files from here (ignore the 2.6.29 git builds for
now):

2.6.29 is a huge improvement over .28, so ignoring it would be
foolish. And all omap kernels there are built from git.

will that 2.6.29 git kernel build work with the same pre-built
rootfs at the angstrom download page? that was my only concern. if
it's compatible, then, yes, it would be a no-brainer to go with the
2.6.29 kernel.

and built from *which* git? the kernel.org linux-omap git here?

http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git

The .ipk files for the kernel have a Source: field, have a look in there. It will also list the 100+ patches that are getting applied.

using what config file? "omap3_beagle_defconfig"?

zcat /proc/config.gz on a running system will give you the config used.

If you want more details, everything is built with OE, all settings and source locations can be found in there.

2.6.28 and 2.6.29 are configured for the pico projector by default.
2.6.29 has fixes that can even cope with bootloaders that show dogs
on the screen.

what do you mean they're "configured?" as in, the kernel
configuration already sets the appropriate omapfb settings? so that
one doesn't need to specify them at all in u-boot bootargs? that's
convenient.

That's exactly what "configured for the pico projector by default" means. The only caveat is that it will accept params from u-boot, so if you tell uboot to boot the kernel with settings that are incompatible with the pico, the pico will obviously not work.

regards,

Koen