**** BEGIN LOGGING AT Wed Jun 20 03:00:08 2018 Jun 20 03:04:35 https://puri.sm/posts/librem5-solving-the-first-fsf-ryf-hurdle/ Jun 20 03:19:34 I am not convinced this particular loophole makes a difference in terms of the openness of the hardware (even if the FSF is happy with it). Jun 20 03:20:02 But in saying that, I dont think anyone makes a smartphone capable SoC that doesn't need binary blobs of some form. Jun 20 03:21:05 I think it is ridiculous that just moving the blobs around makes it FSF-free Jun 20 03:21:47 the secondary processor exception should apply to the DDR PHY no matter where the blob for it is installed Jun 20 03:24:56 I am surprised there isn't more work done to reverse engineer something like that or are there things that make doing so difficult? Jun 20 03:26:14 I read in the Phoronix forums that the POWER9 code is open and that coreboot folks reversed DDR3 stuff on x86 Jun 20 03:26:23 https://www.phoronix.com/forums/forum/phoronix/latest-phoronix-articles/1031488-purism-s-librem-5-to-rely-on-secondary-processor-for-binary-blobs#post1031520 Jun 20 03:27:07 I am guessing that there might well be pressure from the makers of the SoC not to reverse engineer their stuff and share it with the world (and their competitors) Jun 20 03:29:26 yeah, Purism has been hit by that before. Intel got them to take down a whole article about reverse engineering something. (luckily it was already on archive.org) Jun 20 03:29:44 What were they reverse engineering? Jun 20 03:30:17 ok, yeah now I remember, BIOS stuff Jun 20 03:33:09 yeah, ME or something Jun 20 03:39:02 I doubt we will see full core-boot 100% free of blobs support on any desktop-grade Intel chip made in the last 10 years any time soon. Not just because of how complex it is but because Intel will use their army of lawyers to stop it. Jun 20 03:39:50 AMD is probably just about as bad on this. **** ENDING LOGGING AT Thu Jun 21 00:49:10 2018 **** BEGIN LOGGING AT Thu Jun 21 00:49:15 2018 **** ENDING LOGGING AT Thu Jun 21 00:49:15 2018 **** BEGIN LOGGING AT Thu Jun 21 00:58:15 2018 **** ENDING LOGGING AT Thu Jun 21 01:11:42 2018 **** BEGIN LOGGING AT Thu Jun 21 02:42:16 2018 **** ENDING LOGGING AT Thu Jun 21 03:00:01 2018