Sun Sep 14 20:25:46 CEST 2014

Building linux kernel

git clone https://github.com/torvalds/linux.git
cd linux
git checkout 3.17.0-rc4
git checkout -b bbb

wget https://rcn-ee.net/deb/wheezy-armhf/v3.17.0-rc4-bone2/defconfig
mv defconfig arch/arm/configs/beaglebone_defconfig

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- beaglebone_defconfig
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- menuconfig
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- LOADADDR=0x82000000 -j4 uImage dtbs
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules

(don't use arm-linux-gnueabihf- ?)

I took LOADADDR from uEnv.txt

us the "uImage-dtb.am335x-boneblack" step necessary?

Some other notes [4].

So with all these different approach I'm left with the questions:
- does a vanilla kernel work or is a different branch necessary?
- does the dtb need to be compiled in?
- what about firmware?

This[5] is the official one.
Looks like it got switched to 3.14 recently[6]:

    So the "-bone" is close to mainline (small # of patches). The
    "-ti" we are a basing on a ti branch: (git.ti.com, patchset
    >20Mb).. Plus the 'debian' linux-image-armmp will also work once
    we switch to jessie..  (you can even install ubuntu's linux-image
    *.deb) the bootloader will find it.

Maybe stick to 3.8?  My bbb is running 3.8.13-bone47 which in git has
moved to 3.8.13-bone64

This is compiled here[7].
That one does have CONFIG_UIO_PRUSS=m in config[8].
Let's try.

[1] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git
[2] https://rcn-ee.net/deb/wheezy-armhf/v3.17.0-rc4-bone2/defconfig
[3] http://elinux.org/Building_BBB_Kernel
[4] http://eewiki.net/display/linuxonarm/BeagleBone+Black
[5] https://github.com/beagleboard/linux
[6] http://permalink.gmane.org/gmane.comp.hardware.beagleboard.user/72908
[7] https://rcn-ee.net/deb/wheezy-armhf/v3.8.13-bone64/
[8] https://rcn-ee.net/deb/wheezy-armhf/v3.8.13-bone64/defconfig