Wayland's Weston Gets Output Configuration File
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...
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?
Originally Posted by FunkyM
WTF Wayland/Weston devs.
Why the fuck do we need this when we have KMS?
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!
Because KMS don't remember a custom resolution after a restart.
Originally Posted by asdx
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.
Last edited by Jonno; 07-31-2012 at 01:49 PM.
Originally Posted by asdx
What we did in X.Org was make the configuration file optional. The problem with xorg.conf wasn't that it existed, but instead that you could not start up a server without it. We spent a lot of time making the server do the right thing by default and making sure that most people would never have to touch it. But we retained the option for people who had different needs from the default heuristics.
You should also probably look into therapy if something as basic as a new entry in weston.ini makes you this angry.
Originally Posted by daniels
I apologize for expressing myself that way, but I have this huge PTSD that comes from a few years ago (before we had KMS) when X would require a xorg.conf to even start (if you were lucky), and I would have to help people over SSH with their xorg.conf. It was terrible. This probably was before (or after) the XFree86/Xorg fork.
I simply don't want that to happen to Wayland/Weston and I'm worried about similar experiences happening again.
Why can't we have things just work?
You are probably right about therapy, I need it *sigh*.
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?