- CRUX-ARM - lists.crux-arm.nu

Toolchain 2.7: Preprocessor symbols patch.
by Victor Martinez 17 Jul '11

17 Jul '11

Hello, like I told in the irc channel, I found some problems trying to build firefox and thunderbird. Both of them looked for some symbols, _ARM_PCS_VFP or __ARM_PCS, and our toolchain only defines __ARM_EABI__. With this patch we can give gcc 4.5.2 these definitions. The entire discussion and this patch can be found at [1]. <code> --- gcc-4.5.2.orig//gcc/config/arm/arm.c 2011-07-14 17:25:05.000000000 +0000 +++ gcc-4.5.2//gcc/config/arm/arm.c 2011-07-14 17:31:26.000000000 +0000 @@ -700,7 +700,7 @@ static int after_arm_reorg = 0; /* The maximum number of insns to be used when loading a constant. */ static int arm_constant_limit = 3; -static enum arm_pcs arm_pcs_default; +enum arm_pcs arm_pcs_default; /* For an explanation of these variables, see final_prescan_insn below. */ int arm_ccfsm_state; --- gcc-4.5.2/gcc/config/arm/arm.h.orig 2009-12-23 16:36:40.000000000 +0000 +++ gcc-4.5.2/gcc/config/arm/arm.h 2011-07-14 18:37:45.000000000 +0000 @@ -94,7 +94,13 @@ if (arm_arch_iwmmxt) \ builtin_define ("__IWMMXT__"); \ if (TARGET_AAPCS_BASED) \ - builtin_define ("__ARM_EABI__"); \ + { \ + if (arm_pcs_default == ARM_PCS_AAPCS_VFP) \ + builtin_define ("__ARM_PCS_VFP"); \ + else if (arm_pcs_default == ARM_PCS_AAPCS) \ + builtin_define ("__ARM_PCS"); \ + builtin_define ("__ARM_EABI__"); \ + } \ } while (0) /* The various ARM cores. */ @@ -1648,6 +1654,9 @@ ARM_PCS_UNKNOWN }; +/* Default procedure calling standard of current compilation unit. */ +extern enum arm_pcs arm_pcs_default; + /* A C type for declaring a variable that is used as the first argument of `FUNCTION_ARG' and other related values. */ typedef struct </code> I hope someone can check this and comment about. I need to rebuild the entire system and make the test building those ports. Any comments, suggestions or opinions are welcome. Regards, Victor. [1] http://gcc.gnu.org/ml/gcc-patches/2010-07/msg01654.html --- Learning bit by bit Victor Martinez | http://lokalix.dyndns.org

2 2

Installer ideas
by Jose V Beneyto 27 May '11

27 May '11

Hi all, thinking about the current state of CRUX-ARM, I had some ideas that I'll try to explain as best I can. When we started this project we had a few devices and they also lacked the ability to boot from a medium (e.g. SD card) and to install CRUX on a different medium (such as an SSD). There were days when we had to use a flash card and the installation process was limited to unzip our file release (rootfs) in the root partition. Now we have some efikamx smarttop/smartbook devices (thanks to Genesi CEO) that have an SSD inside and allow to use a bootable either from an SD card, or perhaps a USB-CDROM, USB stick, etc. That is why I think we've reached the point where we can think of using an installer as is done in CRUX. I propose some ideas: - Use a initrd or initramfs image with a similar init script like the one in system/iso.git (CRUX), which should search for and mount the crux media - Use a 'setup' script to perform the installation on the user selected media. a) the script could be written in 'dialog' like upstream CRUX, but we must add 'dialog' to our initrd/initramfs b) for now we can live with a simple shell script Anyways we must add(*) 'pkgadd' to our initrd/initramfs (*) is not posible to just decompress the rootfs like we did in the past, so people should be able to select individual packages - Use a directory structure similar to upstream where we could find a directory called crux/ which contains: - a dir per collection of packages (core, opt, xorg) - the kernel directory for sources - tools, etc. - Also we could think in use an external tool to customize installer images with the number of packages we want, etc. I have some other ideas (taken from my own modifications to the original installer of CRUX) but I believe that for now we could at least to implement a basic installer. Naturally there are many things that could have explained in more detail, but I'd rather get a first impression of your ideas. What do you think? -- Jose V Beneyto | http://sepen.mine.nu

