Thanks for that link, Thierry. I think that you've written one of the more detailed pieces of documentation. Part 4 [Linux Kernel Configuration Build] I think is pretty generic and handbook worthy. Would sure have saved me a lot of time. I think that would be useful to place at https://crux-arm.nu/Documentation/BuildingKernels
Any reason why you decided to use Arch Linux and then replaced it? Why not use a more 'from scratch' method, like: a. compile u-boot b. compile kernel [mailine or some patched version from the odroid community] c. download / cross-compile rootfilesystem. d. prepare boot media. Any reason why you didn't use the mainline kernel? I could be wrong, but I saw it has "OK" support now? Robin Krens ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, May 17, 2019 2:04 AM, Thierry Moreau <[email protected]> wrote: > On 16/05/19 06:44 AM, Robin Krens wrote: > > > Dear CRUX-arm users, developers, > > Over the last couple months, I have been playing around with CRUX-arm. > > One of > > things I noticed is the lack of a handbook or general approach for > > CRUX-arm. > > I'm aware of the difference with x86 and that there is no one size fits all > > solution. It could be the lack of documentation, but I think as of now, > > CRUX-arm > > goes against the main CRUX philosophy. The KISS principle, handbook and > > simple > > package management are, I think, the strong points of CRUX. > > For most supported boards, however, it seems it is impossible to > > redo/retrace > > the steps, compile a bootloader/kernel and have a basic working system. With > > "basic working system" here I mean something that boots and has basic > > funtionality (i.e. networking and usb storage). Referring to the x86 > > handbook > > (installation section) it just mentions how to enable some basic > > options（CONFIG_SATA_AHCI=y， CONFIG_BLK_DEV_SD=y，CONFIG_EXT4_FS=y）to > > bring up > > your root filesystem. Maybe your graphics cards or webcam doesn't work. > > Doesn't > > matter. CRUX is targeted for the experienced user. They will figure it out. > > Comparing this to the ARM branch of CRUX, most supported boards just > > provide a > > bootloader and kernel image. But I have no idea what these kernels are > > about. > > Are these basic configurations? Or are these copies from armbian just to > > work > > out of the box? Again, this could be a lack of documentation and > > misunderstanding on my side. But I would like to see a clearer approach. > > Maybe > > some devices on your board don't work, doesn't matter, at least it is more > > elegant. Again, I think CRUX is for the experienced user. Users that want a > > fullblown and fast working system, will swander off to armbian anyway. > > I would like to hear other people's opinions about the above mentioned > > points. > > Besides that, I willing to work on a general handbook for ARM. > > If you look at > https://crux-arm.nu/Main/Documentation > and then at > https://crux-arm.nu/SupportedDevices/Odroid-C2 > then you get an URL to > http://www.connotech.com/crux_arm64_odroidc2.html > which might be a helpful. > > (I'm the author of this contribution.) > > I did cross-compile the ARM (64 bits) Linux kernel. > > I remember having managed to install X.11 and natively compile quite a > few packages (an NFS swap space was needed for the larger ones). This > was after the above document was posted. > > "Hope it helps!" > > - Thierry Moreau > > > Sincerely, > > Robin Krens > > > > crux-arm mailing list > > [email protected] > > https://crux-arm.nu/mailman/listinfo/crux-arm _______________________________________________ crux-arm mailing list [email protected] https://crux-arm.nu/mailman/listinfo/crux-arm
