Wayland's Weston Gets Output Configuration File

[phoronix]

Phoronix: Wayland's Weston Gets Output Configuration File

Weston, the reference compositor to Wayland, now has support for output configuration from the Weston config file, i.e. the equivalent of configuring your output options with an X.Org Server from the xorg.conf...

http://www.phoronix.com/vr.php?view=MTE1MDg

[FunkyM]

Wasn't it actually a good thing to have a dynamic setup of output devices?
I can remember that there was quite some work done to allow Xorg to run without a xorg.conf file once, right?

[asdx]

Nice to see progress in Wayland/Weston.

But what's the point of this feature? Doesn't KMS already does the job of setting the modes automatically?

[asdx]

Wasn't it actually a good thing to have a dynamic setup of output devices?
I can remember that there was quite some work done to allow Xorg to run without a xorg.conf file once, right?

That's my question, why are Wayland developers reintroducing a feature (configuration file) when Xorg devs tried to get rid of it?

[disi]

That's my question, why are Wayland developers reintroducing a feature (configuration file) when Xorg devs tried to get rid of it?

It is really so 90's
This is one reason why I wouldn't use a binary driver with Xorg...

p.s. I know nVidia-Fans, they provide xrandr support for a month now (after ~15 years or so)

[asdx]

WTF Wayland/Weston devs.

Why the fuck do we need this when we have KMS?

[uid313]

That is retarded.

In a INI file, the [output] is considered a header/category/topic and everything under is key and value.
You cant have a header with same name, that is not valid INI file!

[roland]

We want a config file because we can't assume that the correct configuration will always be selected. I have two laptops with external monitors, on one I want the laptop monitor off and the external at its native resolution. On the other I want both lvds and hdmi to be at the greatest common resolution. How is KMS going to do this correctly? This config file seems perfectly flexible, I don't understand the complaints.

[Jonno]

Why the fuck do we need this when we have KMS?

Because KMS don't remember a custom resolution after a restart.

All Wayland does with this information is tell KMS to turn on/off the specified output and change its resolution to the one specified, the default (eg without a config file) will be to keep each display as is (usually at the native resolution which the kernel autodetected at startup), just like it does today.

E.g. KMS knows how to change resolution, but needs to be told what resolution the user wants to use. This is just one way of telling it, one that persists over a reboot. Dynamic (xrandr-style) resolution changes will of course also be supported.

[asdx]

Because KMS don't remember a custom resolution after restart.

All Wayland does with this information is tell KMS to turn on/off the specified output and change its resolution to the one specified, the default (eg without a config file) will be to keep each displays settings as is (usually the native resolution which the kernel autodetected at startup), just like it does today.

I don't fucking care if KMS remembers the resolution or not after restart, I don't want to be editing a config file like a fucking idiot for setting something basic as my screen resolution.

We're not in 1970 anymore.

The resolution is the job for KMS to handle, not the user. Period.

What the fuck is this.