I have a custom AT91RM9200 board running Xserver-Kdrive 1.3 from org.openembedded.dev branch. This interfaces to the linux framebuffer.
When I use a mouse, or animate images on the screen, I can see artifacts laid behind. In debugging it, I can see that if I put in a solid color where the 16 bits are "00 1F 00 1F" and run the mouse pointer over that area, I see "1F 1F 1F 1F 00 1F 00 1F" as though it either wrote back the incorrect location, or was using an incorrect endianness, or something else. This problem does NOT show up using tiny-x from a buildroot toolchain. I want to be able to use OE and need to use OE for my development, but can not locate what could be the configuration issue here. I have checked in kdrive-common and haven't seen anything and have searched around the web for someone with a similar issue and haven't come up with anything. Can anyone give some guidance of things to look at or check into? Any info from Xdpyinfo that could be useful? It all *looks* right, but it doesn't act right. Christopher _______________________________________________ Openembedded-users mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
