On Tue, Jun 7, 2016 at 4:41 PM, Andreas Reschke <arm_ml@xxxxxxxxxxx> wrote: > Am 13.05.2016 um 19:00 schrieb Peter Robinson: >> On Fri, May 13, 2016 at 5:53 PM, Andreas Reschke <arm_ml@xxxxxxxxxxx> wrote: >>> Am 05.05.2016 um 11:18 schrieb Peter Robinson: >>>>>>>>>> Hi there, >>>>>>>>>> now the board is on my table. >>>>>>>>>> >>>>>>>>>> The only image i've found is >>>>>>>>>> linaro-desktop-cubietruck-plus-card-dp-v1.1.img. But I don't think its >>>>>>>>>> a >>>>>>>>>> real aarch64 Image: >>>>>>>>>> >>>>>>>>>> linaro@cubietruck-plus:~$ uname -a >>>>>>>>>> Linux cubietruck-plus 3.4.39 #7 SMP PREEMPT Tue Mar 1 09:34:33 CST >>>>>>>>>> 2016 >>>>>>>>>> armv7l armv7l armv7l GNU/Linux >>>>>>>>>> linaro@cubietruck-plus:~$ >>>>>>>>>> I think this should be armv8l ? >>>>>>>>>> >>>>>>>>>> Is there any howto to create/build a aarch64 Image on a Cubieboard 5 >>>>>>>>>> with >>>>>>>>>> Fedora ? >>>>>>>>> >>>>>>>>> Is this a real aarch64 board? As far as I can tell [1], although their >>>>>>>>> website is terrible on the details, it's a ARMv7 device not a aarch64 >>>>>>>>> device. >>>>>>>> >>>>>>>> It is only armv7 I have one at home, last I tried it there was some >>>>>>>> issues >>>>>>>> still. I will try when I get home and see how it works now. >>>>>>>> >>>>>>>> Dennis >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> arm mailing list >>>>>>>> arm@xxxxxxxxxxxxxxxxxxxxxxx >>>>>>>> http://lists.fedoraproject.org/admin/lists/arm@xxxxxxxxxxxxxxxxxxxxxxx >>>>>>> >>>>>>> Hi Dennis, >>>>>>> that would be fine. >>>>>>> >>>>>>> Greetings >>>>>>> Andreas >>>>>> I put last nights rawhide minimal image on, the output was serial port >>>>>> only. >>>>>> HDMI had nothing, I do not have a monitor with DP support so I can not see >>>>>> if >>>>>> something is coming out there, the system booted but hung when it got to >>>>>> [ OK ] Reached target Basic System. >>>>> >>>>> The CubieTruck Plus uses an A83T for which only quite minimal support is >>>>> in the upstream kernel. mmc support still is waiting for merging, so no >>>>> rootfs, so this makes sense. >>>>> >>>>> Also no video output support whatsoever yet. >>>> Yes, so with Dennis actually having a device the boot is to what we >>>> should expect, it actually boots and you get serial output but the >>>> device is not actually useful at the moment without >>>> storage/usb/network. >>>> _______________________________________________ >>>> arm mailing list >>>> arm@xxxxxxxxxxxxxxxxxxxxxxx >>>> http://lists.fedoraproject.org/admin/lists/arm@xxxxxxxxxxxxxxxxxxxxxxx >>> Hello , >>> >>> Update: I've taken the Image >>> Fedora-Minimal-armhfp-Rawhide-20160511.n.0-sda.raw.xz >>> >>> With the USB-Serial-Cable connected: >>> ....... >>> Feb 11 16:31:59 localhost dracut-initqueue[396]: Warning: >>> dracut-initqueue timeo >>> Feb 11 16:31:59 localhost dracut-initqueue[396]: Warning: Could not boot. >>> Feb 11 16:32:00 localhost systemd[1]: Received SIGRTMIN+20 from PID 398 >>> (plymout >>> Feb 11 16:32:00 localhost dracut-initqueue[396]: Warning: >>> /dev/disk/by-uuid/7b7f >>> Feb 11 16:32:00 localhost systemd[1]: Starting Dracut Emergency Shell... >>> Feb 11 16:32:01 localhost audit[1]: SERVICE_STOP pid=1 uid=0 >>> auid=4294967295 ses >>> Feb 11 16:32:01 localhost systemd[1]: Received SIGRTMIN+21 from PID 398 >>> (plymout >>> Feb 11 16:32:01 localhost kernel: audit: type=1131 >>> audit(1455208321.060:14): pid >>> dracut:/# >>> >>> How it's going on? Is there anything I can help to support this board? >> >> Basically we need to get the support upstream. We generally don't pull >> in custom patches for board enablement, but rather support what is >> upstream because we just don't have the resources to do that for the >> 100s of ARM SBCs out there. >> >> Peter >> _______________________________________________ >> arm mailing list >> arm@xxxxxxxxxxxxxxxxxxxxxxx >> http://lists.fedoraproject.org/admin/lists/arm@xxxxxxxxxxxxxxxxxxxxxxx >> > > Question: when will be A83T mmc support available in Fedora Kernel? I > see patches from Januar and Februar for the Vanilla Kernel. Just because you see patches, doesn't mean they've been accepted for upstream inclusion, just for review. We support the vast majority when ever it lands in an upstream mainline kernel. So in the case of rawhide that's usually with in a day or two of Linus landing the pull request. In the case of a stable Fedora release the kernel team normally push a new kernel to the stable releases around the .2 stable release but that varies a little with each kernel cycle. With a quick look it looks like only some of the bits for the MMC (clocking/regulators) on sun8i/a83/cubie 5 have landed upstream in 4.7 so it's still not in a usable state so it would be 4.8 at the earliest. Peter _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/arm@xxxxxxxxxxxxxxxxxxxxxxx