2 3

[ANN] CRUX-ARM 2.7-test1 available
by Jose V Beneyto 25 May '11

25 May '11

Hi, we're announcing the first test release of CRUX-ARM 2.7. Changelog: http://crux-arm.nu/Documentation/Changelog Rootfs: http://crux-arm.nu/releases/2.7/crux-arm-rootfs-2.7-test1.tar.bz2 http://crux-arm.nu/releases/2.7/crux-arm-rootfs-2.7-test1.tar.bz2.md5 Kernel files for versatile devices (qemu): http://crux-arm.nu/files/devices/versatile/config-2.6.35.6 http://crux-arm.nu/files/devices/versatile/zImage-2.6.35.6 http://crux-arm.nu/files/devices/versatile/modules-2.6.35.6.tar.bz2 Now we're working on getting support for more kernel devices. Please report problems if you find them. Help is always welcome :D Best regards, -- Jose V Beneyto | http://sepen.mine.nu

3 7

Genesi Scrum 2011
by acrux 18 May '11

18 May '11

There is a great opportunity from Genesi USA and CRUX developers are invited to partecipate. http://www.genesi-usa.com/event/genesiscrum By my side, i'm really sorry but i'm already booked up every days with work and studies and family...thus i cannot be there. cheers, --acrux -- acrux <acrux_it(a)libero.it>

3 2

some hints for efikamx
by acrux 18 May '11

18 May '11

little hints i collected these days using this board... maybe they are usefull. kernel: as you already know the best way is still to get sources from the Genesi overlay here: http://gitorious.org/efikamx/linux-kernel To build it, you need to remember to build uImage too because isn't still automatically done but is, anyway, correctly done using zImage: cd linux make menuconfig make make uImage make modules_install here my working kernel config: http://cruxppc.org/~acrux/arm/kernel/linux-2.6.31.14.22-efikamx.config EfikaMX does use an u-boot forks (specific for mx5) that looks for the bootfile "boot.scr" in the first readble partition on MMC (i.e. SD) and then on the SSD PATA. It's capable to read ext2/ext3 and vfat and to hanlde dos partiton table. you can understand why reading here on line #13 http://pastebin.com/RUvrBuFm bootcmd=for device in "mmc ide"; do if strcmp ${device} == mmc; then; mmcinit; setenv units "0 1"; else; setenv units "0"; fi; for interface in ${units}; do if strcmp ${device} == mmc; then mmcprobe ${interface}; else; ide reset; fi; for fs in "ext2 fat"; do setenv loadcmd "${fs}load ${device} 0:1"; if ${loadcmd} ${scriptaddr} boot.scr; then; if imi ${scriptaddr}; then; autoscr ${scriptaddr}; fi; fi; done; done; done; Anyway the safer scenario is that the partition where the kernel image resides should be a primary one and formatted as ext2 with 128-byte inodes. mkfs.ext2 -I128 /dev/mmcblk0p or mkfs.ext2 -I128 /dev/sda1 Now we can work on boot.scr In my scenario i don't use any initrd or others... This is my working boot.script http://cruxppc.org/~acrux/arm/boot.script.efikamx and you can build it to be readble from u-boot with: mkimage -A arm -O linux -a 0 -e 0 -T script -C none -n "EfikaMX Boot Script" -d myboot.script.efikamx boot.scr # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0b95:772a ASIX Electronics Corp. Bus 002 Device 002: ID 1a40:0101 TERMINUS TECHNOLOGY INC. USB-2.0 4-Port HUB Bus 002 Device 003: ID 13d3:3273 IMC Networks 802.11 n/g/b Wireless LAN USB Mini-Card # cat /proc/cpuinfo Processor : ARMv7 Processor rev 5 (v7l) BogoMIPS : 799.53 Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x2 CPU part : 0xc08 CPU revision : 5 Hardware : Genesi Efika MX (Smarttop) Revision : 51030 Serial : 0000000000000000 -- GNU/Linux on Power Architecture CRUX PPC - http://cruxppc.org/

