On 10/29/09, Ralf Mardorf <[email protected]> wrote: > rosea grammostola wrote: >> >> >> On Thu, Oct 29, 2009 at 6:36 PM, Ralf Mardorf >> <[email protected] <mailto:[email protected]>> wrote: >> >> rosea grammostola wrote: >> > There is. But I'm wondering if it's different when I just build >> for my >> > own system or for 'all' pc's. >> > How do I know which packages I should have installed for the kernel >> > build, to support as much hardware as possible... >> >> For the kernel build it's not important what packages you have got >> installed. Important is, that you keep the CPU type at x86 or x86_64 >> instead of optimizing it e.g. to amd64. >> >> >> This is in the config: >> # >> # CONFIG_64BIT is not set >> CONFIG_X86_32=y >> # CONFIG_X86_64 is not set >> CONFIG_X86=y >> CONFIG_OUTPUT_FORMAT="elf32-i386" > > This looks like it is for all 32bit CPUs. I guess for 64bit CPUs a > separated compiling is needed. You will get some help when running "# > make menuconfig" (I recommend menuconfig, but there are also other tools).
So you can compile a 65bit kernel on a 686 computer? Just changing it in menuconfig? > >> >> It's also important that you >> don't fit the number of CPUs to your hardware, keep it at e.g. 512 >> instead of using 2. >> >> >> Where can I find that? This is in the config: >> # >> # Digest >> # >> CONFIG_CRYPTO_CRC32C=m >> CONFIG_CRYPTO_CRC32C_INTEL=m >> CONFIG_CRYPTO_MD4=m >> CONFIG_CRYPTO_MD5=y >> CONFIG_CRYPTO_MICHAEL_MIC=m >> CONFIG_CRYPTO_RMD128=m >> CONFIG_CRYPTO_RMD160=m >> CONFIG_CRYPTO_RMD256=m >> CONFIG_CRYPTO_RMD320=m >> CONFIG_CRYPTO_SHA1=m >> CONFIG_CRYPTO_SHA256=m >> CONFIG_CRYPTO_SHA512=m >> CONFIG_CRYPTO_TGR192=m >> CONFIG_CRYPTO_WP512=m > > Run "make menuconfig" during your kernel build process, this will be > easier, because it has a help option and it displays readable text > instead of CONFIG_VARIABLES. > >> >> This issues, timer resolution, rt support etc. is >> set by the config file. Copy /boot/config-2.6.29-1-multimedia-amd64 to >> your source directory and rename it to .config, then load it when you >> run "# make menuconfig", if needed, IIRC I didn'd need to copy the >> config file. For the build you might need: >> fakeroot >> gcc >> kernel-package >> make >> libncurses5-dev >> Btw. the patch command has got a --dry-run option. >> >> >> >> --dry-run option? > > You need to use the vanilla kernel source and to add a patch for rt > support. If you add the patch script by the patch command you can > simulate this by using "patch --dry-run [snip] | grep FAIL" to see if > everything is fine. Normally this isn't needed when you patch a vanilla > kernel with any patch, but maybe you will add an additional patch that > might conflict with the rt patch, e.g. the tux on ice patch would > conflict, thus you would need to add some patches manually, but don't > worry, patching a vanilla kernel with rt won't cause any trouble. > _______________________________________________ > 64studio-users mailing list > [email protected] > http://lists.64studio.com/mailman/listinfo/64studio-users > _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
