Op 29 okt. 2011, om 15:19 heeft Robert P. J. Day het volgende geschreven:

possibly off-topic but i'm sitting in a fedora/ARM talk right this
minute at FSOSS/linuxfest at york u, and the presenter mentioned that
when building fedora for pandaboards, they had to back off from kernel
3.0.4 to 2.6.35 because, in that situation, the filesystem had a bad
habit of switching unpredictably into read-only mode.

is this a known issue in any yocto context? again, sorry if this is
wandering far afield but yocto on a pandaboard was at the top of my
TODO list for this coming week.

I'm not seeing that problem on the pandaboard that's running 3.0.x and angstrom. The default in angstrom/meta-ti is 2.6.35 due to multimedia acceleration madness.