How to get an earlier Angstrom kernel

GoogleGroups
1

Hi,
    I am trying to revert to an earlier kernel of Angstrom and seem to
be having trouble doing it. I updated to linux-omap-2.6.29-r46 which
caused there to be a few problematic patches and kernel panics, and
would like to revert back to the linux-omap-2.6.29-r35 and set it as
the default kernel for the console-image recipe and all those images
that are built off of it. Can someone help me do this using
openembedded?

I appreciate any help,
Bob

2

Hi Bob,

The following recipe: linux/linux_omap-2.6.29 tells you where to set
the preferred revision:

# The main PR is now using MACHINE_KERNEL_PR, for omap3 see conf/
machine/include/omap3.inc

So changing the MACHINE_KERNEL_PR field in conf/machine/include/
omap3.inc to r35 will solve your problem.

Thanks,
Tim

3

This is way incorrect. omap3.inc only contains the version number, it
doesn't contain the actual patchset used to create
r35. If you want r35 you need to look into the git log and git
checkout *COMMIT the tree at the time of 'r35' and copy the
linux-omap-2.6.29.bb file along with any missing patches and
rebuild...

COMMIT: e47846def85976da24a74838c55fafcb7751d3dd

Regards,

4

It just so happens that I formatted my computer in between the Linux
versions so I don't believe I will be able to find r35 via looking at
my past fit checkouts. Is there another way?

Thanks!

5

All history is available in the Angstrom openembedded git tree...
Just reclone it on your new install..

Regards,

6

Is the commit you listed above the correct one or only an example?
Being that I am somewhat new to get and would like to be able to do
this quickly in the future, how did you find the commit number so
easily? I tried looking through git log --summary and couldn't find
that one...

To summarize I used the following commands:

git checkout e47846def85976da24a74838c55fafcb7751d3dd -b linux-
omap-2.6.29-r35
mv tmp_dir/ tmp_dir_old # I dont know if this was needed
bitbake console-image

Should this do it? Sorry for continuing to pick at this, I'm still
figuring things out. Thanks for the help.

-Bob

7

Hi Bob,

No problem at all, since there have been alot of changes since r35,
you'll probably want to move your current tmp_dir..

That git id is correct for r35, for reference i pulled it from here:
http://cgit.openembedded.net/cgit.cgi/openembedded/log/recipes/linux/linux-omap-2.6.29

It's the commit id right before it was changed to r36...

Regards,

8

Great! Thank you very much. I have one more question that you might be
able help me with. In the process of of playing around with the git
tree I accidentally deleted it (I thought I was in a different
folder). I recloned the repo just fine but now I am getting a warning
at the start of all my bitbake builds. The warning is:

/var/lib/python-support/python2.6/bb/COW.py:29: DeprecationWarning:
the sets module is deprecated import types, sets

I have a feeling that doing a 'git pull' might fix this but I am
afraid to do it because it might change the commit that I am on. Do
you have any quick suggestions on how I could deal with this? I don't
want to take up too much of your time so I appreciate any help you can
offer.

Thanks!

9

Strange, i haven't seen that error before..

The checkout might be too old, so lets just merge the two..

From the r35 checkout,

Copy all the folders & files from:
recipes/linux/linux-omap-2.6.29/

and copy

recipes/linux/linux-omap_2.6.29.bb

To a temp location

Next checkout the top of the git tree, and copy the files back in that
directory and overwrite the *.bb file. It'll give you the latest
Angstrom checkout along with the older r35 kernel.

Regards,