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

1) Would anyone want a ready-to copy set of files to transfer to an SDHC
card in order to run Gentoo Linux on their Beagle Bone?

I would absolutely love that!

- Grant

  1. Would anyone want a ready-to copy set of files to transfer to an SDHC
    card in order to run Gentoo Linux on their Beagle Bone?

I would absolutely love that!

Ditto.

If there is good manifest info, I’d probably be fine in giving a mirror.

I don’t know what you mean by “manifest”. A readme.txt file? A provenance? My knowledge of terms of art can be spotty; let me know what you need.

Also, I’m happy to try compiling builds with specified configuration files. I built my own Ångström following the instruction at the Ångström site and use the uImage to facilitate communicating with my 1-wire™ device. My hope was to identify what in the Ångström build exposes the drivers and/or bus so I could activate them in a standard Gentoo build. Anyone interest in this endeavor is welcome to make suggestions (or provide a configuration file) which I can submit to my cross compiler.

I don't know what you mean by "manifest". A readme.txt file? A provenance?

Provenance with license terms.

My knowledge of terms of art can be spotty; let me know what you need.

I just don't want to get myself in legal hot water by not satisfying
license terms of redistributing your images. If there are source
requirements from LGPL, GPL, etc., then I need to know I have
satisfied the source terms.

Also, I'm happy to try compiling builds with specified configuration files.
I built my own Ångström following the instruction at the Ångström site and
use the uImage to facilitate communicating with my 1-wire(tm) device. My
hope was to identify what in the Ångström build exposes the drivers and/or
bus so I could activate them in a standard Gentoo build. Anyone interest in
this endeavor is welcome to make suggestions (or provide a configuration
file) which I can submit to my cross compiler.

A kernel compatible with the one that Angstrom uses can be acquired
from http://github.com/beagleboard/kernel.

Unless you have express permission from the builder to use his/hers source mirror, you need to host the sources yourself.

Also, I'm happy to try compiling builds with specified configuration files.
I built my own Ångström following the instruction at the Ångström site and
use the uImage to facilitate communicating with my 1-wire(tm) device. My
hope was to identify what in the Ångström build exposes the drivers and/or
bus so I could activate them in a standard Gentoo build. Anyone interest in
this endeavor is welcome to make suggestions (or provide a configuration
file) which I can submit to my cross compiler.

A kernel compatible with the one that Angstrom uses can be acquired
from http://github.com/beagleboard/kernel.

Is patch.sh from above meant to patch vanilla-sources-3.2.21 (for
example) and thereby boot the BeagleBone?

- Grant

Also, I’m happy to try compiling builds with specified configuration files.
I built my own Ångström following the instruction at the Ångström site and
use the uImage to facilitate communicating with my 1-wire™ device. My
hope was to identify what in the Ångström build exposes the drivers and/or
bus so I could activate them in a standard Gentoo build. Anyone interest in
this endeavor is welcome to make suggestions (or provide a configuration
file) which I can submit to my cross compiler.

A kernel compatible with the one that Angstrom uses can be acquired
from http://github.com/beagleboard/kernel.

Is patch.sh from above meant to patch vanilla-sources-3.2.21 (for
example) and thereby boot the BeagleBone?

I believe it patches vanilla 3.2 and applies the stable patches as well to generate a 3.2.x that boots with cape support.

>
> >> Also, I'm happy to try compiling builds with specified configuration files.
> >> I built my own Ångström following the instruction at the Ångström site and
> >> use the uImage to facilitate communicating with my 1-wire(tm) device. My
> >> hope was to identify what in the Ångström build exposes the drivers and/or
> >> bus so I could activate them in a standard Gentoo build. Anyone interest in
> >> this endeavor is welcome to make suggestions (or provide a configuration
> >> file) which I can submit to my cross compiler.
> >
> > A kernel compatible with the one that Angstrom uses can be acquired
> > from http://github.com/beagleboard/kernel.
>
> Is patch.sh from above meant to patch vanilla-sources-3.2.21 (for
> example) and thereby boot the BeagleBone?

I believe it patches vanilla 3.2

Hahahahahahhaha. *wipes away tears*.

and applies the stable patches as well to generate a 3.2.x that boots with cape support.

It's a shell script, so opening it an editor will tell you.

Also, I’m happy to try compiling builds with specified configuration files.
I built my own Ångström following the instruction at the Ångström site and
use the uImage to facilitate communicating with my 1-wire™ device. My
hope was to identify what in the Ångström build exposes the drivers and/or
bus so I could activate them in a standard Gentoo build. Anyone interest in
this endeavor is welcome to make suggestions (or provide a configuration
file) which I can submit to my cross compiler.

A kernel compatible with the one that Angstrom uses can be acquired
from http://github.com/beagleboard/kernel.

Is patch.sh from above meant to patch vanilla-sources-3.2.21 (for
example) and thereby boot the BeagleBone?

I believe it patches vanilla 3.2

