different versions of angstrom for the BB?

just packing up for a drive down to NYC this weekend, and i'll
probably have some spare time so i figured to take the BB and play
with angstrom. i used the "stable/2009" branch of the checkout of OE
to build angstrom and, after a few hours, it all worked, after which i
got uImage-2.6.29-r35-beagleboard.bin and everything else.

  however, i notice that, over at
http://www.angstrom-distribution.org/demo/beagleboard/, what's
available is the apparently newer(?) "r37" revision. why the
difference in revision number? does r37 represent the "dev" branch?
i'll probably, at some point, want to build the dev release anyway
just for comparison purposes.

rday

Hi Robert,

This is all in git...

Follow omap3.inc which defines the 'r#'

http://cgit.openembedded.net/cgit.cgi/openembedded/commit/?id=9628f84b91574ba4c1f968ae49d8cbca3544f01c

r36: was a defconfig change, too only the normal beagleboard kernel:
http://cgit.openembedded.net/cgit.cgi/openembedded/commit/?id=6d524f9beed79eb6b6b7486f59ba19729bb28a45

r37: was the addition of the 2.6.29 'pm' kernel, no change to normal
beagleboard kernel
http://cgit.openembedded.net/cgit.cgi/openembedded/commit/?id=b25b3f49653065e2a69a04d43f6ee030259c3891

Regards,

ah, thanks. sadly, i've been away from the BB for several weeks so
i'm having to refresh my memory on all of this. but i'd better get
back to speed quickly:

  http://twitter.com/rpjday/status/2804739247

pressure's on. :slight_smile:

rday

ok, i just checked and i get it. the stable/2009 branch of OE is
still at r35, but the fully-updated org.openembedded.dev branch is now
up at r40, which inspires the potentially moronic question --
precisely which git commit on the dev branch do those downloadable r37
images correspond to?

  was it exactly the commit you list above that switched from r36 to
r37? didn't have to be, of course, i'm just curious. for the sake of
reproducibility, i generally like to know what it takes to *exactly*
reproduce what's in pre-built downloadable images.

rday

ok, i just checked and i get it. the stable/2009 branch of OE is
still at r35, but the fully-updated org.openembedded.dev branch is now
up at r40, which inspires the potentially moronic question --
precisely which git commit on the dev branch do those downloadable r37
images correspond to?

was it exactly the commit you list above that switched from r36 to
r37? didn't have to be, of course, i'm just curious. for the sake of
reproducibility, i generally like to know what it takes to *exactly*
reproduce what's in pre-built downloadable images.

rday
--

It's hard to say exactly, since it's obviously after omap3.inc was
changed to r37, but it potentially could be the last commit before
r38.. :wink: (as far as the whole angstrom root file system 'build' )

But as far as the kernel and it's patches the rXX is bumped 'usually
99% of the time', that commit associated with that change is the one
you want to 'git checkout' to get that exact *.bb recipe, to form each
rXX, if you build externally on your own..

Side note, this why my kernels have an 'oerXX' on them, to help users
understand what source & patch revision they came, although they might
be binary different due to the compiler version used..

Regards,

yup, i'd already deduced that. and i realize it sounds incredibly
picky but, for the sake of testing, i think it's important to know
exactly how pre-built images came to be so that developers can
reproduce them *precisely*. so something as simple as perhaps a
README file in the downloads directory stating the git commit from
which the images were derived would be useful. there's no point in
guessing about stuff like that if you're trying to debug and you want
to make sure others can reproduce what you're seeing.

rday

yup, i'd already deduced that. and i realize it sounds incredibly
picky but, for the sake of testing, i think it's important to know
exactly how pre-built images came to be so that developers can
reproduce them *precisely*. so something as simple as perhaps a
README file in the downloads directory stating the git commit from
which the images were derived would be useful. there's no point in
guessing about stuff like that if you're trying to debug and you want
to make sure others can reproduce what you're seeing.

rday

I agree, it's useful..

For the most part i do that, base kernel tree, it's git commit, and
the cgit link for Angstrom's patches..

http://www.rcn-ee.com/deb/kernel/beagle/jaunty/v2.6.29-58cf2f1-oer40.1/changes.txt

patch and defconfig used included in base directory..

Regards,

ok, i'm going to have to take a closer look at that to figure out
what you're doing. if you have a step-by-step writeup, that would be
cool. but as i read it (admittedly in a bit of a rush as i'm packing
for a trip), you're using the regular OE infrastructure for your
build, but you're custom building the kernel from the stock omap git
checkout (tmlind) with the appropriate OE patches applied to that, is
that it?

  i'll have to read that more carefully later when i get the time.

rday

ok, i'm going to have to take a closer look at that to figure out
what you're doing. if you have a step-by-step writeup, that would be
cool. but as i read it (admittedly in a bit of a rush as i'm packing
for a trip), you're using the regular OE infrastructure for your
build, but you're custom building the kernel from the stock omap git
checkout (tmlind) with the appropriate OE patches applied to that, is
that it?

i'll have to read that more carefully later when i get the time.

Exactly... Basically i'm building the same kernel in the an
appropriate debian based chroots for each version. (lenny, squeeze,
jaunty, etc).

I do have a complete writeup located in the debian wiki located here:
http://elinux.org/BeagleBoardDebian#Normal_Kernel_Build

The exact steps are there, however it could always use a few more 'words'.. :wink:

Regards,

I made a new image of ubuntu in which the sign is smaller and better, but the keyboard and mouse does not work ...

ah, this is building a *debian* distro, not an angstrom distro. i
missed that part. or did i misread that?

rday

That sounds suspiciously like the following:

root@beagleboard:~# cat /etc/angstrom-version
Angstrom 2009.X-test-20090722
Built from branch: org.openembedded.dev
Revision: 4223c584f1597b7e9d3f9c77ef4907e242eff9c4

regards,

koen

um, yeah, kinda like that. :slight_smile:

rday

Great, if you would stop your nasty habit of hijacking threads things would even be better.

ah, this is building a *debian* distro, not an angstrom distro. i
missed that part. or did i misread that?

There isn't anything really 'debian' specific in that section...

It just covers how to read the git tree, apply specific patches and
.config, and build the kernel yourself...

Regards,

ok, i'll have to take the time to read it more carefully later. i
might want to make that part of my fall presentation at OLF -- all the
little tricks involved in configuring and building.

rday