Originally posted by LinuxID10T
View Post
Announcement
Collapse
No announcement yet.
"We have no plans to support Wayland."
Collapse
X
-
-
I think everyone should keep in mind why Nvidia did their Linux driver in the first place... usage in the commercial 3D rendering sector and big players like Disney using Linux in their production pipeline.
There is basically no interest regarding the support of home-users, and having stable "gaming" drivers for Linux was just a side effect, so to say.
That is why Nvidia will not support Optimus on Linux (only used in Laptop), and why Wayland support is unlikely (since it is a geared toward consumers... e.g. desktop Linux use).
Leave a comment:
-
Originally posted by Kano View PostIt definitely works with with older driver to decode full hd content using mplayer and xbmc with the auto settings in bios and 1 gb ram. Just vlc is a no go - too slow.
Leave a comment:
-
It definitely works with with older driver to decode full hd content using mplayer and xbmc with the auto settings in bios and 1 gb ram. Just vlc is a no go - too slow.
Leave a comment:
-
Stephan Warren seems to say the same thing as well,
It's probably simplest to get a 512MB system. Various users with 256MB have reported success, but it depends a lot on what else is running on your system
Leave a comment:
-
Mythtv seems to agree with me on the video memory allocation.
Many playback issues can be resolved by making sure enough memory has been allocated to the video card, 256MB is a bare minimum requirement and 512MB is strongly recommended. For on-board video this is usually configured via the "GPU Window" BIOS option.
Leave a comment:
-
Originally posted by Kano View PostI don't know if you need to call it mem leak, but with 256.xx driver i can use a 1 gb atom system with 128 mb for vga without swap and with 260.xx driver this is completely impossible. With 2 gb ram the thing would look different as you definitely must have more than 1 gb ram...
Leave a comment:
-
Originally posted by borsook View PostIs there any reason in the architecture preventing Wayland from having network transparency in the future? I honestly don't know, I never needed network transparency and never will. Wayland is not feature complete as of now, so maybe? Fragmentation can be bad (look at what happened to Compiz some time ago) but choice can be great and Wayland may really push forward development of drivers in so far a bit overlooked areas.
Fragmentation is not necessarily an issue here because X11 and Wayland are different projects trying to achieve different, if overlapping, goals. X.org and Wayland are both free software, and there is much capacity to improve one based on improvements in the other. Especially where it is in relation to the graphics drivers. This would be more like KDE vs. Gnome ? they both run on X, but they never started as the same project; As such, the only issues that can be are the ones that fools make. And look how well those two projects are getting along, now.
As for nVidia supporting KMS, well if they do that would be great, and they wouldn't even need to write a framebuffer console ? one of the things about KMS is that the fbcon module is not hardware specific ? if anything understood the kernel driver other than their own proprietary OpenGL stack in X11.
Leave a comment:
-
I don't know if you need to call it mem leak, but with 256.xx driver i can use a 1 gb atom system with 128 mb for vga without swap and with 260.xx driver this is completely impossible. With 2 gb ram the thing would look different as you definitely must have more than 1 gb ram...
Leave a comment:
-
Originally posted by Kano View PostThere are much bigger ram consumers, like the nvidia 260 series driver - when you want to use vdpau on systems with low memory you need very much swap space currently, you could not gain that amount while just using wayland. nvidia should better optimize the new driver for ram usage, would be better for all...
I know there was a vdpau mem leak in the earlier 260 series but that has since been resolved.
Leave a comment:
Leave a comment: