I have added "mem=80M" to the kernel command line and created a directfbrc with the following:
system = devmem # select 'devmem' system module video-phys = 85000000 # 0x80000000 + 80MB offset video-length = 16777216 # 16MB for acceleration and ARGB OSD dithering accelerator = 6400 # disable probing in davinci driver When I start up a simple directfb applicaton I get the following messages: (*) Davinci/Driver: Mapped fb0 with length 1658880 at 0x84e00000 to 0x414f4000 (*) Davinci/Driver: Mapped fb1 with length 3760128 at 0x84800000 to 0x41689000 (*) Davinci/Driver: Mapped fb2 with length 1658880 at 0x84400000 to 0x41a1f000 (*) Davinci/Driver: Mapped fb3 with length 3760128 at 0x84000000 to 0x41bb4000 My question is that the fb0 starting address is 0x84e00000 which is below the video-phys = 85000000 address specified in directfbrc. All fb0 to fb3 are mapped at addresses below video-phys = 85000000. I would expect fb0 to be mapped from e.g. 85000000 and fb1 mapped to an address higher than this etc. My image is distorted and I am thinking this is why. Please could someone explain this to me. Thanks Ryan American Dynamics -- View this message in context: http://www.nabble.com/Explanation-of-framebuffer-address-mappings-tp19414350p19414350.html Sent from the DirectFB Dev mailing list archive at Nabble.com. _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
