On Tuesday 30 April 2013, Alexander Shiyan wrote: > > On 04/04/2013 05:39 AM, Stephen Warren wrote: > > > A simple frame-buffer describes a raw memory region that may be rendered > > > to, with the assumption that the display hardware has already been set > > > up to scan out from that buffer. > > > > > > This is useful in cases where a bootloader exists and has set up the > > > display hardware, but a Linux driver doesn't yet exist for the display > > > hardware. > > > > > > Signed-off-by: Stephen Warren <swar...@wwwdotorg.org> > ... > > > + framebuffer { > > > + compatible = "simple-framebuffer"; > > > + reg = <0x1d385000 (1600 * 1200 * 2)>; > > > + width = <1600>; > > > + height = <1200>; > > > + stride = <(1600 * 2)>; > > > + format = "r5g6b5"; > > > + }; > > > > I'm not an expert on DT, but I think the point of DT is to describe the > > hardware. This doesn't describe the hardware at all. > > On my incompetent opinion, "bpp" parameter can replace size of > framebuffer and "stride". Is not it?
Not necessarily: you could have a stride that is larger than a line. Arnd _______________________________________________ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org https://lists.ozlabs.org/listinfo/devicetree-discuss