Preparing the release CRUX-ARM 2.6
Hello, thinking in the first release of CRUX-ARM 2.6. What do you think to make it for next week? The 4th CRUX-ARM release candidate (RC4) has been tested for both, no-eabi and eabi. The current status for them is quite good: no-eabi: It's working fine on Jornada 720 (with a 2GB compact flash card, at the moment there are some problems[1]) and versatile (qemu) eabi: It's working fine on ipaq 191x, htc-prophet (qtek S200), htc-elf (htc Touch) and versatile (qemu). Suggestions, comments and opinions are welcome. Regards, Victor. [1] There are problems trying to run it in a 4GB compact flash. Working on progress about this topic.
Hi Victor, On 05/12/10 11:53, pitillo@crux-arm.nu wrote:
Hello, thinking in the first release of CRUX-ARM 2.6.
What do you think to make it for next week? The 4th CRUX-ARM release candidate (RC4) has been tested for both, no-eabi and eabi. The current status for them is quite good: no-eabi: It's working fine on Jornada 720 (with a 2GB compact flash card, at the moment there are some problems[1]) and versatile (qemu) eabi: It's working fine on ipaq 191x, htc-prophet (qtek S200), htc-elf (htc Touch) and versatile (qemu).
Suggestions, comments and opinions are welcome.
Regards, Victor.
[1] There are problems trying to run it in a 4GB compact flash. Working on progress about this topic. Well I think the problem is only related to boot, so I tried 2 methods: with and without an initrd filesystem and seems that on boot time the kernel can't discover a valid hdX device and it returns a panic error. However I tried with the initrd and the problem persists, it can't discover them, but at least I can create some nodes (/dev/hda, /dev/hda1 and /dev/hda2), so it's possible to mount the rootfs for chroot.
I don't really know what is happening (for now ;D) but I'm sure we can't re-write the /etc/rc script for the initrd which should do these steps (discover block devices, create nodes, mount devices and chroot). What do you think? Anyways that shoud be developed separately so IMHO our release it's ready!! Greetings, -- Jose V Beneyto | http://sepen.mine.nu/
* Jose V Beneyto (sepen@crux-arm.nu) wrote:
Hi Victor,
Hello, thinking in the first release of CRUX-ARM 2.6.
What do you think to make it for next week? The 4th CRUX-ARM release candidate (RC4) has been tested for both, no-eabi and eabi. The current status for them is quite good: no-eabi: It's working fine on Jornada 720 (with a 2GB compact flash card, at the moment there are some problems[1]) and versatile (qemu) eabi: It's working fine on ipaq 191x, htc-prophet (qtek S200), htc-elf (htc Touch) and versatile (qemu).
Suggestions, comments and opinions are welcome.
Regards, Victor.
[1] There are problems trying to run it in a 4GB compact flash. Working on progress about this topic. Well I think the problem is only related to boot, so I tried 2 methods: with and without an initrd filesystem and seems that on boot time the kernel can't discover a valid hdX device and it returns a panic error. However I tried with the initrd and the problem persists, it can't discover
On 05/12/10 11:53, pitillo@crux-arm.nu wrote: them, but at least I can create some nodes (/dev/hda, /dev/hda1 and /dev/hda2), so it's possible to mount the rootfs for chroot.
I don't really know what is happening (for now ;D) but I'm sure we can't re-write the /etc/rc script for the initrd which should do these steps (discover block devices, create nodes, mount devices and chroot).
What do you think? Anyways that shoud be developed separately so IMHO our release it's ready!!
It's fine then, we can put RC4 in release state. About the other topic we can move the talk to a new thread and keep there the info and progress together.
Greetings,
Regards, Victor.
-- Jose V Beneyto | http://sepen.mine.nu/
_______________________________________________ crux-arm mailing list crux-arm@crux.arm.nu http://crux-arm.nu/mailman/listinfo/crux-arm Learning bit by bit Victor Martinez | http://lokalix.dyndns.org
Hi Victor, On 05/12/10 22:30, pitillo@crux-arm.nu wrote:
[...] It's fine then, we can put RC4 in release state. About the other topic we can move the talk to a new thread and keep there the info and progress together. As we talked in our irc meetings we had a little issue with wget related to openssl, but fortunately we solved the problem [1], so now we can safely upgrade this package and finally release 2.6 version.
Regards, [1] http://crux-arm.nu/gitweb/?p=ports/core-cross.git;a=commitdiff;h=f34e618166f... -- Jose V Beneyto
participants (2)
-
Jose V Beneyto
-
pitillo@crux-arm.nu