Everything just sounds so complicated...feelslikeautumn wrote: ↑Mon Apr 09, 2018 10:19 amDiscussion on fedora mailing list - https://www.spinics.net/linux/fedora/fe ... 11918.html
What does "DT" and "beta freeze" mean? I guess it's not relevant to RPi....Everything is in Fedora 28+ now.... well almost. The 4.16rc6 kernel
has a bootable DT, that's not yet in the F-28 nightly images though
due to the beta freeze.
What "bits" that were not present before? "Per usual" meaning copy over the firmware files to the first partition?There's all the bits in the firmware/u-boot though. So on a F-28
nightly image if you set a card up as per usual for a Raspberry Pi 3
and then do one other command it'll boot.
I am totally lost... did not get any of that... what is a "DT"? What does "3plus" mean? How to upgrade the kernel? To what and why?Once you've set up the card all you have to do is copy the RPi3 DT to
a 3plus DT and it'll do an initial boot. Once it's booted you can then
just upgrade the kernel and it'll be fine moving forward.
On ARMv7 basically do the following:
cp <BOOT mount point>/dtb-kernel-4.16.0-0.rc4.git0.1.fc28/bcm2837-rpi-3-b.dtb
<BOOT mount point>/dtb-kernel-4.16.0-0.rc4.git0.1.fc28/bcm2837-rpi-3-b-plus.dtb
cp <BOOT mount point>/dtb-kernel-4.16.0-0.rc4.git0.1.fc28/broadcom/bcm2837-rpi-3-b.dtb
<BOOT mount point>/dtb-kernel-4.16.0-0.rc4.git0.1.fc28/broadcom/bcm2837-rpi-3-b-plus.dtb
Unmount boot and continue as usual.
Once it's running if you update the kernel to rc6 you should be
running just fine. One other thing to note is there's some different
bits needed for the wifi. I'm going to put all of those, inc the one
needed for the original Pi3, into an rpm but I've not had a chance to
do that as yet. Give me a day or so and I'll likely get that done.
Maybe the lack of user-friendly documentation is a sign that this process is not quite ready for public consumption?
Personally, I think it's because the RPi3 - lacking a proper bios - makes it difficult to install any operating systems other than the default one. So, on top of being faced with the problem of not being able to run live USB/DVDs, the gatekeepers leave no clear instructions on how to get an ARM64 os on 2 partitions (one of them being the RPi firmware; the other the file system). It's all smoke and mirrors.
It's not that difficult, just takes a while to get it done and tested. Loads of people have released their own distro's. There's always a time gap when a new product that needs new firmware and drivers is released, to catch up.gilius wrote: ↑Mon Apr 09, 2018 7:59 pmPersonally, I think it's because the RPi3 - lacking a proper bios - makes it difficult to install any operating systems other than the default one. So, on top of being faced with the problem of not being able to run live USB/DVDs, the gatekeepers leave no clear instructions on how to get an ARM64 os on 2 partitions (one of them being the RPi firmware; the other the file system). It's all smoke and mirrors.
Users browsing this forum: No registered users and 3 guests