Conversation
Notices
-
@lxoliva What @jxself refers to is that Linux-libre deblobbing has now gone beyond removing firmware and into CPU microcode patches...
-
@leny2010 I noticed that Coreboot also contains such things. We really need someone to make a Coreboot-libre without them. cc: @lxolivia
-
@jxself @lxoliva I have no problem with removing firmware http://ur1.ca/9fnbh as per the guidelines. They don't say http://ur1.ca/9fnbx
-
@leny2010 Different terminology. That updates are released and can change CPU behavior makes it more like software than hardware I think.
-
@jxself No chip desinger would agree. Technically it is not software, therefore not firmware, which is all the guidelines cover.
-
@jxself You are implicitly trying to extend the software freedoms to another [related] field.
-
My opinion is that just as the software freedoms do not extend to artwork, they do not extend to microprograms.
-
@jxself In the sense that free microprograms are a separate issue that is not within l-libre's remit.
-
@leny2010 CPU microcode is code that programs hw to behave as an x86*; how's that difft from controlling disks, radios, etc?
-
@leny2010 I provided you with neither the defective CPU nor the non-Free patch for it; Linux-libre doesn't need fixing in this regard
-
@leny2010 as for patching CPU bugs, if your CPU worked before the microcode loader was even there, what are you complaining about?
-
@leny2010 GCC has a long history of accepting changes to compensate for bugs in various CPUs; there's nothing -libre-specific about it
-
@leny2010 cpu microcode is not in linux; intel microcode has shipped separately under nonfree licenses forever; same with amd now
-
@lxoliva That you are going beyond the remit of the Free Dist Guidelines, beyond software into what is hardware - microprograms
-
@leny2010 if the FSDG explicitly mentions nonfree microcode as acceptable, I'll change Linux-libre, so pls write to FSDG authors
-
@leny2010 now, I'm pretty sure you won't get such a change in, because I know where we draw the line, and that's what I implemented
-
@lxoliva OK. Thanks for your time.
-
-
@leny2010 :-) thanks :-)
All Identi.ca content and data are available under the