Hahahahahahhaha. wipes away tears.

Oh, right, the 3.2 starts with a TI PSP kernel. The 3.6 starts with a vanilla kernel. 3.6 is getting kinda close to usable.

> > Is patch.sh from above meant to patch vanilla-sources-3.2.21 (for
> > example) and thereby boot the BeagleBone?
>
> I believe it patches vanilla 3.2

Hahahahahahhaha. *wipes away tears*.

Oh, right, the 3.2 starts with a TI PSP kernel. The 3.6 starts with a
vanilla kernel. 3.6 is getting kinda close to usable.

Could someone clarify this for me? I'm just a lowly user after all.
I'd like to boot some sort of a standard kernel (vanilla?) after
applying patches which will enable it to run on the BeagleBone. Is
that what patch.sh is meant to do?

Can this only be done with a 3.2 kernel? Or only with a 3.6 kernel?

- Grant

Both 3.2/3.6 start out with one of linus' v3.2/v3.6-rc based
kernels... BUT the v3.2 is just a massive ugly/etc fork...

Regards,

> > Is patch.sh from above meant to patch vanilla-sources-3.2.21 (for
> > example) and thereby boot the BeagleBone?
>
> I believe it patches vanilla 3.2

Hahahahahahhaha. *wipes away tears*.

Oh, right, the 3.2 starts with a TI PSP kernel. The 3.6 starts with a
vanilla kernel. 3.6 is getting kinda close to usable.

Could someone clarify this for me? I'm just a lowly user after all.
I'd like to boot some sort of a standard kernel (vanilla?) after
applying patches which will enable it to run on the BeagleBone. Is
that what patch.sh is meant to do?

Can this only be done with a 3.2 kernel? Or only with a 3.6 kernel?

Both 3.2/3.6 start out with one of linus' v3.2/v3.6-rc based
kernels... BUT the v3.2 is just a massive ugly/etc fork...

Is there a way to manually patch 3.6-rc sources I've downloaded onto
the Beaglebone via Gentoo's portage?

If not, what do I need to do before I can run these commands successfully:

git checkout origin/beaglebone-3.6 -b beaglebone-3.6 ./patch.sh
cd kernel make uImage make uImage-dtb.am335x-bone

https://github.com/beagleboard/kernel/tree/beaglebone-3.6

I haven't used git before so I'm having trouble getting off the ground.

- Grant

> > Is patch.sh from above meant to patch vanilla-sources-3.2.21 (for
> > example) and thereby boot the BeagleBone?
>
> I believe it patches vanilla 3.2

Hahahahahahhaha. *wipes away tears*.

Oh, right, the 3.2 starts with a TI PSP kernel. The 3.6 starts with a
vanilla kernel. 3.6 is getting kinda close to usable.

Could someone clarify this for me? I'm just a lowly user after all.
I'd like to boot some sort of a standard kernel (vanilla?) after
applying patches which will enable it to run on the BeagleBone. Is
that what patch.sh is meant to do?

Can this only be done with a 3.2 kernel? Or only with a 3.6 kernel?

Both 3.2/3.6 start out with one of linus' v3.2/v3.6-rc based
kernels... BUT the v3.2 is just a massive ugly/etc fork...

Is there a way to manually patch 3.6-rc sources I've downloaded onto
the Beaglebone via Gentoo's portage?

Yes, this is in the basics of ebuild files.

If not, what do I need to do before I can run these commands successfully:

git checkout origin/beaglebone-3.6 -b beaglebone-3.6 ./patch.sh
cd kernel make uImage make uImage-dtb.am335x-bone

https://github.com/beagleboard/kernel/tree/beaglebone-3.6

I haven't used git before so I'm having trouble getting off the ground.

There are lots of great tutorials out there. You might try the
lessons on github. [1]

[1] http://learn.github.com/p/intro.html

> > Is patch.sh from above meant to patch vanilla-sources-3.2.21 (for
> > example) and thereby boot the BeagleBone?
>
> I believe it patches vanilla 3.2

Hahahahahahhaha. *wipes away tears*.

Oh, right, the 3.2 starts with a TI PSP kernel. The 3.6 starts with a
vanilla kernel. 3.6 is getting kinda close to usable.

Could someone clarify this for me? I'm just a lowly user after all.
I'd like to boot some sort of a standard kernel (vanilla?) after
applying patches which will enable it to run on the BeagleBone. Is
that what patch.sh is meant to do?

Can this only be done with a 3.2 kernel? Or only with a 3.6 kernel?

Both 3.2/3.6 start out with one of linus' v3.2/v3.6-rc based
kernels... BUT the v3.2 is just a massive ugly/etc fork...

Is there a way to manually patch 3.6-rc sources I've downloaded onto
the Beaglebone via Gentoo's portage?

Yes, this is in the basics of ebuild files.

I've used epatch before, but in order to use it I think I need one or
more diff files. Are they available?

- Grant

