**** BEGIN LOGGING AT Thu Jan 26 02:59:57 2012 **** ENDING LOGGING AT Thu Jan 26 03:37:48 2012 **** BEGIN LOGGING AT Thu Jan 26 03:55:12 2012 Jan 26 04:10:24 hi Jan 26 04:36:20 hi Jan 26 05:58:37 hi Jan 26 09:37:37 There are a few machines no longer supported in the oe-core layers in Angstrom. I'm thinking of setting up an oe-core layer for Kirkwood devices (e.g. Sheevaplug). Is it generally just a straight copy of machine confs from oe classic to core or are there functional changes? Jan 26 11:40:58 i accidentally populated a script through /etc/rc* that stalls my system (a while loop) on boot. i'm trying to start my system (using bootargs with u boot) into a run level that will allow me to fix it but am having no luck. it seems like my bootargs are never saved.. any ideas how to fix this issue? Jan 26 11:41:14 i basically want to setenv bootargs $bootargs init=/bin/sh Jan 26 11:43:17 angstrom: 03testlab  07yocto * r008dcf0ef2 10testlab/beagleboard/eglibc/systemd-image/ (5 files): beagleboard: systemd-image configured for angstrom v2012.01-core using branch angstrom-staging and revision e03cd65aa3fc4f98dd0c186479b714215fa46369 Jan 26 12:00:34 ok, got it by editing nandargs. thanks for your time Jan 26 14:19:00 hi Jan 26 14:44:33 angstrom: 03testlab  07yocto * re63b06eff3 10testlab/beaglebone/eglibc/Cloud9-IDE/ (build-id installed-package-sizes.txt installed-packages.txt): beaglebone: Cloud9-IDE configured for angstrom v2012.01-core using branch angstrom-staging and revision e03cd65aa3fc4f98dd0c186479b714215fa46369 Jan 26 16:44:29 Is Angstrom expected to run on the RaspberryPi hardware? **** ENDING LOGGING AT Thu Jan 26 17:46:57 2012 **** BEGIN LOGGING AT Thu Jan 26 17:48:19 2012 Jan 26 20:46:52 angstrom: 03testlab  07yocto * r019355954e 10testlab/beaglebone/eglibc/Cloud9-IDE/ (build-id installed-package-sizes.txt installed-packages.txt): beaglebone: Cloud9-IDE configured for angstrom v2012.01-core using branch angstrom-staging and revision fb5894bcfee62086535e6205116dcab10ee128a9 Jan 26 22:16:47 Any reason that Angstrom would not work on the RaspberryPi hardware? Jan 26 22:23:47 Mojito: won't work out of the box right now, but it would not be too hard to get it working I suspect Jan 26 22:24:53 With such small machines, I would like to avoid the more bloated distros for an embedded application Jan 26 22:25:46 absolutely Jan 26 22:26:17 I suspect all that would be needed would be an appropriate machine configuration and the kernel (and the kernel source is already available) Jan 26 22:26:48 RPi does not use TI chips, so there are bound be be driver differences Jan 26 22:27:40 The first run RPi model "B" units look awfully attractive to fool around with at a price of $35. Jan 26 22:28:03 that's why you would just use the kernel the RPi folks have released; that ought to give you all of the appropriate drivers Jan 26 22:28:19 Half the price of a BeagleBone but *with* video and audio outputs Jan 26 22:28:21 (well, aside from the binary blobs that will no doubt be needed) Jan 26 22:28:40 yeah, it's definitely interesting Jan 26 22:28:44 I suppose just using the RPi-blessed kernel and strip out all the apps I dont need **** ENDING LOGGING AT Fri Jan 27 02:59:57 2012