* Ryan Mullen (rmull@rmull.com) wrote:
Hello,
Hey Ryan,
Attached are two patches that should enable a CuBox device to be supported by the CRUX-ARM git kernel and uboot.
You may read the procedure I follow (once these patches are applied) here[0] to verify that I'm doing the right thing.
I've took a look to the procedure and it's fine, as described at docs but using hardfp toolchain, which is right too IMHO.
You may download a kernel tarball here[1] and a kernel config here[2] if you are interested in hosting them in the CRUX-ARM distfiles. These are not stored permanently at the moment though we can discuss something if device maintainers will be expected to host their own files.
Currently we need to talk about hosting, as we haven't too much space, but for those kind of things is right to host them. You are using the same scheme we use in current supported kernels and you are packaging it as a xz file (we are using tar.bz2 and for next snapshots we'll change it to be xz files too).
The original kernel sources are from https://github.com/vDorst/linux/tree/CuBox-v3.5.3-Patched but there has been activity in the repo since the snapshot was taken.
I'll get your current snapshot to keep it hosted at crux-arm.nu as other device's kernel sources. Currently, it has more sense than making another snapshot which isn't curretly tested with these last sources. In cubox's case, you'll be the maintainer and if you need to update the kernel source, you can repackage and test it again, letting us know about the tests results and newer sources location to get and put them in crux-arm.nu. We can talk by mail or any other way to sync newer sources with a kernel version bump in git. Furthermore, related to kernel, we provide a zImage/uImage (depending on device needs) and the modules packaged too (this has been done so far manually, but we are adopting another unified and automated method in 2.8 branches).
Testing has been light, since I've been unable to install a full userspace. I've been using this kernel with my old install and I haven't noticed any issues that could be attributed to the kernel.
As we talk in irc channel, you can deploy efikamx's rootfs in your device's internal/external storage (you should know more about which methods are available currently for cubox) and as they share the same arch and fpu, it should run right too. We are currently updating documentation to let others know about some methods to install CRUX-ARM into supported devices. Soon, this new docs will be available and we'll try to follow a pattern to make newer ones for future devices. May be this can be interesting to make a new documentation wikipage for this device too.
I'm not sure what the policies for the kernel configs are - I tend to use as few modules as possible and strip out support for things like USB network adapters, which might be useful for people performing installations. I've shipped it as-is.
We try to provide a full device support inside the kernel and we try to add the modules that we think are interesting. We don't like too much support for a start point. All kernel configs are open to all people to ask to add/remove any kind of support that could be interesting for all people, but not personal things. As you told, we try to strip them too.
Regards, Ryan
I think the only needed files to make the push in cubox.git 2.7 are the final binary (uImage) and modules snapshot packaged. If you can provide a link to get them and put directly in crux-arm.nu, I think it would be perfect. Very good job. Thank you very much. I hope, you can put hands on your device and CRUX-ARM to be the current and main developer/maintainer for this device (kernel and future cubox overlay ports tree) Kind regards, Victor. --- Learning bit by bit Victor Martinez | http://lokalix.dyndns.org