[beagleboard] Gentoo on Beagle Bone - Already to Built Image: Should I Stage It?

And don't forget to also merge, this tree

EXTERNAL_TREE="git://arago-project.org/git/projects/linux-am33x.git"
EXTERNAL_BRANCH="v3.2-staging"
EXTERNAL_SHA="720e07b4c1f687b61b147b31c698cb6816d72f01"

on top of v3.2.0 before you patch the local directories..

Nice, ugly mess isn't it? :wink:

Regards,

I have beaglebone-3.2 from git and I'm trying to patch the vanilla
3.2.30 sources but all I get are failed hunks like this:

# cd beaglebone-3.2/patches/3.2.30
# patch -p1 --dry-run -d /usr/src/linux
<0134-VFS-make-vfs_fstat-use-f-get-put-_light.patch
patching file fs/stat.c
Hunk #1 FAILED at 57.
1 out of 1 hunk FAILED -- saving rejects to file fs/stat.c.rej

Does anyone know what I'm doing wrong?

Yes, use v3.2.0 sources as a base, and actually look inside the
patch.sh file at the "PATCHSET" variable and patch those directories
in order listed..

And don't forget to also merge, this tree

EXTERNAL_TREE="git://arago-project.org/git/projects/linux-am33x.git"
EXTERNAL_BRANCH="v3.2-staging"
EXTERNAL_SHA="720e07b4c1f687b61b147b31c698cb6816d72f01"

on top of v3.2.0 before you patch the local directories..

Nice, ugly mess isn't it? :wink:

I'm bound to screw this up 10 ways. Is the 3.6 patching process any
better/cleaner/easier?

Alternatively, if I use patch.sh, can I stay on top of updates without
doing a full download each time? In other words, would running
patch.sh twice in a row result in very little being downloaded?

- Grant

I have beaglebone-3.2 from git and I'm trying to patch the vanilla
3.2.30 sources but all I get are failed hunks like this:

# cd beaglebone-3.2/patches/3.2.30
# patch -p1 --dry-run -d /usr/src/linux
<0134-VFS-make-vfs_fstat-use-f-get-put-_light.patch
patching file fs/stat.c
Hunk #1 FAILED at 57.
1 out of 1 hunk FAILED -- saving rejects to file fs/stat.c.rej

Does anyone know what I'm doing wrong?

Yes, use v3.2.0 sources as a base, and actually look inside the
patch.sh file at the "PATCHSET" variable and patch those directories
in order listed..

And don't forget to also merge, this tree

EXTERNAL_TREE="git://arago-project.org/git/projects/linux-am33x.git"
EXTERNAL_BRANCH="v3.2-staging"
EXTERNAL_SHA="720e07b4c1f687b61b147b31c698cb6816d72f01"

on top of v3.2.0 before you patch the local directories..

Nice, ugly mess isn't it? :wink:

I'm bound to screw this up 10 ways. Is the 3.6 patching process any
better/cleaner/easier?

Yes, it's less of a massive un-maintable fork, as it's based on v3.6..
But much less support for Capes at this exact moment in time. :slight_smile:

Alternatively, if I use patch.sh, can I stay on top of updates without
doing a full download each time? In other words, would running
patch.sh twice in a row result in very little being downloaded?

Once you run "./patch.sh" the first time it will "git clone" linus'
tree (1) so if you've already cloned that before, just do (exactly)

git clone git://github.com/beagleboard/kernel.git
cd kernel
git clone --reference /dir/to/existing/linux/git/clone/
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel

(i wasn't thinking when i named the directory "kernel" in a repo name
"kernel" opps, too late to ever fix that. :wink: )

and it'll pull your git objects from your already cloned directly,
instead via the internet.. (note, as this point, don't remember the
other clone, as your objects are shared)

If you DON'T have a previous clone.. Find some free-wifi, as you'll
need to download around 500-700Mb on the initial running of
"./patch.sh" but afterwards it'll just pull in the git objects..

1: kernel/git/torvalds/linux.git - Linux kernel source tree

Regards,

Once you run "./patch.sh" the first time it will "git clone" linus'
tree (1) so if you've already cloned that before, just do (exactly)

git clone git://github.com/beagleboard/kernel.git
cd kernel
git clone --reference /dir/to/existing/linux/git/clone/
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel

(i wasn't thinking when i named the directory "kernel" in a repo name
"kernel" opps, too late to ever fix that. :wink: )

and it'll pull your git objects from your already cloned directly,
instead via the internet.. (note, as this point, don't remember the
other clone, as your objects are shared)

If you DON'T have a previous clone.. Find some free-wifi, as you'll
need to download around 500-700Mb on the initial running of
"./patch.sh" but afterwards it'll just pull in the git objects..

1: kernel/git/torvalds/linux.git - Linux kernel source tree

Thanks, I will do this ASAP. The patch.sh operations for 3.2 and 3.6
should be run completely separately and don't share any info?

- Grant

Once you run "./patch.sh" the first time it will "git clone" linus'
tree (1) so if you've already cloned that before, just do (exactly)

git clone git://github.com/beagleboard/kernel.git
cd kernel
git clone --reference /dir/to/existing/linux/git/clone/
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel

(i wasn't thinking when i named the directory "kernel" in a repo name
"kernel" opps, too late to ever fix that. :wink: )

and it'll pull your git objects from your already cloned directly,
instead via the internet.. (note, as this point, don't remember the
other clone, as your objects are shared)

If you DON'T have a previous clone.. Find some free-wifi, as you'll
need to download around 500-700Mb on the initial running of
"./patch.sh" but afterwards it'll just pull in the git objects..

1: kernel/git/torvalds/linux.git - Linux kernel source tree

I ran patch.sh for 3.6, but when it completed I realized there is no
.config file in kernel/ and 'make am335x_evm_config' doesn't work as
it did for 3.1. Am I supposed to import my 3.1 .config and 'make
oldconfig'?

- Grant

Have you looked in the 'configs/' directory in the main repo?