From: shc_work@mail.ru (=?UTF-8?B?QWxleGFuZGVyIFNoaXlhbg==?=) Date: Tue, 30 Apr 2013 18:38:05 +0400 Subject: =?UTF-8?B?UmVbMl06IFtQQVRDSCBWMl0gdmlkZW86IGltcGxlbWVudCBhIHNpbXBsZSBm?= =?UTF-8?B?cmFtZWJ1ZmZlciBkcml2ZXI=?= In-Reply-To: <517F753F.5090909@ti.com> References: <1365043183-28905-1-git-send-email-swarren@wwwdotorg.org> <517F753F.5090909@ti.com> Message-ID: <1367332685.945287573@f287.mail.ru> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org > 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 ... > > + 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? ---