2 2

Genesi EfikaMX and CRUX/ARM
by acrux 05 May '11

05 May '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi Jose V., hi Victor, Genesi CEO is glady to help CRUX ARM project too. They are really kind people and long-standing supporters of the CRUX PPC GNU/Linux project[1] since 2003. Here there are two Genesi Efika MX Smarttop (i.MX515)[2]+debug_board with your names... thus I need your address to ship. Faster is better. The shipment with registered mail from Italy to Spain is 13,00 euro for each machine. At your opinion you can refund me by paypal after you'll receive the stuff. cheers, - --acrux [1] http://cruxppc.org/Donors [2] http://www.genesi-usa.com/products/efika - -- GNU/Linux on Power Architecture CRUX PPC - http://cruxppc.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk3B60EACgkQxq34tDeO7LjF4wCfSmAJED3o51HYNLSRrDwI/mjy fqQAnAsaKZT5tsb29ZkG68GGAPLmGlKy =5xip -----END PGP SIGNATURE-----

2 1

new user (on i.MX515 based devices)
by acrux 04 May '11

04 May '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi pitillo, hi all, i'm going to receive from Genesi some nice ARM based stuff (Cortex-A8) therefore i'd like to understand how enjoy them with CRUX. About me... I'm a really long-long-standing CRUX user on x86 and later on I moved to PowerPC and Sparc64. I also did, from scratch, a 2.4 release full 64bit for my old Sun Ultra5. I also use x86-64 machines but only with MS products. I'd like to port and support a CRUX ARM flavour for the only Genesi Efika MX (i.MX515) as I still interested to maintain alive the CRUX PPC project. With CRUX PPC we used to have a kind of PPC overlay managed quite good from a bot on our own server and with a well tuned port/package manager like our ilenia[1]. There are a good numbers of ports that must unavoidably be different from the x86 ones. Anyway there are other deep differences as CRUX PPC supports both 32 and 64bit archs sharing the same ports tree and it has a bit different toolchain. I was thinking to start from CRUX PPC ports tree but 'cause there already is a your full working ARM port I hope we'll help each others to understand how I can implement my effort with your nice project and to help you to improve it if i'm capable. I'd like to have a full working and well tuned CRUX for this ARM machines i.e. EABI with HardFloat and SIMD Neon enabled. I still must investigate on Linaro resources about the best toolchain to choose but maybe i'll be obliged to choose gcc-4.6 and eglibc. A native build farm, i guess, is also desirable to implement with distcc . cheers, - --acrux [1] http://cruxppc.org/Ilenia - -- GNU/Linux on Power Architecture CRUX PPC - http://cruxppc.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk28bNQACgkQxq34tDeO7LgfSQCePeZnzTWFxtM4P7x2LxQ3xxps 67sAn36UjRl49QoatgELnReu9+S/+0OD =ps6F -----END PGP SIGNATURE-----

2 3

CRUX-ARM 2.7 status
by Victor Martinez 16 Mar '11

16 Mar '11

