On 2015-12-01, Ian Campbell wrote: > On Tue, 2015-12-01 at 16:10 +0000, Mark Morgan Lloyd wrote: >> > With respect to mainline kernel support, this page shows a pretty good >> > picture: >> > http://elinux.org/RPi_Upstreaming >> > >> > Many of the drivers are already upstreamed or queued for 4.4. >> >> So is there a chance it will be supported by "Stretch", or will it be >> whatever comes after that? > > If someone does the work there's no reason it couldn't make Stretch, > the freeze isn't until the second half of next year. > > I guess the first step in "doing the work" would be tested patches to > enable the relevant drivers etc in the .config for the armmp package > filed as wishlist bugs against src:linux package, once trunk hits 4.4 > if that's a prerequisite. The .dts files for rpi2 haven't even hit linux-next, no idea when they'll be posted. I tried a kernel build with ~120 patches from the raspberry pi git repository, but the .config ended up disabling most other platforms, so didn't seem suitable for an armmp variant. Perhaps it's just a matter of enabling the right options... So, "doing the work" requires a fair amount of upstreaming yet... > The only sticking point I can see up front is many of the blobs in > /boot/firmware are non-free (right?), which means they can't really be > in Debian, only in the non-free repository, which has an impact on the > production of SD-card images and maybe d-i too, I suppose. Yes, this is a big downside. That said, it wouldn't be hard for users to download the netboot kernel + initrd and load them from config.txt. I did set up an rpi2 for one of the armhf build nodes for the reproducible builds project. It used the non-free firmware, an rpi2 build for u-boot (mainline worked fine), and a kernel built with ~120 patches from the raspberry pi foundation git repository. Haven't tested anything other than microSD, USB, and serial console, really, so maybe missing important features such as HDMI... live well, vagrant
Attachment:
signature.asc
Description: PGP signature