[beagleboard] Beaglebone Black kernel

http://www.angstrom-distribution.org/building-angstrom

j.

There is a link on the card that comes in the box.

http://circuitco.com/support/index.php?title=BeagleBoneBlack

However, the card cannot read itself to you. Follow the links on the Wiki from the link above.

http://circuitco.com/support/index.php?title=BeagleBoneBlack#Software_sources

Gerald

which point to https://github.com/beagleboard/kernel/tree/3.8

which sadly does not have tags that point to specific release revisions :frowning:

Well, I guess you need to pass on the sadness to Jason! Because it is supposed to! All I can do is provide access to the links provided. If the links change or need be changed, I have to have the correct ones to provide to everyone.

I gave up my crystal ball many years ago!

Gerald

Maybe this one has the magic link. Look under" Quick Link"

http://beagleboard.org/Support/Software%20Support

If it does, let me know and I will use that link. Hopefully it will continue to work.

Gerald

Well, yeah... That repo is just a "shared" repo for kernel
development, for beagleboard.org users/developers. It doesn't have
any ties into any "build" system, such that any user can get involved,
without having to learn bitbake/dpkg-buildpackage/etc...

Koen will import changes from that into the "meta-beagleboard" repo
used directly by Angstrom.. the "tag" will be somewhere:
https://github.com/beagleboard/meta-beagleboard/commits/master

Regards,

Not being a GPL expert, will this satisfy the requirements of GPL?

Gerald

under "Quick Links->Source Code" this points to:

https://code.google.com/p/beagleboard/wiki/BeagleSourceCode

which points back to https://github.com/beagleboard/kernel

Working with a lot of "other" development boards, this beagleboard.org
project is most GPL compliment project around.

I do see the original posters point, he want's the exact kernel source
used in the BeagleBone Black as is. (he might only be happy if the
source was tarred up and included in the eMMC)

If we only did one "image" update every 3 years like zyx companies, we
could point to this exact kernel 'tag'.. But since Angstrom is more a
"free-rolling" distro, this gets interesting.. I know when you run
bitbake to build an image it tar's up all the source's.. Those should
be saved, such that on request users can get them..

The only real indicator i see is this one tag: (PV = "3.8.11")
https://github.com/beagleboard/meta-beagleboard/blob/master/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb#L15

Didn't it use to be: PV = "3.8.11"+rXYZ and you could use the rXYZ to
figure it out.

Regards,

and "compliant" as well. :slight_smile:

rday

and from ^^^ it get's pulled here ->
https://github.com/beagleboard/meta-beagleboard/commits/master/common-bsp/recipes-kernel/linux

It was shipped with 3.8.6, so maybe:
https://github.com/beagleboard/meta-beagleboard/commit/0d3f8f51cd07b0f16ca831e5640d6c048d568645

https://github.com/beagleboard/meta-beagleboard/tree/0d3f8f51cd07b0f16ca831e5640d6c048d568645/common-bsp/recipes-kernel/linux

buiild directions:
https://github.com/beagleboard/meta-beagleboard/blob/0d3f8f51cd07b0f16ca831e5640d6c048d568645/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb

build patches:
https://github.com/beagleboard/meta-beagleboard/tree/0d3f8f51cd07b0f16ca831e5640d6c048d568645/common-bsp/recipes-kernel/linux/linux-mainline-3.8

all built off mainline: v3.8.6

Regards,

Not being a GPL expert, will this satisfy the requirements of GPL?

Working with a lot of "other" development boards, this beagleboard.org
project is most GPL compliment project around.

oh certainly, I did not want to imply otherwise, I was just hinting at the issue that some people face to get the exact sources as used for a build.

I do see the original posters point, he want's the exact kernel source
used in the BeagleBone Black as is. (he might only be happy if the
source was tarred up and included in the eMMC)

a git with a hash or tag should be fine as well, and the code does not need to be included, the GPL does not demand that.

If we only did one "image" update every 3 years like zyx companies, we
could point to this exact kernel 'tag'.. But since Angstrom is more a
"free-rolling" distro, this gets interesting.. I know when you run
bitbake to build an image it tar's up all the source's.. Those should
be saved, such that on request users can get them..

releases still can be tagged.

The only real indicator i see is this one tag: (PV = "3.8.11")
https://github.com/beagleboard/meta-beagleboard/blob/master/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb#L15

Didn't it use to be: PV = "3.8.11"+rXYZ and you could use the rXYZ to
figure it out.

as I understand it, its linux 3.8 stable at revision

  9fa1d01e4fef818465d4b684b528e32b3fa68639

and then the below patches applied

Correct!

If you look real close, the "patch.sh" in:
https://github.com/beagleboard/kernel/tree/3.8

actually generated that *.bb file. :wink:

Regards,

now if that repo had tags :slight_smile:

We can always back tag it.. Say after the CircuitCo guys release an
image, they go back to the repo and back tag it:

git tag -a 3.8.8-angstrom-2013-xx-yy 9fceb02

Then it should be easy for users to find the correct one..

Regards,