On Mon, Mar 02, 2015 at 04:08:29PM +0000, Pawel Moll wrote: > I'm not sure about this... The word "virtual" never works well with > device tree nodes defined as "hardware description". > > I understand what you're doing, but adding this property to the display > controller's node doesn't sound right. How does this describe hardware? > If anywhere, it's more like a job for the panel node? A better description (and implementation) would be to describe the size of the RAM available for video purposes. The driver can then use the requested virtual X resolution to limit (and/or compute) the virtual Y resolution to allow Y panning/wrapping of the display. This would match some hardware where the video RAM is indeed a separate physical set of RAM (such as the IM-PD/1). -- FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
