Summary of Fedora on Odroid XU4
1. with Kernel 4.6.5-300.fc24 system boots without failure, but update
to newer kernel fails due dracut didn't build suitable intramfs
https://bugzilla.redhat.com/show_bug.cgi?id=1482825
2. newer kernel works only with "cpuidle.off=1" inserted into the
"append" kernel line in the /boot/extlinux/extlinux.conf file, but all
USB3 Hosts failed, no onboard ethernet
3. To boot the system from the eMMC card:
A. The initramfs image file must be rebuilt. The simplest way is to:
a. Boot up using the MicroSD card;
b. Partition the eMMC card such that partition 1 begins on sector
3072
(Default starting sector from fdisk is 2048). There should be
4 partitions created;
c. Mount the Fedora image desired to be installed on the eMMC
card;
d. Copy all partition data from the mounted fedora image
partitions (there are 4 for Fedora 26 ARM images) to the appropriate
eMMC partitions;
e. Update the UUID values on what will be the
/boot/extlinux/extlinux.conf file and /etc/fstab files of the eMMC card;
f. Assuming the eMMC partitions are mounted as such --
mount /dev/mmcblk1p4 /mnt
mount /dev/mmcblk1p2 /mnt/boot
then perform the following mounts --
mount -o bind /proc /mnt/proc
mount -o bind /dev /mnt/dev
mount -o bind /sys /mnt/sys
B. Rebuild the eMMC card's initramfs by executing the following
command:
chroot /mnt dracut --add-drivers='pwrseq_emmc mmc_block'
/boot/initramfs-4.11.8-300.fc26.armv7hl.img 4.11.8-300.fc26.armv7hl
C. Flash the boot information in the header of the eMMC card;
C. Shutdown the system, then remove the MicroSD card;
D. Boot up using the eMMC card.
4. If the system is to be updated using "dnf update", a new initramfs
image must again be generated. This can be done using steps 1f - B.
above using the new initramfs and kernel images provided by the "dnf
update".
----------------------------------------------------------------
Note to the developers/maintainers of dracut:
The kernel modules "pwrseq_emmc" and "mmc_block" should be included in
dracut for the Odroid-XU3 and Odroid-XU4 such that the user need not
have to execute this procedure each time and update to the system is
performed.
Is this correct and complete ?
Andreas

Hello,
I try to activate the spi on my raspberry3 using a fedora 26.
I tried these options:
device_tree_param=spi=on
dtoverlay=spi-bcm2708
I use this kernel:
4.12.5-300.fc26.armv7hl
I see that the support in kernel seems already inside:
CONFIG_SPI=y
# CONFIG_SPI_DEBUG is not set
CONFIG_SPI_MASTER=y
But I never see the devices /dev/spi* appearing.
I can't see any messages regarding spi in dmesg.
I tested with a raspbian and I see them correctly.
I think I miss somethiing.
Could you help.
Thanks.

As we are getting closer to the F27 Final release, I would like to ask
members of the ARM SIG to revisit and finalize Talking Points for the
F27 ARM release. This helps not only the community Marketing team, but
also Ambassadors who arrange release parties and evangelize the
release worldwide.
[1] https://fedoraproject.org/wiki/Fedora_27_talking_points#Fedora_ARM
Thank you,
Jan
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic