From: "Frederic Soulier" <[EMAIL PROTECTED]> > Hi > > Excuse my ignorance but I don't understand the relationship between the > -tmb kernel and the (official?) -mdk kernel? > Is that work done in parallel that will end up in a unified kernel or > something like that? > Could someone in the know enlighten me on this one? >
You can think of it in the same way as the -ac kernels are to the original kernel.org kernel.... It's somewhat a "playing ground" for new features and drivers, that does not exist in main mdk kernels... (you could also call it a "hackkernel" ...) This kernel is not officially supported by mdk, and even if some patches from it ends up in the main kernel, don't expect that all of them ever will., as that's always up to Juan and the mdk kernel team... as for how my kernel is related to the mdk kernel, think of it like this... Take the current mdk kernel: kernel-2.4.22-0.5mdk when I add my patches to it, I change the name: kernel -> kernel-tmb and when I do my first build, I add '.1tmb_ ' to the version numbers (second build would be '.2tmb_') so that you will see the difference in '/lib/modules/*' and '/usr/src/*' and I have to keep the 'mdk' part at the end of the version number to satisfy the /etc/init.d/kheader, or people will have problems when they need to compile 3rdparty kernel-modules (ex.nvidia) against it... and just to summarize, just compare the names: kernel-2.4.22-0.5mdk kernel-tmb-2.4.22-0.5.1tmb_mdk and you see how easy it is to know wich mdk kernel it's based on... Thomas
