after playing around with the C2 for a week,I'd like to share my experiences:
U-Boot
- The C2 u-boot support loading files (kernel image, dtb, etc.) from USB devices directly, but loading speed is terrible slow (USB 1 low speed?)
- The internal timer seems to be not adjusted, the bootdelay counts down to 0 really fast
- The bootargs/systemd parameter for automatic fsck should be fsck.repair=yes instead of fsck.fix=yes (/media/boot/boot.ini)
- It takes a couple of minutes until ntpd will set the correct time after boot
- Debootstrap needs manual tweaking in order to create another debian/ubuntu rootfs
- Docker refuses to start, most likely due to broken apparmor profiles
- Automatic setting of timezone information fails to whatever reason
- update-initramfs creates broken/incomplete images
- Simply too old (e.g. mkimage doesn't know about arm64 platform)
- boots up fast
- Docker runs nicely, almost ... some kernel oops (aufs related) appear
- Docker builds from source without any hassle
- package lzop isn't available for arm64, but it isn't needed to build a kernel anyway
- fw_printenv is broken (but the Ubuntu binary runs fine with Debian)
- boots up nicly
- needless to say that Docker runs out of the box
- succesfully patched for aufs support
- CONFIG_DEBUG_INFO switch tends to blow up uInitrd
- update-initramfs needs additional hooks to include fsck.ext4 support (needed to invoke fsck from initrd during boot)
Code: Select all
debian@c2:~/kernel/3.14$ cat /etc/initramfs-tools/hooks/e2fsck.sh #!/bin/sh . /usr/share/initramfs-tools/hook-functions copy_exec /sbin/e2fsck /sbin copy_exec /sbin/fsck.ext4 /sbin
- C2 GPIO PIN layout: is it identical to the C1/C1+? With 3.3 voltage level as well?
PS: I'm not sure if a forum is the right place/tool to raise and manage issues. May be tools like JIRA or github will do a better job for this particular kind of tasks.