>From what I've read, updating your OE source tree should be simply running

git pull

from your $OVEROTOP directory (i.e., ~/overo-oe).  As for finding overo.h, my copy is located at


The long list of numbers after 'u-boot-omap3-1_2009... might change for your configuration.  If this path does not exist, rebuild u-boot-omap3 with

bitbake -c rebuild u-boot-omap3

Then the above path should exist and contain overo.h as well as overo.c and other files.

On Tue, Feb 16, 2010 at 12:40 PM, Richman1234 <richard.manley@navy.mil> wrote:

coderdrone wrote:
> On Thu, Feb 11, 2010 at 10:44 AM, ScottEllis
> <scottellis.developer@gmail.com
>> wrote:
>> You must not have pulled from git in a long time if your u-boot source
>> tree looks this way.

OK, how do I get my overo.h files?  How do I update my source tree?  What
'git' command do I need to run?

View this message in context: http://old.nabble.com/How-to-turn-on-and-find-a-GPIO-pin----tp27427920p27612210.html
Sent from the Gumstix mailing list archive at Nabble.com.

SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
gumstix-users mailing list