Yes, this is definitely a "WTF?" moment in the history of Slashdot. I suggest that you all just move on to the next story and refuse to feed the troll by asking him questions.

Slashdot, obviously, has to innovate in order to stay current. Thus, they are now taking the next step after "Anonymous Cowards". The new "Identified Troll" feature will include interviews of people who have prostituted their personal credibility to some company's calculated disinformation campaign.

There's nothing I find particularly alarming here and the behaviour is in fact pretty much what I would expect for computing sin(x). Sure, maybe the doc needs updating, but nobody would really expect fsin to do much better than what it does. And in fact, if you wanted to maintain good accuracy even for large values (up to the double-precision range), then you would need a 2048-bit subtraction just for the range reduction! As far as I can tell, the accuracy up to pi/2 is pretty good. If you want good accuracy beyond that, you better do the range reduction yourself. In general, I would also argue that if you have accuracy issues with fsin, then your code is probably broken to begin with.

There's a difference between attacking a piece of software and attacking the author. I personally have no opinion on systemd (hell, I don't even know what init system I'm running atm), but I feel like any complaint people have should be directed at whoever *chose* systemd, rather than who wrote it. You can't blame someone for writing software. If you don't like it, don't use it and/or tell distros not to use it.

And since this is a camera passthrough, not an optical overlay, that's a glaring implementation flaw. Properly aligning the head tracking framerate, camera framerate, and rendering would let them render the virtual objects in lockstep with the physical ones (at least at speeds where motion blur isn't a significant issue; you can fake that by minimizing motion blur in the real image by using a short shutter time on the cameras).

So, they're locking out things that can brick the card (flash ROM/fuses, screw up thermal sensors) and apparently a hint of OS security (the Falcons that respond to userspace commands can no longer access physical memory, only virtual memory). The latter sounds somewhat bizarre, considering the firmware should be fully under the control of the driver, not userspace (I guess/hope?), but not unreasonable. Maybe there are software security reasons for this.

Nouveau is free to continue using its own free blobs or to switch to nvidia's. If they start adding restrictions that actively cripple useful features or are DRM nonsense, then I would start complaining, but so far it sounds like an attempt at protecting the hardware while maintaining manufacturing flexibility for nvidia. This isn't much different from devices which are fused at the factory with thermal parameters and with some units disabled; the only difference is that here firmware is involved.

NV seem to be turning friendlier towards nouveau, so I'd give them the benefit of the doubt. If they wanted to be evil, they would've just required signed firmware for the card to function at all. The fact that they're bothering to have non-secure modes and are only locking out very specific features suggests they're actively trying to play nicely with open source software.

I last tried a Debian install around the time of Dayton Hamvention, so a few months ago. I don't have a bug #, I tried to debug GDM for a while but didn't have enough time. I can try another install sometime soon.

Well, a Core i5 tablet with two parallel screen digitizers is an odd enough bird that you can't expect it to run on the somewhat aged Debian stable. And indeed the older GNOME there handles the touchscreen incorrectly.

Because it has a touchscreen and a separate pen digitizer on the same screen. And now with the keyboard, it also has a Cirque touchpad, for a total of three digitizers.

The Toughpad has a touchscreen and a pen (with a separate digitizer!) and the touchscreen doesn't work properly in the older GNOME in stable.

There is a video of someone throwing around my model, without the keyboard, here.

After something like 20 years I finally found a system that won't run Debian unstable right now. My Panasonic Toughpad FZ-G1 magnesium tablet + iKey Jumpseat magnesium keyboard. Systemd and GDM break. Bought (for less than full price) because I am a frequent traveler and speaker and really do need something you can drop from 6 feet and pour coffee over have it keep working.

But because of this bug I have ubuntu at the moment, and am not having fun and am eager to return to Debian.

We are in a War on Faith, because Faith justifies anything and ISIS takes it to extremes. But in the end they are just a bigger version of Christian-dominated school boards that mess with the teaching of Evolution, or Mormon sponsors of anti-gay-marriage measures, or my Hebrew school teacher, an adult who slapped me as a 12-year-old for some unremembered offense against his faith.