Re:After protest, Lenovo adds Linux compatibility to Yoga 90...
by sengork on Wednesday November 09, 2016 @06:22PM
(#12915893)
I find the recruitment information page on that domain rather amusing: http://www.infradead.org/recruitment.html
Re:After protest, Lenovo adds Linux compatibility to Yoga 90...
by saganus on Wednesday November 09, 2016 @06:56PM
(#12916200)
I read it and even tried to search for his name because apparently he has made important contributions to Linux (he links /usr/src/linux/CREDITS as his CV so...), but couldn't find anything specifically about his work.
Do you happen to know what does he work/has worked on regarding Linux?
Re:After protest, Lenovo adds Linux compatibility to Yoga 90...
by thewisenerd on Thursday November 10, 2016 @06:09AM
(#12919417)
He's the lead developer at LinuxMTD (http://www.linux-mtd.infradead.org/); (no wonder I seem to remember the "infradead" name from somewhere).
More about him, here: http://www.advogato.org/person/dwmw2/
Re:After protest, Lenovo adds Linux compatibility to Yoga 90...
by revelation on Wednesday November 09, 2016 @06:19PM
(#12915868)
Can someone explain in greater detail what exactly Intel is trying to do here?
It sounds like trying to tunnel NVMe through something that is only connected over an AHCI interface.
Re:After protest, Lenovo adds Linux compatibility to Yoga 90...
by userbinator on Friday November 11, 2016 @06:47AM
(#12929797)
I'm not too familiar with this area of PC hardware, but it does seem like their AHCI controller can be configured to act like a PCI bridge with an NVMe device on the other side of it.
Re:After protest, Lenovo adds Linux compatibility to Yoga 90...
by incompatible on Wednesday November 09, 2016 @05:05PM
(#12915168)
Is the unreliable hardware causing problems for Windows users?
Re:After protest, Lenovo adds Linux compatibility to Yoga 90...
by digi_owl on Wednesday November 09, 2016 @11:15PM
(#12917672)
Nope, because Intel can just push some binary drivers out and everyone will down it with a gargle.
The kernel patches are refused because the kernel devs expect to maintain the code for as long as there are devices in active use that need it once allowed in.
Thus they demand a proper spec for the device behavior so they can test for breakages down the line. And apparently the patches are already violating AHCI behavior expected by the kernel.
Or at least that is what i got out of reading the short ML thread.
However, the kernel maintainers turned down the patch because the hardware itself was bizarre, underspecified, and unreliable in common cases.
This is an ongoing story and i expect there'll be a resolution in a few months.
ML discussion thread is here: http://lists.infradead.org/pipermail/linux-nvme/2016-October...