I know a number of people have asked about support for the venerable
Beagle xM over time and while it's booted and worked fine with DT
since 3.8 the usb and hence network has always been an issue.
So as of 3.14 all the bits for the Beagle xM are finally in and I have
my Beagle xM working with network etc... with one caveat, there's a
minor DT change needed for revisions A and B (C will work OOTB)
So I just thought I would put a quick straw poll out there for those
interested in making the xM work whether they are in the AB camp or
the C camp.
I just created an F21 Change for aarch64 emulation:
There's a good chance that qemu-system-aarch64 will be end user useful by the
time Fedora 21 starts taking shape, so I'll use that page to track making sure
it's all wired up correctly in Fedora, and make sure it gets some media
attention, etc. If things don't land in time we can just drop the page, the
actual heavy lifting is being done by linaro in qemu land.
Also, I submitted an abstract for a Flock talk about the general state of
arm/aarch64 virt and emulation. So if you see that on the proposal list, it's
Just thought I'd put this out on a dedicated thread for those that are
The process for the first boot on the GA images is slightly manual and
documented in the post above, in the next few days we'll get some
updates bits out to fix the issue properly moving forward and have the
fixes into rawhide nightlies RSN.
X/display output is the current main issue I'm aware of so you'll need
a serial console.
Let us know of any success, failure or other issues.
Thanks for your patience! There's some more learnt about booting ARM
here and we'll make sure the fix is integrated for any of the other
platforms this issue might affect.
I received an UDOO today (looking through the list, it looks like I would
have been better off with a Wandboard for the power (except for the Arduino
stuff, so that's good) oh well :) Anyway, I tried their Ubuntu images and
I'm simply not happy with them. It's been a while since I've used Ubuntu
(been using Fedora pretty much since I started at Red Hat), things are
unfamiliar and honestly they don't quite work right. I'd like to use
Fedora, but it looks like support is only in Rawhide at the moment. I'm
really not all that concerned with using Rawhide (though if I could
backport support to Fedora 20 that would be awesome), I just don't know
where to start. Could anyone give me any pointers or some links on how to
get started, please?
> Thanks, Robert.
> tps65217 was the clue I needed. Fedora config has it building as a
> module. But the module is not included in the initramfs, so not
> available at boot time.
> Solution: Either rebuild the Fedora kernel with
> "CONFIG_REGULATOR_TPS65217=y" or edit /etc/dracut.conf, 'add_drivers
> +="tps65217-regulator"' and rebuild initramfs/uinitrd, gets the Fedora
> kernel booting.
> Now need to figure out where the power management has gone. I suspect
> your kernels have it built-in and Fedora has "CONFIG_XXX=m", so more
> module nonsense.
Fedora's 3.13.x might still be missing these:
They should hit v3.15-rcX (fingers crossed)
Beyond that, advanced power-management (suspend) thru the cortex-m
firmware doesn't work outside of ti's v3.12.x branch anyways.