Yes, we're talking about the same thing.

I'm aware of the company that found the actual problem - I specifically stated that I read the linked articles, and that link you provided is one of the ones already linked. Obviously the kernel devs erred when they automatically assumed there wasn't a kernel bug.

That said, Linus never apologises for his own out-rightly abusive comments and actions. There's no way he's going to apologise on behalf of someone else, especially when there's some truth to the kernel developers comments - there are known bugs in the Samsung firmware. They just made the mistake of assuming that this particular one was one of those instead of one of their own. The best we can hope for is those responsible developers apologising on their own behalf.

840 (non EVO) and 840 EVO. As far as I'm aware it doesn't affect the 850 EVO. They didn't even bother addressing the 840 non EVO model with their firmware updates.

It's actually much simpler than that. Windows doesn't yet support queued TRIM, it still uses the legacy serial TRIM. The Samsung firmware bug is in the queued TRIM implementation, which is a different issue to the Linux kernel TRIM bug that Samsung found.

No, it's a case of everyone jumping to conclusions.

No, they went on the queued TRIM blacklist due to a different bug. This bug was an unrelated serial TRIM bug when used in conjunction with RAID.

That really depends on whether OS X uses serial or queued TRIM. The Samsung drives work fine with serial TRIM, but are still broken with queued TRIM. The bug that Algolia reported and Samsung fixed in the kernel was a serial TRIM issue in the Linux kernel with RAID, which is unrelated to the queued TRIM firmware issues.

Because there are two separate bugs.

The queued TRIM blacklist on Samsung drives doesn't affect Windows because Windows doesn't support queued TRIM yet. This Linux kernel bug is a different issue, but many assumed it was the same, even though Algolia clearly stated in their blog post that they weren't using queued TRIM.

I've read the articles. There are two separate bugs here. One, Samsung drives advertise support for queued TRIM even though it's not properly supported, causing corruption. Two, the kernel had a TRIM bug that affected serial TRIM with mdadm RAID, which is the kernel bug Samsung found and fixed. The queued TRIM bug still exists in the Samsung firmware.

No, it's official. Microsoft no longer requires that Secure Boot must be able to be disabled on x86 machines to get Windows certification.

Key emphasis on "should". I wouldn't put it past them to do sequential loading in Javascript.

I think that's 100ms per ad. With lots of ads, you'll easily get into the multi second range.

The $105 million fine is not for the 1.4 million vehicles recalled due to the remote hack. The fine is for a separate set of issues on which recalls weren't properly done. The $105 million fine also isn't the end of the punishment, they have to also purchase back affected vehicles from consenting owners.

How certain are you that there will be no eDRAM versions of socketed Skylake?

You're probably thinking of NVIDIAs Optimus technology in portable devices. In which case, no, the Intel graphics aren't enhancing anything. The output from the NVIDIA chip gets piped through the Intel chip, as the Intel chip is the only one attached to the display. It's a solution to requiring a reboot with muxed GPU switching solutions. There's also a mild performance reduction with the Optimus solution.