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

[FS#3 - Task closed] Create a toolchain with hardfp support.
by CRUX-ARM 21 Nov '11

21 Nov '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#3 - Create a toolchain with hardfp support. User who did this - Victor Martinez (pitillo) Reason for closing: Implemented Additional comments about closing: Done in http://crux-arm.nu/gitweb?p=toolchain-hardfp.git;a=summary More information can be found at the following URL: http://crux-arm.nu/bugs/index.php?do=details&task_id=3 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[FS#17 - Task closed] test2: filed only for test
by CRUX-ARM 03 Nov '11

03 Nov '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#17 - test2: filed only for test User who did this - Mr Super User (admin) Reason for closing: Not a bug More information can be found at the following URL: http://crux-arm.nu/bugs/index.php?do=details&task_id=17 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[FS#17 - Task opened] test2: filed only for test
by CRUX-ARM 03 Nov '11

03 Nov '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Jose V Beneyto (sepen) Attached to Project - CRUX-ARM Summary - test2: filed only for test Task Type - Bug Report Category - ports/core-arm Status - New Assigned To - Operating System - CRUX-ARM Severity - Low Priority - Normal Reported Version - 2.7 Due in Version - Undecided Due Date - Undecided Details - test2 More information can be found at the following URL: http://crux-arm.nu/bugs/index.php?do=details&task_id=17 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[FS#16 - Task closed] test: filed only for test
by CRUX-ARM 03 Nov '11

03 Nov '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#16 - test: filed only for test User who did this - Jose V Beneyto (sepen) Reason for closing: Not a bug More information can be found at the following URL: http://crux-arm.nu/bugs/index.php?do=details&task_id=16 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[FS#16 - Task opened] test: filed only for test
by CRUX-ARM 03 Nov '11

03 Nov '11

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Jose V Beneyto (sepen) Attached to Project - CRUX-ARM Summary - test: filed only for test Task Type - Bug Report Category - devtools Status - New Assigned To - Jose V Beneyto, Victor Martinez Operating System - CRUX-ARM Severity - Low Priority - Normal Reported Version - 2.7 Due in Version - Undecided Due Date - Undecided Details - test More information can be found at the following URL: http://crux-arm.nu/bugs/index.php?do=details&task_id=16 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

Notes about the installer for CRUX ARM
by Jose V Beneyto 20 Oct '11

20 Oct '11

Hey all, as we talked many times, maybe we need an iso image which groups all our releases for a version. That's a way to have all our development in the same place and released. For this notes I'll use word "iso" but in the practice we don't need to have an iso image for downloading and burn to a cdrom, so just we need a filesystem structure that provides all the stuff to create the installation media for our final device. With that I wanted to say that maybe we could just release CRUX-ARM-2.7.iso or maybe CRUX-ARM-2.7.tar.bz2, but that doesn't matter. With that in mind I'll explain my ideas about this file to release. === Contents for the iso (comments are below for every section) /packages /packages/core /packages/core-hardfp * directories where store core packages /packages/opt /packages/opt-hardfp /packages/xorg /packages/xorg-hardfp /packages/efikamx /packages/efikamx-hardfp * directories where store more collection packages (maybe optional) * efikamx has his own dedicated packages /boot /boot/efikamx /boot/efikamx/boot.script /boot/efikamx/build.sh * directories with config files for the bootloader (u-boot, ...) - boot.script: it's used to generate boot.scr, required for the bootloader u-boot to boot - build.sh: script that generates uImage and uInitrd from zImage and initrd.gz /initrd /initrd/initrd.gz /initrd/initrd.gz-hardfp * directories with generated initrd images /kernel /kernel/efikamx/zImage-2.6.31.14.22-efikamx_20110510 /kernel/efikamx/zImage-2.6.31.14.22-efikamx-hardfp_20110510 /kernel/efikamx/linux-2.6.31.14.22-efikamx_20110510.tar.bz2 /kernel/efikamx/linux-2.6.31.14.22-efikamx-hardfp_20110510.tar.bz2 /kernel/efikamx/modules-2.6.31.14.22-efikamx_20110510 /kernel/efikamx/modules-2.6.31.14.22-efikamx-hardfp_20110510 * direcories with kernel images, sources and modules per device /tools/ /tools/mkimage * directory with tools which could be required to create the installation media /install/setup /install/setup.dependencies * directory with files for the installation - setup: install script - setup.dependencies: file that contains all dependencies for the packages in the installation media. At least is required to have all dependencies for core If other collections will be used then this file should have all the deps for that /crux-media * file required to identify the installation media. Contents like: "2.7-20111020" * also identifies the iso === Features that could be added as optional or in the future it would be easy to add more devices like the sheevaplug to this structure i.e: /boot/sheevaplug/*, /kernel/sheevaplug/* also it would be easy to add an another optimization i.e: /packages/core-armv5te, /packages/core-armv7l, ... === How can I create an installation media? Example for the efikamx device (hardfp): 1 - Download the iso image or the tarball (CRUX-ARM-2.7.iso or maybe CRUX-ARM-2.7.tar.bz2) 2 - Access to contents a) For the iso you sould burn the image to a cdrom and mount it to a directory ($ISO_DIR) b) Or you could mount (-o loop ...) directly the iso image to a directory ($ISO_DIR) c) For the tarball you should untar contents to a directory ($ISO_DIR) For all those cases above we used the variable $ISO_DIR as the dir where contents are 3 - Prepare (partition, format filesystems, mount) your media installation device We used the variable $MNT_DIR as the dir where the media installation device is mounted 4 - Copy files to them 4.1 - Essential stuff # cp $ISO_DIR/crux-media $MNT_DIR 4.2 - Boot stuff (bootloader files, kernel image and initrd image) 4.2.1 - Copy files # cp $ISO_DIR/boot/efikamx/* $MNT_DIR # cp $ISO_DIR/kernel/efikamx/zImage-2.6.31.14.22-efikamx-hardfp_20110510 $MNT_DIR/zImage # cp $ISO_DIR/initrd/initrd.gz-hardfp $MNT_DIR/initrd.gz 4.2.2 - Configure the bootloader # cd $MNT_DIR # ./build.sh To execute the build script you'll need mkimage on your $PATH Some distros like debian has a package for that called uboot-mkimage, but if not you could use the one provided in the iso. For that you sould do something like: # install -D -m 0755 $ISO_DIR/tools/mkimage ~/bin/mkimage # export PATH=$PATH:~/bin 4.3 - Kernel sources and modules # mkdir -p $MNT_DIR/crux/kernel # cp $ISO_DIR/kernel/efikamx/linux-2.6.31.14.22-efikamx-hardfp_20110510.tar.bz2 $MNT_DIR/crux/kernel # cp $ISO_DIR/kernel/efikamx/modules-2.6.31.14.22-efikamx-hardfp_20110510 $MNT_DIR/crux/kernel 4.4 - Packages # mkdir -p $MNT_DIR/crux/core # cp $ISO_DIR/packages/core-hardfp/* $MNT_DIR/crux/core 4.5 - Files required for the installation (without those files you can still use the media you created for rescue tasks) # cp $ISO_DIR/install/* $MNT_DIR/crux === More ideas we could create a tiny documentation for covering every device installation: i.e: doc/INSTALL.efikamx, doc/INSTALL.efikamx-hardfp, doc/INSTALL.qemu, ... those docs would help us to create the wiki documentation, and also to wrote scripts that perform the installations ... === End of notes :D Well, what do you think about? Regards, -- Jose V Beneyto | http://sepen.mine.nu/

2 1

crux-armhf for efikamx
by acrux 14 Oct '11

14 Oct '11

I got it. This first (internal) release built on EfikaMX is ready. This full hardware floating point release still includes only core packages (and some opt too) and it has been started from scratch 'cause ABI incompatibility. Here the full work: http://cruxppc.org/~acrux/arm/2.7-HARD/ crux-armhf-2.7-test0-2G_image.xz (935M) - it's a full working MMC image of my machine that does use ilenia as ports manager and overlay supervisor. Thus a 'man ilenia' could help. It has the serial console and sshd enabled and a static IP (192.168.0.211). The 'root' pasword is 'cruxppc' as i've a lot of devel machines from CRUX PPC project and we use to have the same root password everywhere. The arm ports tree overlay is located 'as local' in /usr/ports/arm . arm-ports.tar.bz2 (634K) - it's an archive with ports from the arm overlay core.tar.bz2 (95M) opt.tar.bz2 (20M) pkg.list (3.0K) - they're archives with the built packages to install as chroot. crux-armhf-rootfs-2.7-test0.tar.bz2 (107M) - it's a clean system like the official way. linux-2.6.31.14.23-efikamx_20110610.tar.bz2 (63M) linux-2.6.31.14.23-efikamx.config (57K) - it's the last kernel from genesi git uImage (3.3M) bootkernel-modules.tar.bz2 (1.7M) - they'are boot kernel and modules/firmware Known issues: 1) wrong file-5.07's output (like on PowerPC) for some kind of files type. e.g. root@efikamx:/mnt/DEVEL# file mio mio: DOS-executable ( root@efikamx:/mnt/DEVEL# md5sum mio ba52d7e6f0c41a7bcaf49a216864e34a mio instead it should be.. acrux@killer:~$ file mio mio: Linux rev 1.0 ext2 filesystem data acrux@killer:~$ md5sum mio ba52d7e6f0c41a7bcaf49a216864e34a mio 2) alsa-utils does build but segfault cheers, --nico -- GNU/Linux on Power Architecture CRUX PPC - http://cruxppc.org/

2 11

[ANN] CRUX-ARM 2.7 released
by Victor Martinez 21 Sep '11

21 Sep '11

Hello all, CRUX-ARM 2.7 is now released. It can be found in the dowload section [1]. The changelog can be found here [2] We did a test cicle and it seems to be working right. The only thing to take care is udev, which its update can break some devices (efikamx). All feeedback, opinions and bug reports are welcome. Best regards, CRUX-ARM team. [1] http://crux-arm.nu/Main/Download [2] http://crux-arm.nu/Documentation/Changelog --- Learning bit by bit Victor Martinez | http://lokalix.dyndns.org

2 1

Crux, Armedslack and Compiling an X driver!
by lee jones 13 Sep '11

13 Sep '11

Hello all :) I know this might be a strange thing to ask here about a different linux distro, but I was just wondering as I'm trying to make this work. I've seen that crux linux runs on the efika mx smartbook and has an x windows driver compiled for it. On the distro I'm trying to use (armedslack) there is no driver, instead the efika mx smartbook in question uses only the inbuilt (presumably into the kernel) vesa driver. What I was wondering is how the x window driver for the efika mx was created? From what I've read it uses at least one propietary part and the files xf86-video-imx and libz160. Can anyone here please tell me if I need any additional pieces and how the driver in crux was created? thanks ljones

2 1

Meeting proposal.
by Victor Martinez 20 Jul '11

20 Jul '11

Hello all, I would like to propose a meeting this week. I think it could be fine this Wednesday (2011/07/20) at 19:00 GMT in #crux-arm. I start the little list with points to discuss and talk about. 1.- 2.7 release: I would like to finish this task, closing perl cross-compilation problem and releasing the new relase candidate for the 2.7 version. The test1 relase is working really well here, but there weren't any reports from other people. 2.- HardFP: This point is really important for me too. We need to make a plan to see how to act with this topic. It would be great to perform the needed server setup to give acrux permission to start working there, and let him put all his good job in the server, keeping all the work together in one site. 3.- Open for suggestions (may be the installer sepen?) Feel free to comment this topics and make changes in proposed date if it's needed. Waiting your comments, suggestions or opinions. Best regards, Victor. --- Learning bit by bit Victor Martinez | http://lokalix.dyndns.org

3 2