On Mon, 2011-04-11 at 12:08 +0200, Tomasz MÅoduchowski wrote: > >> Is there a way to diagnose why the omapdss fails to scale ovl 0? > > No need to diagnose, graphics overlay (overlay 0) cannot be scaled =). > Thanks so much! > > Now that you pointed me in the right direction - the only place this > limitation is actually mentioned is the TRM document (and the driver > seems quite content to export unsupported functionality to the sysfs) True. I've long had plan to add the sysfs files only if the feature is actually supported. > Perhaps next time someone stumbles over my naive question and finds > this thread. If I find the time this week, I'll try adding something > to the documentation. I've mostly tried to keep the documentation only discuss about the software side. The TRM is public and should be used to understand the hardware. 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. Tomi -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
