git source trees for the images currently in http://www.angstrom-distribution.org/demo/beagleboard/

Hello,

Can someone please send the git source tree URL for the MLO file and the u-boot.bin
located at http://www.angstrom-distribution.org/demo/beagleboard/.

I am looking for the source trees that were used to build those binaries.

Thanks very much,
Chuck

go to the angstrom website, click on 'developers' and follow the instructions

go to the angstrom website, click on 'developers' and follow the instructions

Thanks Koen.

I am looking for just the U-Boot and x-loader git URLs, rather than cloning the
entire Angstrom distribution and building it under OE/bitbake.

Chuck

go to the angstrom website, click on 'developers' and follow the instructions

Thanks Koen.

I am looking for just the U-Boot and x-loader git URLs, rather than cloning the
entire Angstrom distribution and building it under OE/bitbake.

The information you are looking for is in the metadata. Please sort
through it and find the recipes. You do not need to understand OE very
well to figure out what sources are being used. The developers are
busy enough without having to do this for you.

Philip

I asked the question after already having tried delving through them a bit.

It looks like the recipes describe something more of a git tree pointer combined
with a handful of patches to be applied during bitbake (that's what is looks like
at least).

For example, take a look at:
  http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-bsp/u-boot/u-boot_git.bb

That points to a git source tree and a directory of patches:
  http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-bsp/u-boot/u-boot

Therefore my question was if there is a specific URL for the sources that went into
the images. Because by looking at these recipes, there is no patched git source tree
from Angstrom, but rather a pointer to a git source tree plus a list of patches to be
applied by bitbake. That is not the same as many open source projects, which have a
URL to a git source tree that contains the patched source.

So from perusing the recipes, it appeared there was no visible source tree that could
be cloned in a straightforward way (i.e. git clone) to get the source for the demo images
for just U-Boot and x-loader.

Creating an entire local Angstrom clone via bitbake seemed like overkill, if there was instead
a URL available for the working U-Boot source and x-loader sources.

Chuck

go to the angstrom website, click on 'developers' and follow the instructions

Thanks Koen.

I am looking for just the U-Boot and x-loader git URLs, rather than cloning the
entire Angstrom distribution and building it under OE/bitbake.

The information you are looking for is in the metadata. Please sort
through it and find the recipes. You do not need to understand OE very
well to figure out what sources are being used. The developers are
busy enough without having to do this for you.

Philip

I asked the question after already having tried delving through them a bit.

It looks like the recipes describe something more of a git tree pointer combined
with a handful of patches to be applied during bitbake (that's what is looks like
at least).

For example, take a look at:
http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-bsp/u-boot/u-boot_git.bb

That points to a git source tree and a directory of patches:
http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-bsp/u-boot/u-boot

Therefore my question was if there is a specific URL for the sources that went into
the images. Because by looking at these recipes, there is no patched git source tree
from Angstrom, but rather a pointer to a git source tree plus a list of patches to be
applied by bitbake. That is not the same as many open source projects, which have a
URL to a git source tree that contains the patched source.

So from perusing the recipes, it appeared there was no visible source tree that could
be cloned in a straightforward way (i.e. git clone) to get the source for the demo images
for just U-Boot and x-loader.

from bb:

SRC_URI_beagleboard = "git://www.denx.de/git/u-boot.git;protocol=git \

clone this tree ^

Branch on this commit:
SRCREV_pn-${PN}_beagleboard = "c7977858dcf1f656cbe91ea0dc3cb9139c6a8cc8"

file://0001-OMAP3-Beagle-Pin-Mux-initialization-glitch-fix.patch \

file://0002-OMAP-Remove-omapfb.debug-y-from-Beagle-and-Overo-env.patch
\

file://0003-omap3_beagle-enable-the-use-of-a-plain-text-file-nam.patch
\

file://0004-OMAP3-BeagleBoard-Enable-pullups-on-i2c2.patch \

