Denis Oliver Kropp wrote: > LearnerMan wrote: >> 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. > > No, it's correct. The kernel allocates fb0-fb3 for layers and DirectFB > additionally gets the 85000000 area for offscreen images etc. > >> My image is distorted and I am thinking this is why. > > Which resolution do you use? The kernel might not allocate enough memory. > > It's also important which device belongs to which layer... >
Really a pain... why not have a clean driver in user space only and forget about all those different fb driver versions with all their bugs and drawbacks... -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
