Comment 30 for bug 1805668

Adam: we are currently working on base support of the raspi3 boards based on the old work that was done for the raspi2 (and please note those did not get much love since a while anyway). The way they work right now is not perfect, but this is the first 'iteration' we intend to set as a baseline for further work. We're trying to get everything for that 'baseline' landed in bionic right now to make work on this easier (e.g. having daily builds etc). There are some things we could already do better but there's a tight time-frame we need to fit into.

To address some of your concerns: you probably checked an outdated flash-kernel since for the need of the beta images we have added Pi3 B+ support and a modified boot.scr for our uses. Currently both the boot partition and flash-kernel come with compatible bootscripts so there should be no conflict here. I also don't see how you tell that the config.txt generated by livecd-rootfs will not work. The config.txt we use in the boot partition in the current build scheme comes from the pi3 classic gadget tree and has device_tree_address=0x03000000, which is what all of our planned boot.scr for pi3 are using (both in the boot partition during image boot + what flash-kernel uses).

I would for now recommend to wait a bit until the base, surely far from perfect, images are ready and then we can all work together on getting a satisfying, clean raspi2/raspi3 experience. We are aware of the fact that the system architecture here is flawed - and we promise it will be made better. Especially now that Dave's around to help us out exactly with that.

What I would recommend: once we have all the 'beta' work landed, I most certainly recommend posting bugs about things that don't work or seem to work suboptimal and letting us know.