> > Is patch.sh from above meant to patch vanilla-sources-3.2.21 (for
> > example) and thereby boot the BeagleBone?
>
> I believe it patches vanilla 3.2

Hahahahahahhaha. *wipes away tears*.

Oh, right, the 3.2 starts with a TI PSP kernel. The 3.6 starts with a
vanilla kernel. 3.6 is getting kinda close to usable.

Could someone clarify this for me? I'm just a lowly user after all.
I'd like to boot some sort of a standard kernel (vanilla?) after
applying patches which will enable it to run on the BeagleBone. Is
that what patch.sh is meant to do?

Can this only be done with a 3.2 kernel? Or only with a 3.6 kernel?

Both 3.2/3.6 start out with one of linus' v3.2/v3.6-rc based
kernels... BUT the v3.2 is just a massive ugly/etc fork...

Is there a way to manually patch 3.6-rc sources I've downloaded onto
the Beaglebone via Gentoo's portage?

Yes, this is in the basics of ebuild files.

I've used epatch before, but in order to use it I think I need one or
more diff files. Are they available?'

Have you looked at http://github.com/beagleboard/kernel ?

Could someone clarify this for me? I'm just a lowly user after all.
I'd like to boot some sort of a standard kernel (vanilla?) after
applying patches which will enable it to run on the BeagleBone. Is
that what patch.sh is meant to do?

Can this only be done with a 3.2 kernel? Or only with a 3.6 kernel?

Both 3.2/3.6 start out with one of linus' v3.2/v3.6-rc based
kernels... BUT the v3.2 is just a massive ugly/etc fork...

Is there a way to manually patch 3.6-rc sources I've downloaded onto
the Beaglebone via Gentoo's portage?

Yes, this is in the basics of ebuild files.

I've used epatch before, but in order to use it I think I need one or
more diff files. Are they available?'

Have you looked at http://github.com/beagleboard/kernel ?

Are these the diffs I want for 3.2:

https://github.com/beagleboard/kernel/tree/beaglebone-3.2/patches/3.2.29

I'm planning to add an epatch line to the vanilla-sources-3.2.29
ebuild which references a folder containing the necessary diffs. I'm
hoping I'll end up with a fully-patched set of kernel sources for the
Beaglebone. patch.sh is failing because I'm on the road with a
metered internet connection which keeps dropping and git doesn't seem
to resume.

If that should work, can anyone give me a git/rsync/anything command
which will grab those diffs for me?

- Grant

While there's a process there, I just ended up grabbing Koen's
Beaglebone 3.2 kernel sources via git. It's the easiest way of
getting them. I'm also compiling them on the 'bone (an A3), so I'd do
this in /usr/src:

git clone -b beaglebone-3.2 https://github.com/koenkooi/linux.git

Make sure you've emerged git on your 'bone. a 16 gig card works
nicely, but I'm looking at if I can latch on some actual RAM on these
things as swap and /tmp. Will probably enable zram/compressed swap as
well.

I wonder if they make SRAM or pSRAM in the gigabyte range...

Are these the diffs I want for 3.2:

https://github.com/beagleboard/kernel/tree/beaglebone-3.2/patches/3.2.29

I'm planning to add an epatch line to the vanilla-sources-3.2.29
ebuild which references a folder containing the necessary diffs. I'm
hoping I'll end up with a fully-patched set of kernel sources for the
Beaglebone. patch.sh is failing because I'm on the road with a
metered internet connection which keeps dropping and git doesn't seem
to resume.

If that should work, can anyone give me a git/rsync/anything command
which will grab those diffs for me?

While there's a process there, I just ended up grabbing Koen's
Beaglebone 3.2 kernel sources via git. It's the easiest way of
getting them. I'm also compiling them on the 'bone (an A3), so I'd do
this in /usr/src:

git clone -b beaglebone-3.2 https://github.com/koenkooi/linux.git

Thank you, I'm working on this now.

- Grant

Are these the diffs I want for 3.2:

https://github.com/beagleboard/kernel/tree/beaglebone-3.2/patches/3.2.29

I'm planning to add an epatch line to the vanilla-sources-3.2.29
ebuild which references a folder containing the necessary diffs. I'm
hoping I'll end up with a fully-patched set of kernel sources for the
Beaglebone. patch.sh is failing because I'm on the road with a
metered internet connection which keeps dropping and git doesn't seem
to resume.

If that should work, can anyone give me a git/rsync/anything command
which will grab those diffs for me?

While there's a process there, I just ended up grabbing Koen's
Beaglebone 3.2 kernel sources via git. It's the easiest way of
getting them. I'm also compiling them on the 'bone (an A3), so I'd do
this in /usr/src:

git clone -b beaglebone-3.2 https://github.com/koenkooi/linux.git

Make sure you've emerged git on your 'bone. a 16 gig card works
nicely, but I'm looking at if I can latch on some actual RAM on these
things as swap and /tmp. Will probably enable zram/compressed swap as
well.

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?

- Grant

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..

Regards,