Type: Posts; User: Nille; Keyword(s):
Whats not working? Special Standby is interesting.
The NTFS Bench with a Userspace Driver is worthless ... Why do you don't make a test with the Kernel Driver from tuxera or the kernel Driver from Samsung for exFat? The last one is interesting...
You can't mean the glibc ... like there abi break in 2.19
@SystemCrasher sounds like a bunch of bullshit.
Its more: Because there is no other 3D API ...
Why do you not use the remote PowerShell?
But the problem with big kernels are still there ;)
Not till Microsoft Support and make it a valid option for the windows compatibility logo
Why from china? we talk only about chips. Its not to hard to ban affected chips from from the import. If they cant sell the chips in the EU or US, i bet they change there minds.
And what is the opinion from ffmpeg?
ha ha, no its not. Try and use the driver some time or read the tests from phoronix.
Mesa and OpenGL is not the only part of a driver. There are some other places there some love is needed. e.g. complete VA-API, crossfire, deinterlacing or in the future vulkan support.
There is the first troll/fanatic ...
Like the problems one the last 5-6 Patchdays? Or the disbanded security team? Dont get the wrong impression. Some decisions are great but some others are horrible.
Microsoft has also releases the driver framework for the kernel and userspace under the MIT License and Sample code (Unknown License)
Windows driver frameworks source on GitHub
The 10.04 Desktop is still EOL since 2 Years.
CPU Dispatcher ....
ffmpeg, x264 etc use own functions that can utilize the instructions if they available.
The Mailinglist link point back to the same blog post.