https://bugs.kde.org/show_bug.cgi?id=504611
--- Comment #15 from Zamundaaa <xaver.h...@kde.org> --- (In reply to Sergio from comment #12) > I have had some interaction with the iio-proxy-developers. > > Their point is that the sensor data is correct. It should be the user of the > data that practices the display orientation to use that data correctly > taking into account that there is already a display rotation practiced at > the DRM level. Their take is that it is the wayland compositor that already > talks to the DRM interfaces, so it has all the means to know. There is no display rotation practiced at the DRM level. panel_orientation is purely information for the compositor to apply, not something the driver does under the hood. > Maybe they are right. In the end the display might not (e.g. in the future) > be the single user of the orientation data. There might be a day when in > tablets speakers arrays become the norm. In this scenario, the signal > processing chain might need to know the orientation to produce correct > stereo. And it would need the "real" orientation. It is only the display > that needs to know of any rotation introduced at the display connector level. The issue here is *not* that the sensor orientation needs to be adjusted to match the display, exactly the opposite. Your sensor is oriented so that it matches the display, instead of the device. (In reply to Sergio from comment #14) > Would then an easy solution be to have a "tickbox" in the display > configuration dialog saying "ignore panel_orientation overrides"? Wouldn't > that fix everything? No, KWin is not the correct place to work around the orientation sensor being wrong. -- You are receiving this mail because: You are watching all bug changes.
