On Fri, 2016-11-18 at 12:56 -0600, Rob Herring wrote: > On Fri, Nov 18, 2016 at 8:15 AM, One Thousand Gnomes > <gnomes@xxxxxxxxxxxxxxxxxxx> wrote: > > > > > > > > AIUI, we're not taking new FB drivers. This should be a DRM > > > driver > > > instead. > > Yes - clone one of the dumb DRM drivers, or if you've got any > > little bits > > of acceleration (even rolling the display) then it's possibly worth > > accelerating for text mode. > > > > > > > > > > > > > +- max-width: The width of the framebuffer in pixels. > > > > +- max-height: The height of the framebuffer in pixels. > > > > +- bits-per-color: only "8" is currently supported > > > These are not h/w properties. > > How are the max ones not hardware properties ? > Because the way they are used is setting the mode, not some check of > the max when the mode is set. If this is synthesized for only one > size, then that would be different, but we have bindings for modes. > > Rob Currently the idea is to just synthesize the display to just 1920 x 1080. Therefore we came to a conclusion that it should be part of the HW properties. HeanLoong -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html