Maybe it’s time to talk about a new Linux Display Driver Model
yosoygames.com.ar
Maybe it’s time to talk about a new Linux Display Driver Model
1–10 of 69 posts
Re: Maybe it’s time to talk about a new Linux Display Driver Model
#2Re: Maybe it’s time to talk about a new Linux Display Driver Model
#3Re: Maybe it’s time to talk about a new Linux Display Driver Model
#4Re: Maybe it’s time to talk about a new Linux Display Driver Model
#5The thing about being able to read other process memory under Linux has always driven me nuts. Linux is fairly secure _except_ for this one giant gaping hole that nobody mentions.
Re: Maybe it’s time to talk about a new Linux Display Driver Model
#6The thing about being able to read other process memory under Linux has always driven me nuts. Linux is fairly secure _except_ for this one giant gaping hole that nobody mentions.
Re: Maybe it’s time to talk about a new Linux Display Driver Model
#7The thing about being able to read other process memory under Linux has always driven me nuts. Linux is fairly secure _except_ for this one giant gaping hole that nobody mentions.
This is extra fun considering WebGL.
Re: Maybe it’s time to talk about a new Linux Display Driver Model
#8I am currently using 2 displays connected to my graphics card and one connected to my igpu on my Linux desktop at home, and it's really not that hard to set up. Unfortunately the GPU does all the rendering and passes images to the iGPU, but I believe this is the case too with Windows. Also there are a few bugs when using this setup to do with monitor positioning.
Re: Maybe it’s time to talk about a new Linux Display Driver Model
#9The thing about being able to read other process memory under Linux has always driven me nuts. Linux is fairly secure _except_ for this one giant gaping hole that nobody mentions.
Should be pretty straightforward to fix. I wonder why it isn't. Is someone discussing the issue?
Re: Maybe it’s time to talk about a new Linux Display Driver Model
#10The thing about being able to read other process memory under Linux has always driven me nuts. Linux is fairly secure _except_ for this one giant gaping hole that nobody mentions.
Should be pretty straightforward to fix. I wonder why it isn't. Is someone discussing the issue?