Tiny Core Base > Raspberry Pi

How to use a newer kernel?

<< < (11/13) > >>

tinypoodle:

--- Quote from: sbp on April 08, 2013, 03:47:46 PM ---I don't know exactly what to do after having build the kernel - the modules should go into the piCore.gz?

--- End quote ---

http://wiki.tinycorelinux.net/wiki:custom_kernel

bmarkus:

--- Quote from: sbp on April 08, 2013, 03:47:46 PM ---The problem I had with using a wifi-USB dongle and a USB-DAC at the same time could be solved by adding this line to the cmdline.txt: dwc_otg.speed=1


--- End quote ---

There are many issues with the Pi's USB stack, like USB keyboard breaks WiFi link, incompatibility wit keyboards, peformance isssue with playback, etc. affecting various distributions and applications. Also some kernel guys simply call is scrap.

dwc_otg.speed=1

limits USB speed to 12 Mbit/s which means less overhead for driver/CPU. In many cases it solves the problem, but it is limiting connected unit's performance too.

You may read this:

http://raspberrypi.stackexchange.com/questions/1886/what-kernel-parameters-are-available-for-fixing-usb-problems

sbp:
hi I hope you have not given up on me, I'm still trying and reading up on how to make a kernel + modules for raspberry.

The status now is:
I can build a functional kernel if I use the .config file from bmarcus's 3.6.11 kernel.

But after reading the tinycore wiki: http://wiki.tinycorelinux.net/wiki:custom_kernel
 I stumbled on the following sentence:


--- Code: ---"The TC patches and other related files for the standard TC kernel are available at
http://tinycorelinux.net/4.x/x86/release/src/kernel/ "
--- End code ---

Should I apply the TC-patches to the raspberry kernel before building the kernel, and can the patches from the x86 version be used on an ARM kernel?

And regarding the modules - this is where I think I have most problems:


--- Code: ---When it comes to the modules and firmware files, you basically have two options, either let them be part of your initrd (a file named “tinycore.gz” in TC) or let them be part of extension files
(*.tcem). In most cases it is probably best to have some of them built into the initrd and some
available as loadable extensions. If you are unsure, build all of your files into the initrd.
--- End code ---

I think the best option for me will be to put them in the tinycore.gz.
But I can't find any description on how to make the tinycore.gz

Do you have a step-by-step procedure?

Steen

tinypoodle:
http://wiki.tinycorelinux.net/wiki:remastering
http://wiki.tinycorelinux.net/wiki:dynamic_root_filesystem_remastering

bmarkus:

--- Quote from: sbp on April 14, 2013, 04:34:03 AM ---
Should I apply the TC-patches to the raspberry kernel before building the kernel, and can the patches from the x86 version be used on an ARM kernel?


--- End quote ---

No these are for x86. On RPi we are using the official RPi kernels.

Regarding initrd see http://wiki.tinycorelinux.net/wiki:remastering

Navigation

[0] Message Index

[#] Next page

[*] Previous page