this is really cool
the only thing i'd change is use dkms to have the gpiomem module built
automatically on kernel upgrades
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code
the complicated manor in which i would go about figuring this out would be as
such:
boot into raspbian with the default led settings, then use dtc to dump the
active device tree into a dts file
dtc -I fs -O dts -s /proc/device-tree > ~/led1.dts
reboot, but this time with desired led settings in
> (do I have to copy/paste what you provided into your post ?)
yes, save that into bcm2837.dtsi.diff
>I am running aarch64, so do I have to play with arm or arm64 ?
the instructions should also work for arm64 systems
>When going into arch directories I have no dts file at all ? Did I miss
fortunately you don't have to compile the kernel completely, just generate a
single dtb in the sources
and that diff --git is just part of the output of a git diff, you need to: dnf
install patch dtc gcc
cd /usr/src/kernel/4.16.3-300.fc28.aarch64/
patch -p1 < /tmp/bcm283x.dtsi.patch
cd
you're going to have to opt for a more manual installation procedure since
pimoroni's install method assumes you're using raspbian, and has more
debianesque methods built-in
first, the eariler patch i posted for bcm283x.dtsi to generate
bcm2837-rpi-3-b.dtb will get spidev enabled on fedora
things i should have probably asked first:
have you tried the unicorn hat in raspbian, is it functional?
which unicorn hat is it exactly, which pins are you using?, because it looks
like there are ones that use spi0 and others spi1
and as for spi:
spi@7e204000 is spi0
spi@7e215080 is spi1
>How did you build the dtb from dts ?
get the kernel source
apply patch
diff --git a/arch/arm/boot/dts/bcm283x.dtsi b/arch/arm/boot/dts/bcm283x.dtsi
index ac00e730f898..1bcbd98ed1c2 100644
--- a/arch/arm/boot/dts/bcm283x.dtsi
+++ b/arch/arm/boot/dts/bcm283x.dtsi
@@ -376,6 +376,14 @@
for the sake of completeness:
diff --git a/arch/arm/boot/dts/bcm283x.dtsi b/arch/arm/boot/dts/bcm283x.dtsi
index 9d293decf8d3..d32d4861c98d 100644
--- a/arch/arm/boot/dts/bcm283x.dtsi
+++ b/arch/arm/boot/dts/bcm283x.dtsi
@@ -26,2 +26,3 @@
serial1 =
+ ethernet1 =
on the command line you can modify the device tree blobs with fdtget/fdtput
to get the status of any given node:
# fdtget /boot/dtb/bcm2837-rpi-3-b.dtb /soc/spi@7e204000 status
disabled
to change the status of the node
# fdtput --type s /boot/dtb/bcm2837-rpi-3-b.dtb /soc/spi@7e204000 status okay
to quote the fedoraproject wiki on the raspberry pi:
Are Device Tree Overlays supported?
There's basic support for overlays in u-boot and the linux kernel but an
overlay manager isn't yet upstream. There's (sic)
Is GPIO supported?
GPIO isn't supported well as they need to be mapped with Device
10 matches
Mail list logo
