I still need to thank you for getting the ball rolling for me. It gave me an entry point and I very much appreciate that. 
I successfully built Scott's boot image ('pansenti-boot-image' though admittedly kernel 3.2 not 3.5) last night and am currently building his console image. Whether it succeeds or not, I now have a starting point and again greatly appreciate your help. 
Especially as you helped iron out my confusion over the next steps to open up the GPIO pins I need. 

Do I modify the pins MUX settings in the board-overo.c file as well or do I need to do that in uboot?

Thanks again,

On Fri, Jan 3, 2014 at 9:54 AM, Chris Whittenburg [via Gumstix] <[hidden email]> wrote:
On Thu, Jan 2, 2014 at 5:41 PM, bstromb <[hidden email]> wrote:

Parsing of 1651 .bb files complete ( 1650 cached, 1 parsed). 2027 targets, 41 skipped, 0 masked, 0 errors. 
ERROR: No recipes available for:  / home/bstromberg/poky/meta-ros/recipes-support/boost/boost_1.54.0.bbappend
ERROR: Command execution failed: Exited with 1 

Well, I did a fresh build, and got the same error.  I haven't looked into it much, but my first question would be why Gumstix added the meta-ros layer? 

Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
gumstix-users mailing list
[hidden email]

If you reply to this email, your message will be added to the discussion below:
To unsubscribe from Disabling led_gpio pins in kernel or U-boot on Overo Fire COM (Omap3530), click here.

View this message in context: Re: Disabling led_gpio pins in kernel or U-boot on Overo Fire COM (Omap3530)
Sent from the Gumstix mailing list archive at