On Mon, Oct 03, 2011 at 11:26:25PM +0200, Adam Lackorzynski wrote:
(...) Ok, but then it's good as it is displaying something. It's just the driver that needs to learn about that.
Adam
Hi Adam,
what steps are required to do that? Do I need to adjust the driver in lcd-omap3.c (l4/src/l4/pkg/drivers/lcd/src)? That file contains the following code:
335 static void configure_dss_beagleboard(l4_addr_t frame_buffer) 336 { 337 // for beagleboard just set the framebuffer address and let it run, 338 // everything else is already configured by U-Boot 339 write_dss_reg(Reg_dispc_gfx_ba0, frame_buffer); 340 write_dss_reg(Reg_dispc_gfx_ba1, frame_buffer); 341 }
So it should just work.
Maybe a newer version of U-Boot solves this?
Sorry for these newbish questions.
Thanks Giorgio
Hi,
On Tue Oct 04, 2011 at 14:16:10 +0200, Giorgio Wicklein wrote:
what steps are required to do that? Do I need to adjust the driver in lcd-omap3.c (l4/src/l4/pkg/drivers/lcd/src)? That file contains the following code:
335 static void configure_dss_beagleboard(l4_addr_t frame_buffer) 336 { 337 // for beagleboard just set the framebuffer address and let it run, 338 // everything else is already configured by U-Boot 339 write_dss_reg(Reg_dispc_gfx_ba0, frame_buffer); 340 write_dss_reg(Reg_dispc_gfx_ba1, frame_buffer); 341 }
So it should just work.
Hmm, should. I don't think that the registers have changed there.
Maybe a newer version of U-Boot solves this?
Hmm, if it's already doing some graphics, I do not see what a different u-boot would be doing different. But maybe it's worth a try.
Adam
On Tue, Oct 04, 2011 at 11:12:39PM +0200, Adam Lackorzynski wrote:
Hi,
On Tue Oct 04, 2011 at 14:16:10 +0200, Giorgio Wicklein wrote:
Maybe a newer version of U-Boot solves this?
Hmm, if it's already doing some graphics, I do not see what a different u-boot would be doing different. But maybe it's worth a try.
Adam
Hi,
now the framebuffer gets correctly configured and initialized by u-boot. The spectrum example and L4Android can use the fb. Seems good so far.
I wrote a small guide on what I did, in case someone encounter the same issue. (See attachment)
Hi,
my previous email [1] about the framebuffer issue on beagleboard is not really a fix, because the used U-Boot version, which did the nice dss initialisation, is affected by a bug that causes an ehci power down during boot and so a non working USB ehci port.
I found the beagle u-boot logo patch [2], which was used in the broken U-Boot version, and ported it to L4. So we have a working lcd display regardless of the U-Boot initialisation, since the newer versions don't do any dss initialisation [3].
Please feel free to use my patch [4], see attachment.
[1] http://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/005048.html [2] http://groups.google.com/group/beagleboard/browse_thread/thread/3ad9b803a341... [3] http://lists.denx.de/pipermail/u-boot/2011-October/104043.html [4] addressed to l4/pkg/drivers/lcd/src/lcd-omap3.c
l4-hackers@os.inf.tu-dresden.de