Hi Zoran,
please stop sending HTML emails. Your mails are often very hard to view. Especially the quotations are completely messed up by your MUA when you play with the font settings.
On 22.12.2017 10:38, Zoran Stojsavljevic wrote:
Nice. So now we have Ubuntu INTEL SPI device driver messing up with PCH registry. Setting some of them to make BIOS NVRAM RO.
No, it's about the flash chip's own registers not the PCH.
Another workaround will be to add in /etc/rc.d/rc6.d some K process which will fix this problem by clearing offending bit in SR2.
You can't work around a broken driver without a working driver. But if they at least didn't compile the driver into the kernel but a module, you can blacklist that module and everything should be fine.
Nico
Am Freitag, den 22.12.2017, 15:31 +0100 schrieb Nico Huber:
Hi Zoran,
please stop sending HTML emails. Your mails are often very hard to view. Especially the quotations are completely messed up by your MUA when you play with the font settings.
Afaik it's possible to configure mail-servers so they automatically reject HTML-Mails or transcode them to txt. Beside that you often can configure it so it doesn't send E-Mails to people who're subscribed to the list, if they're also in CC.
Maybe reconfiguring coreboot's mailserver would be a good idea :) My 2 ct.
Philipp
Off @topic:
please stop sending HTML emails. Your mails are often very hard to view. Especially the quotations are completely messed up by your MUA when you play with the font settings.
Better?
Zoran
On Fri, Dec 22, 2017 at 3:31 PM, Nico Huber nico.h@gmx.de wrote:
Hi Zoran,
please stop sending HTML emails. Your mails are often very hard to view. Especially the quotations are completely messed up by your MUA when you play with the font settings.
On 22.12.2017 10:38, Zoran Stojsavljevic wrote:
Nice. So now we have Ubuntu INTEL SPI device driver messing up with PCH registry. Setting some of them to make BIOS NVRAM RO.
No, it's about the flash chip's own registers not the PCH.
Another workaround will be to add in /etc/rc.d/rc6.d some K process which will fix this problem by clearing offending bit in SR2.
You can't work around a broken driver without a working driver. But if they at least didn't compile the driver into the kernel but a module, you can blacklist that module and everything should be fine.
Nico