Kernel 3.12.6

[bmarkus]

Hi bmarkus

I managed to make a booting 3.12.6 piCore, based on the config file from your 3.12.1 (just adding the new I2S/PCM options).

It is "fat" as I simply took all the modules and included them in the piCore.gz file. Also I copied the two files "modules.builtin" and "modules.dep"

What do you think the next step is, should I start to only include the modules that are present in the previous 3.12.1 - to slim the new version - and take out the sound and net modules for ALSA and NET packages?

You mention busybox problems -  how do I know if I have that problem as well?

Steen

Try depmod command and check that modules.dep updated correctly and the other files are created, and no segfault.

As fast check:

Code: [Select]

lsmod
modprobe cifs
lsmod


[tinypoodle]

No!!
Linus is very much absolute about:
1. users *not* touching /usr/src at all, besides from installing distro provided system files
2. not to have a single symbolic link in sight

[sbp]

hi bmarkus

the first lsmod command - returned an empty list.

Then I did
sudo modprobe cifs
No errors was observed

AND
the next lsmod command - returned:
Modules  Size   Used by    Not tainted
cifs  444390      0



Also the command
sudo depmod
finished without errors.

EDIT: and it made new files in /lib/modules/3.12.6-piCore/



Steen

[bmarkus]

Interesting. I will do more investigations, here it segfaults. Can you give me your SD card image?

[sbp]

Sure, i Will send you a download link shortly.

Steen

[sbp]

Hi bmarkus.

I have just been reading up on the depmod command, which I have never used before.

But it seems like it is necessary when I make a new version of piCorePlayer with a new kernel - until now I have simply used the files provided by your kernel "modules.builin" and  "modules.dep" but it seems to me now, that using depmod would be more correct?

Steen

[bmarkus]

No, what you are doing is correct for. During startup piCore executes depmod which will update whatever is in initrd. Technically .builtin is not needed (it is missing in x86 version), it is included for user convenience to know what is built-in without looking for additional resources.

In case of cut down release however the correct way is to have .dep for the current modules instead of the full list.

[bmarkus]

It works now. initrd I used to create 3.2.16 versions were courrupted. With a fresh clean rc3 base it is OK.

[lykkedk]

Hi Jesper

As far as I remember I downloaded the cross-compiler https://github.com/raspberrypi/tools/tree/master/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi as described here: http://elinux.org/RPi_Kernel_Compilation

Then in the .config file I added:
Code: [Select]

CONFIG_CROSS_COMPILE="/cross/tools-master/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi/bin/arm-bcm2708hardfp-linux-gnueabi-"


And then just continue as you use to do it

Steen

Okay then, i downloaded the tarball from https://github.com/raspberrypi/tools/archive/master.tar.gz, and extracted it into my /home/jesper/cross directory.

There is not much more explained, what is my next step?


// Jesper

[sbp]

Hi Jesper

As far as I understand all this:
The tar-ball you just installed is your cross-compiler - therefore the line you add to the .config file points to the newly installed cross-compiler.

On my computer I need to add this line to the .config file:
CONFIG_CROSS_COMPILE="/cross/tools-master/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi/bin/arm-bcm2708hardfp-linux-gnueabi-"

BUT you must check that you have the same path - if not change the line so it points to your cross-compiler.

Then you follow the recipe from here http://elinux.org/RPi_Kernel_Compilation

In brief make your changes to the .config file
first
make mrproper
then
make ARCH=arm oldconfigconfig
then
make ARCH=arm menuconfig

finally:
make ARCH=arm -j3

(the -j3 is dependent upon how many cores your computer have)

Steen

[lykkedk]

Hi again 

On my computer I need to add this line to the .config file:
CONFIG_CROSS_COMPILE="/cross/tools-master/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi/bin/arm-bcm2708hardfp-linux-gnueabi-"

Do you meen the $PATH, when you say .config, or the config file located at
jesper@Lykke-laptop:~/rpi/tools/configs$ ls
bcm2708-ct-ng.config  bcm2708hardfp-ct-ng.config  ct-nt-version  gcc-linaro-arm-linux-gnueabihf-raspbian


Also, do i have to set my enviroment (.bashrc) to point to the compiler ??

// Jesper

EDIT !! :: I have been reading the thread, that you mentioned about building a newer kernel.
Did help a lot, for me, but there are still far to many things i do not understand!

I will start a new thread, where i will try to figure out, howto do this from scratch!

[Paul_123]

Everyone seems to be using a cross-compiler......I know the rpi is painfully slow to compile the kernel.   But I have been using my rpi to compile a few modules that have not been included.   I'm using a hardfp based raspbian image, so I would be generating hardfp based modules.

the last image I have of piCore5.1_rc3 is using    the tool chain ....armv6l-picore-linux-gnueabi/bin/armv6l-picore-linux-gnueabi-

is that a hard or soft float kernel?

I've been using piCore images that sbp makes, and he is using the tool chain

.../tools/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi-

[bmarkus]

All piCore kernels ard hardfloat, we have never had a softfloat edition.

[Paul_123]

All piCore kernels ard hardfloat, we have never had a softfloat edition.

ok....so you just rename your tool chain ....thanks

[bmarkus]

Testing 3.12.6 found buggy in tests. There are lost SSH connections, killed processes, failed loop mounts, etc. While there are new features like new camera or SPI DAC support, it is not usable.