Comment 16 for bug 41355

Any work on this would be welcome. I would not mind adding the s3switch utility to the savage upstream code as long as there is no license issues. It is basically one file to make one binary. Now looking at the file, almost every part of it is already in the savage code. Which leads me to think it should be relatively easy to bake it into the savage driver. In order to control the outputs, the xrandr interface would have to be used. I don't know how much work it would be to add xrandr output control to the savage driver, but it seems like the best solution technically and in terms of future support. Would you be willing to look into this? I have not much time for this, and not much xrandr insight, but I will assist in testing (on my Twister card) and code review and make sure it gets upstream.