On 2016-Sep-25 11:22 , Segher Boessenkool wrote:
This isn't about device arguments. This is about using strings in properties to denote an array of integers; which is just a dumb thing to do.
My understanding was that this was to allow specifying a display resolution from the command line.
The sequence I'd expect from that would be that the command line would affect the "output-device" property/non-volatile variable, by adding a specific resolution as an argument to the display device. The display driver would get the resolution as a device-arg string, which it could either parse or do a straight comparison against a list of supported resolutions. That's the way it generally worked on systems at Sun (now Oracle).
Creating properties in /options seems like a long way around to get the information from the command line into the driver.