Hello all (if there is someone...), CRUX-ARM 2.7 is on the way... Current status: *** only for eabi devices *** - Toolchain updated: Kernel headers = 2.6.30.1 libgmp = 5.0.1 libmpfr = 3.0.0 libmpc = 0.8.2 binutils = 2.20.1 gcc = 4.5.2 glibc = 2.12.1 glibc ports = 2.12.1 - Current packages version: acl 2.2.49-1 attr 2.4.44-1 autoconf 2.67-1 automake 1.11.1-1 bash 4.2.8-1 bc 1.06-3 bindutils 9.7.3-1 binutils 2.20.1-1 bison 2.4.3-1 bzip2 1.0.6-1 coreutils 8.10-1 cpio 2.11-1 curl 7.21.4-1 db 4.8.30-1 dcron 4.4-2 dhcpcd 5.2.11-1 diffutils 3.0-1 e2fsprogs 1.41.14-1 ed 1.5-1 file 5.05-1 filesystem 2.7-1 findutils 4.4.2-1 flex 2.5.35-2 gawk 3.1.8-1 gcc 4.5.2-1 gdbm 1.8.3-3 gettext 0.18.1.1-1 glibc 2.12.2-2 grep 2.7-1 groff 1.21-1 gzip 1.4-1 iana-etc 2.4-1 inetutils 1.8-1 iproute2 2.6.37-1 iptables 1.4.10-1 iputils s20101006-1 kbd 1.15.2-1 less 436-1 libarchive 2.8.4-2 libgmp 5.0.1-1 libmpc 0.9-1 libmpfr 3.0.0-p8-1 libpcre 8.12-1 libtool 2.4-1 libusb 1.0.8-1 m4 1.4.16-1 make 3.82-1 man 1.6g-1 man-pages 3.32-1 mlocate 0.23.1-1 module-init-tools 3.12-1 msmtp 1.4.23-1 ncurses 5.8-1 net-tools 1.60-6 openssh 5.8p1-1 openssl 1.0.0d-1 patch 2.6.1-1 pciutils 3.1.7-1 **** perl 5.10.0-3 **** ---> This must be upgraded to finish the release build process and then start the testing/RC process. pkg-config 0.25-2 pkg-get 0.4.5-2 pkgutils 5.35.1-2 ports 1.5-10 procps 3.2.8-3 prt-get 5.18-2 psmisc 22.13-1 rc 2.26-1 readline 6.2.1-1 rsync 3.0.7-1 sed 4.2.1-1 shadow 4.1.4.3-1 sudo 1.8.0-1 sysfsutils 2.1.0-1 sysklogd 1.5-4 sysvinit 2.88-1 tar 1.26-1 tcp_wrappers 7.6-10 time 1.7-1 traceroute 2.0.17-1 udev 141-1 unzip 6.0-1 util-linux-ng 2.19-1 vim 7.3.102-1 wget 1.12-1 which 2.20-1 wireless-tools 29-1 xz 5.0.1-1 zip 3.0-1 zlib 1.2.5-2 - Kernel status: Versatile kernel = 2.6.35.7 (must be downgraded to 2.6.35.6 ????) Others must be bumped up too... and this will be hard in some cases. - TODO: .- toolchain for noeabi devices. .- kernel update for j72x, omap850 and wm8505. .- core-cross collection: perl update. .- {opt,xorg,e17,games}-cross collections: build packages for both ABI's Suggestions, comments and opinions are always welcome... and of course, if someone can give a hand (or two...), it'll be more welcome. Regards, Victor. --- Learning bit by bit Victor Martinez | http://lokalix.dyndns.org

1 0

Some questions.
by Luka Vandervelden 23 Nov '10

23 Nov '10

Hi *. \o_ I have some questions about Crux-ARM. First, is a uclibc based toolchain planned ? (and if not, would be Crux-ARM open to accept patches related to that ? for example, allowing to build the toolchain with uClibc depending on the target) Then, is Crux-ARM open to targets other than arm(|el)-*-linux-* ? (say, for example, mips-Crux-linux-uclibc, or i686-Crux-linux-gnu) The main interest wouldn’t be to port Crux to a new architecture, but to have a working Crux toolchain for that architecture. (everybody is not on x86) And finally, at least for now, why are there pairs of repositories ? There is one for the packages, and another for the cross-packages. Why not adapt the Pkgfiles to cross-build or not depending on the tool used (pkgmk or cross-pkgmk) ? Or even the options given to this tool (--target arm-... for example). So, thanks for your answers. :) Lukc

3 8

RC7 released
by Victor Martinez 20 Sep '10

20 Sep '10

Hello, I just build the new RC7 with some ports added to it: - pkg-get - sudo - bindutils It can be dowloaded from the downloads section with the new pre-packaged toolchains. Changelogs can be found here: http://crux-arm.nu/doc/?ReleaseNotes-2.6_temp Waiting comments, suggestions and problems. Best regards, Victor. Learning bit by bit Victor Martinez | http://lokalix.dyndns.org

2 2