From: Lonnie A. <li...@lo...> - 2015-11-21 22:41:45
|
Hi Devs, What are the thoughts here about adding x86_64 support ? You may ask why would we think about x86_64 support when 2 GB RAM is more than plenty for AstLinux. While x86_64 will be slightly faster in most all cases, it will use more RAM. Though a 2 GB RAM system should still be plenty. Now for the intangibles, modern kernel modules and drivers are usually tested on x86_64 and not on i586, so x86_64 will be better tested ongoing. So, is it worth the effort for the AstLinux team to consider adding x86_64 support ? Of course, the RUNNIX bootloader, alix and net5501 boards will still require 32-bit images. The geni586 and geni586-serial images will continue to be 32-bit. If the answer is "why not" to the above question, how would it be implemented... We would need an additional "crosstool-ng-src/ct-ng-1.20.0-3.2.config" config for x86_64 support generating an additional toolchain. ("crosstool-ng-src/ct-ng-1.20.0-3.2-x86_64.config") We would need an additional "project/astlinux/geni586/linux-smp.config" config for an x86_64 kernel. ("project/astlinux/genx86_64/linux-smp.config") Add two new board types: genx86_64 and genx86_64-serial Since both the toolchain and kernel config is specified in the Buildroot .config file, editing the .config file is all that is needed for an x86_64 custom image. Darrick will need a slightly altered master-build script to also generate x86_64 images. Also binary blobs, like SILK CODECs and the FOP2 interface would need 32 and 64 bit versions. Also the things we didn't think of :-) Thoughts ? Lonnie |