file://0005-ARMV7-OMAP3-BeagleBoard-add-xM-rev-B-to-ID-table.patch \

file://0006-OMAP3-BeagleBoard-add-more-expansionboard-IDs.patch \
                       file://0007-OMAP3-Add-DSS-driver-for-OMAP3.patch \
                       file://0008-BeagleBoard-Added-userbutton-command.patch \

file://0009-OMAP3-beagle-pass-expansionboard-name-in-bootargs.patch \
                       file://0010-Enable-DSS-driver-for-Beagle.patch \
                       file://0011-Add-led-command.patch \
                       file://0012-BeagleBoard-Added-LED-driver.patch \

file://0013-OMAP3-BeagleBoard-updated-default-configuration.patch \

file://0014-Corrected-LED-name-match-finding-avoiding-extraneous.patch
\

file://0015-omap3_beagle-Switch-default-console-from-ttyS2-to-tt.patch
\

file://0016-BeagleBoard-Load-kernel-via-MMC-ext2-not-fat.patch \
                       file://fw_env.config \

then apply these patches.. :wink:

can be found here:

http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-bsp/u-boot/u-boot

then repeat for x-loader

Creating an entire local Angstrom clone via bitbake seemed like overkill, if there was instead
a URL available for the working U-Boot source and x-loader sources.

no clone/bitbake of Angstrom required..

Regards,

from bb:

SRC_URI_beagleboard = "git://www.denx.de/git/u-boot.git;protocol=git \

clone this tree ^

Branch on this commit:
SRCREV_pn-${PN}_beagleboard = "c7977858dcf1f656cbe91ea0dc3cb9139c6a8cc8"

file://0001-OMAP3-Beagle-Pin-Mux-initialization-glitch-fix.patch \

file://0002-OMAP-Remove-omapfb.debug-y-from-Beagle-and-Overo-env.patch
\

file://0003-omap3_beagle-enable-the-use-of-a-plain-text-file-nam.patch
\

file://0004-OMAP3-BeagleBoard-Enable-pullups-on-i2c2.patch \

file://0005-ARMV7-OMAP3-BeagleBoard-add-xM-rev-B-to-ID-table.patch \

file://0006-OMAP3-BeagleBoard-add-more-expansionboard-IDs.patch \
                       file://0007-OMAP3-Add-DSS-driver-for-OMAP3.patch \
                       file://0008-BeagleBoard-Added-userbutton-command.patch \

file://0009-OMAP3-beagle-pass-expansionboard-name-in-bootargs.patch \
                       file://0010-Enable-DSS-driver-for-Beagle.patch \
                       file://0011-Add-led-command.patch \
                       file://0012-BeagleBoard-Added-LED-driver.patch \

file://0013-OMAP3-BeagleBoard-updated-default-configuration.patch \

file://0014-Corrected-LED-name-match-finding-avoiding-extraneous.patch
\

file://0015-omap3_beagle-Switch-default-console-from-ttyS2-to-tt.patch
\

file://0016-BeagleBoard-Load-kernel-via-MMC-ext2-not-fat.patch \
                       file://fw_env.config \

then apply these patches.. :wink:

can be found here:

http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-bsp/u-boot/u-boot

then repeat for x-loader

Creating an entire local Angstrom clone via bitbake seemed like overkill, if there was instead
a URL available for the working U-Boot source and x-loader sources.

no clone/bitbake of Angstrom required..

Regards,

Thanks Robert. I agree, it looks like from the Angstrom side of things, you kind of need
to "build up" the tree using patches if going this route.

Chuck

Chuck Meade wrote:

Creating an entire local Angstrom clone via bitbake seemed like overkill, if there was instead
a URL available for the working U-Boot source and x-loader sources.

no clone/bitbake of Angstrom required..

Regards,

Thanks Robert. I agree, it looks like from the Angstrom side of things, you kind of need
to "build up" the tree using patches if going this route.

yes, this is the way it works there, a git reference and a bunch of patches