Intel Winning Over NVIDIA For Linux Enthusiasts

[deanjo]

Hmmm, there might be a good reason for this. Constructing a GUI should be trivial.

1: get-function Enumerate devices, device properties, current settings. ( equiv of xrandr --properties --verbose )
2: Define GUI elements and positioning
3: Categorize properties into GUI element types (sliders, buttons, box)
4: set function (equiv of xrandr set)

I'll see what my calendar looks like, but I'm willing to bet I could implement something usable faster than I could construct a beer can pyramid. I could also simply take the current GUI and add additional properties (gamma, brightness, etc) without getting into anything difficult (addmode/newmode).

What properties were you gents looking for?

F

Well what old Sax2 would do is query the various driver specific xorg options and give you the option of setting the various boolean / flags and then add that to the xorg.conf. Take it one step farther and upon relaunch of X to either accept the new settings or after a time out revert back to the previous configuration.

[entropy]

Constructing a guy should be trivial.

Go ahead, Dr. Frankenstein!
*SCNR*

1: get-function Enumerate devices, device properties, current settings. ( equiv of xrandr --properties --verbose )
2: Define GUI elements and positioning
3: Categorize properties into GUI element types (sliders, buttons, box)
4: set function (equiv of xrandr set)

I'll see what my calendar looks like, but I'm willing to bet I could implement something usable faster than I could construct a beer can pyramid. I could also simply take the current GUI and add additional properties (gamma, brightness, etc) without getting into anything difficult (addmode/newmode).
F

Sounds promising!

[russofris]

That is a GUI to XRandR. I said "other then basic XRandR settings?"

That being said there is Sax3, but it is still fairly limited so far as well. Old Sax2 you could set any setting under the sun.

Hmmm, there might be a good reason for this. Constructing a GUI should be trivial.

1: get-function Enumerate devices, device properties, current settings. ( equiv of xrandr --properties --verbose )
2: Define GUI elements and positioning
3: Categorize properties into GUI element types (sliders, buttons, box)
4: set function (equiv of xrandr set)

I'll see what my calendar looks like, but I'm willing to bet I could implement something usable faster than I could construct a beer can pyramid. I could also simply take the current GUI and add additional properties (gamma, brightness, etc) without getting into anything difficult (addmode/newmode).

What properties were you gents looking for?

F

[bridgman]

These arent' intel parts, they're imageon, very similar to the powervr gpus found in many ARM socs. Avoid all of those like the plague.

Believe you mean "Imagination Technologies" (makers of PowerVR). The Imageon GPUs were originally developed by ATI.

[deanjo]

Wait... So when I go to Gnome settings --> screen settings.... That's not a GUI to XRandR?

I'm now thoroughly confused.

F

That is a GUI to XRandR. I said "other then basic XRandR settings?"

That being said there is Sax3, but it is still fairly limited so far as well. Old Sax2 you could set any setting under the sun.

[curaga]

He means the Xorg options, and said that a GUI is only available for basic xrandr.

[russofris]

Which brings me to another huge gripe with opendrivers, why the heck is there not a gui that lets you to change these options without having to revert to editing config files other then basic XRandR settings? It's papercuts like this that hold linux back and feed the trolls with ammo to dig at linux.

Wait... So when I go to Gnome settings --> screen settings.... That's not a GUI to XRandR?

I'm now thoroughly confused.

F

[Aleve Sicofante]

I did. Went on DuckDuckGo as well. Couldn't find anything pointing towards what you're saying, unfortunately.

Because it's plain idiotic and he can't back it up by a single source.

[deanjo]

Same experience on Ironlake here (also: freezes with UXA acceleration (bugreport filled) and tearing with SNA). May anyone who recommend Intel hardware to people, tell me: driver for Ironlake GPU was always so bad, or this is result of regressions?

btw, h264 hardware decoding on Ironlake is slower then software.

Which brings me to another huge gripe with opendrivers, why the heck is there not a gui that lets you to change these options without having to revert to editing config files other then basic XRandR settings? It's papercuts like this that hold linux back and feed the trolls with ammo to dig at linux.

[FutureSuture]

Citation: google it.

I did. Went on DuckDuckGo as well. Couldn't find anything pointing towards what you're saying, unfortunately.