> From: "Kalle Vahlman" <[email protected]> > 2011/4/11 Tomi Valkeinen <[email protected]> > > But you are right that normal user shouldn't need to read the TRM > > if he > > just wants to use scaling =). So either the sysfs/ioctl interfaces > > should force the user to use things correctly, or he should get > > clear > > warnings/errors when he uses things incorrectly, or the > > documentation > > should say these things. > > If the sysfs interface is not there, the questions will just turn > from > "why does it not work" to "why is there no sysfs entry"...
I believe there is a significant difference between 'why does it not work' and 'why is there no sysfs entry'. The former (especially together with a non-descriptive debug message under omapdss.debug), indicates that it should work (interface present) but fails to do (for some reason - things like resolutions divisible by 16, integer scaling coefficients, etc were running through my head from past experience with scaler hardware). The latter indicates that it shouldn't work (as intended by the developers - not present, not tested) - at least I'd be more likely to dig into TRM without assuming that it should be working (since someone put the interface to support it). Best Regards, Tomasz -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
