Hey Wawrzek, On 11/18/2013 10:16 PM, Victor Martinez wrote:
On 11/18/13 21:47, Wawrzek Niewodniczanski wrote:
[...] How hard to prepare new ARM port? or maybe someone already did it?
You need a working kernel for the device and a bootloader which let you boot "device's needs". After that, you can use a generic release and rebuild packages with custom cflags (probably rebuilding the entire toolchain with optimizations, using its own overlay as other supported devices could be the best for it) or start from scratch, with crosstools and core/core-arm ports.
Take a look to the community information, there are mailing lists, irc channel and flyspray for these task.
Related to that, we started a document where put this information: http://crux-arm.nu/Documentation/HowToContribute One important thing is to have the kernel source for the device, instead of using a binary image. This will enable the kernel compilation with our last toolchain and thus ensure better compatibility and optimization. If not, at least you have to ensure that the kernel version is greater than 2.6.25, since it is a requirement imposed by our glibc. On your part you should investigate both the bootloader and the kernel and with this we can guide you (via IRC, MailingLists, etc..) to run CRUX-ARM. Anyway, there's a shortcut if you already have a device running linux, since you can chroot our rootfs to make the first compliance checks. We would be happy to help you with your device and thus increase our list of supported devices. I encourage you to start a mailing list thread with this and go put more information about your device, as well as upstream code sources that you discover, etc. In this way it will be easier to help you. Best regards, -- Jose V Beneyto | http://sepen.it.cx/