How do I use device tree overlays on Fedora (since there
is no "cape manager") ?
I assume I have to modify extlinux.conf to boot with a new device tree
file. Is there a way to use "dtc" to merge the am335x-boneblack.dts
file and the overlay file ?
FYI, the reason I ask this question is that I'm interested in CANbus.
I noticed that Fedora has CANbus drivers now. Great. I have a
BeagleBone Black (with Fedora 23 on a SD card) and a "Serial Cape"
from LogicSupply : http://www.logicsupply.com/cbb-serial/ . There are
device tree "overlay" files to enable this :
Yep, it's my report on the worst named arm computer, that runs good :)
Anyway I have two reports.
** 1st report **
From all my tests, the PCDuino3 Nano Light "just works". I installed
the F23 XFCE image, followed the uboot instructions with just one
change, I used the PCDuino3 Nano uboot, cuz Lite is supposed to be the
The graphical first-boot came up, I set it up, and XFCE came up. Not
a bit of extra twiddling on my part.
I am currently updating the system to see if it will automatically
boot into the newer kernel. Since the regular PCDuino3 Nano
automatically boots into the newer kernel, I am 99% confident this
will too. But I don't like to say it will without testing it.
echo "deltarpm=False" >> /etc/dnf/dnf.conf
Use that to speed up your update by at least 20 minutes.
** 2nd report **
PCDuino3 Nano Light is currently $15 on amazon.
CPU: AllWinner A20 SoC, 1GHz ARM Cortex A7 Dual Core
Full size HDMI port
1000 Mb/sec ethernet (take with a grain of salt, but it is faster than
SATA port (no cables)
SD card slot. Says it only handles 32Gig, I run mine with 64Gig sd cards
No on board flash - The big difference between Nano and Nano lite.
Sorry that I sound like an ad. It's just that it's a decent arm
computer that runs straight F23, for only 15 dollars.
I would like to introduce myself to the group. I have recently
received an IGEPv2 board , which is based on the Beagle Board, but
with wifi, bluetooth, ethernet, and more RAM. I'm still at the "wow,
it's tiny and it runs Linux" stage. I should get a bit more time over
the next month and Christmas to play around properly with it.
I'm new to embedded development, but neither new to Linux nor ARM
(writing my first ARM assembly some 15 years ago). However, for the
past 6 years I've not even built a Linux kernel, preferring to use the
default kernel in Fedora for simplicity :)
Firstly, a thank you to those involved in Fedora ARM for getting it to
this stage. If I get the time, I'd really like to contribute some
(probably small) effort to help get Fedora ARM working well on the
IGEPv2 and Beagle Board. As I progress, I'd like to know what I can
do to help.
In the meantime, I have some questions. Apologies in advance if these
1) There are various different kernels from different sources. I'm
used to there being a small set of "right" kernels (that is, Fedora's
idea of "right") for x86. I fully appreciate that different ARM-based
boards are quite different in capabilities (like different instruction
a) Is there likely to be some standardised vanilla Fedora ARM kernel
source? (Or is that simply the source RPM available for Fedora?)
Then patches /could/ be offered for the more common systems (e.g.
Beagle Board & clones, SheevaPlug).
b) Would it then make sense to offer these as pre-built RPMs for common systems?
c) Is there any guidance on which version is good to use as a base?
I've seen quite different kernel versions being used (from 2.6.27 to
2) I understand a little bit about the different calling conventions,
FP differences (e.g. soft FPU versus VFP), and instruction set
differences (v5 versus v7).
a) Can the kernel can be safely built with a different instruction set
targeted? (I know there are different optimisation options passed to
GCC. Apologies if this seems a bit newbie-ish.)
b) For FP-heavy programs (e.g. ogg encoding), is it possible to build
the packages with VFP/NEON but still get them to work in a soft FPU
system? I'd imagine any call to an external library would have to
somehow be defined to use a different calling standard.
3) There seem to be some missing dependencies in the packages in the
current Fedora ARM repository. For example, emacs is requiring
libotf, which doesn't seem to be there in the repository. And
likewise with the xorg-x11-font* packages needing ttmkdir. I'm
confused as to how the RPM could have been successfully built without
it. What am I missing?
4) I see there has been some discussion over unaligned data access.
(Oh, I remember that from the ARM2 days.) It seems as if the
Cortex-A8 cores allow unaligned data access when set up to do so .
Does this, in any way, help with the compatibility of packages
5) I've managed to get various source packages missing from the Fedora
ARM repositories to compile successfully (natively). I guess there is
a reason why there are not in the repos right now -- is that reason
down to time and priorities, or is there some blocking bugs with many
of these packages?
I look forward to being able to contribute something back into Fedora!
Oh, forget to involve the list. So resend this in case someone else needed.
On 12/29/2015 12:57 PM, Robert Moskowitz wrote:
> On 12/28/2015 10:51 PM, Zamir SUN wrote:
>> 1. BBB can boot up to system. And the current problem is display
>> (see bug1123618). If you do not use display (such as use the
>> minimal image)it should be totally fine.
>> 2. $ sudo fedora-arm-image-installer
>> Usage: fedora-arm-image-installer <options>
>> --image=IMAGE - xz compressed image file name
>> --target=TARGET - target board
>> --media=DEVICE - media device file (/dev/[sdX|mmcblkX])
>> --selinux=ON/OFF - Turn SELinux off/on as needed
>> --norootpass - Remove the root password
>> -y - Assumes yes, will not wait for confirmation
>> --version - Display version and exit
>> --resizefs - Resize root filesystem to fill media device
>> Example: fedora-arm-image-installer --image=Fedora-Rawhide.xz
>> --target=panda --media=/dev/mmcblk0 --selinux=OFF
>> Error: not found! Please choose an existing device.
>> So the image can be installed by the script.
>>  https://bugzilla.redhat.com/show_bug.cgi?id=1223618
>> On 12/29/2015 10:26 AM, Robert Moskowitz wrote:
>>> I did some more digging and MAY have my answer in:
>>> I see the script for am335x_boneblack
>>> If that is what the current method is, perhaps the wiki can be updated?
>>> On 12/28/2015 09:21 PM, Robert Moskowitz wrote:
>>>> I am trying to help out someone that has a BBB. I am looking at:
>>>> and the files referred to at:
>>>> do not exist.
>>>> What is the current status for BBB and F23?
>>>> thank you.
>>>> And is it covered in the fedora-installer-script? I don't see it in
>>>> the board.d directory. I do see some uboot files in the F23 image.
>>>> thank you
zsun in #fedora-zh #openshift on freenode.net