Same result with memset or cp : the screen stay white. I'll recheck my timings. Could it be related with the freeze of the splash utility? BTW, it seems that of_get_display_timings() can't manage ranges of datas as mentionned in the binding doc (display-timings.txt). Philippe LEDUC ledphilippe@xxxxxxxxx 2016-02-24 13:43 GMT+01:00 Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>: > On Wed, Feb 24, 2016 at 01:39:25PM +0100, Philippe Leduc wrote: >> > You could try setting it to >> V4L2_PIX_FMT_RGB24 manually in ipu_crtc_mode_set(). >> It is working with this trick and I do not get any error: >> >> Unfortunately, the display stay white... I tried to write it with "mw >> -d /dev/fb0 0xXXXXXXXX +0x40000" and splash freeze the board. > > Try 'cp /dev/ram0 /dev/fb0' or 'memset -d /dev/fb0 0x0 0x55 1M'. With > 'mw' you can only write single words which only gives you some dots in > one screen corner. > > Sascha > > -- > Pengutronix e.K. | | > Industrial Linux Solutions | http://www.pengutronix.de/ | > Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox