Port to new device guide

[xekarfwtos]

Hi everyone,

Is there a guide for porting ArchlinuxARM to new device?

I try to port ArchlinuxARM to mini6410 (http://www.friendlyarm.net/products/mini6410).

My first step is to create a toolchain for armv6.
I modified the xtools-dotconfig-v7 for armv6 but building the toolchain failed.

Thanks in advance for your help.

[WarheadsSE]

Ok, slow down Why is it you want to be building a full chain for armv6?

CPU: http://www.arm.com/community/partners/d ... ctId/2644/

[xekarfwtos]

I want to learn how to use crosstool-ng to build a toolchain.
If I want a toolchain for mini6410 I can use a prebuild one or build one with openembedded.
I found out in github that the porting guide is in TODO list.

[WarheadsSE]

Ok, but you are missing the point of the question:

Why do you want to build a full chain (not toolchain) for armv6? Although, I do recognize that that is an ARM11 armv6 with VFP, you need to be aware of the mountain you're climbing. So far, we've found that it is not worth it based on market saturation & performance gain (at this time) to do a complete v6 hard-float build out. (time, hosting, maintenance, target devices)

It can definitely be done, but we'll not the be the ones supporting it at this time. Also, we have nothing to do with OE. We can help you with the ct-ng setup, however "it failed" doesn't help.

There is essentially nothing to port aside from kernel & device drivers.

[xenoxaos]

For that kind of cost....why didn't you get a PandaBoard?

[xekarfwtos]

@xenoxaos I bought mini6410 + 4.3" TFT with touchscreen a year ago about 106 euro. I already have a beagleboard-Xm and I am waiting a Raspberry-Pi.

@WarheadsSE Ok, I see your point. I know that you have nothing to do with OE.

How can I port ArchlinuxARM in Mini6410?
Which are the steps I should follow?
I like the approach learn by doing. I want learn how ArchlinuxARM project works in order to help you with the project.

You are right, just a "failed" is not helpful. Please see the error below. If you want I can post a diff between your xtools-dotconfig-v7 and mine for armv6.
$this->bbcode_second_pass_code('', '[INFO ] =================================================================
[INFO ] Installing C library headers & start files
[EXTRA] Configuring C library
[ERROR] configure: error: support for the tls_model attribute is required
[ERROR]
[ERROR] >>
[ERROR] >> Build failed in step 'Installing C library headers & start files'
[ERROR] >> called in step '(top-level)'
[ERROR] >>
[ERROR] >> Error happened in: CT_DoExecLog[scripts/functions@172]
[ERROR] >> called from: do_libc_backend_once[scripts/build/libc/glibc-eglibc.sh-common@347]
[ERROR] >> called from: do_libc_backend[scripts/build/libc/glibc-eglibc.sh-common@143]
[ERROR] >> called from: do_libc_start_files[scripts/build/libc/glibc-eglibc.sh-common@60]
[ERROR] >> called from: main[scripts/crosstool-NG.sh@598]
[ERROR] >>
[ERROR] >> For more info on this error, look at the file: 'build.log'
[ERROR] >> There is a list of known issues, some with workarounds, in:
[ERROR] >> '/usr/share/doc/crosstool-ng/ct-ng.hg+default-c800b7d6a50c/B - Known issues.txt'
[ERROR]
[ERROR] (elapsed: 7:50.72)
[07:51] / make: *** [build] Error 1
')

[WarheadsSE]

As I've already said: kernel / modules / drivers. That is all.

As for the error, it appears you are missing some headers & sources.

[xekarfwtos]

What should I use as a rootfs for archlinuxARM?

Sorry, if I am annoying you with my questions.

$this->bbcode_second_pass_quote('', 'A')s for the error, it appears you are missing some headers & sources.

[WarheadsSE]

As for which rootfs: find out the version of the kernel, and if it supports devtmpfs & accept4. If it supports those, then use the main armv5te rootfs. If it does not, start with the oxnas rootfs.

The missing files are needed by the ct-ng and are not part of the rest of the system.

[xekarfwtos]

Is there a guide how to build the rootfs for archlinuxARM from start?