brentn wrote:Hey Sickboy,
I don't know if this is too much to ask, but I would be interested in the process you take/took to modify the kernel - as it would be neat to be able to tune the kernel for my specific machine. (I have compiled kernels before, but not modified to any great extent, and not with make-kpkg)
For instance:
- did you start with a specific .config file, or just blank?
- how did you decide what to modify? Where was most of your effort spent? (ie Devices?)
- were there any options you had to "guess" at?
- how did you decide whether to make something a module, or built-in?
- do you do anything to optomize for the Atom processor?
- what have you tried that didn't work?
- do you do any code patching first? (and how does that work?)
- do you compile the kernel on the AAO, or is that too slow?
- if not, are there any special settings required to compile on say a Desktop i386 machine (for use on AAO)?
- How long does a compile typically take?
- what is the command you use for make-kpkg?
Also, in the case of this upcoming kernel, I see your objectives - exactly which items will you modify to accomplish these?
Thanks!
I'll toss in some info here.
On an initial .config, several have been posted and you can start anywhere. Just try optiions and see what happens.
I make more items modules than stick did. In particular EXT3 and SAMBA(or it's replacement) are large and unused by me. The general "rule" is that you make it built in if you think it is very likely used.
Compile time on the AAO was around 30-45 minutes (I think, did not time), but I now do it on my desktop w/o any special setup.
On patches, stick grabbed a later ALSA, but if you go with the released 2.6.28 it now includes it. I tried a patch to allow hacking the CPU voltage/freq table, but seams of no use.