Hi all, 1. I am using meego 1.1 official image along with meego-handset-ia32-mtf-1.1-boot.bin <http://repo.meego.com/MeeGo/releases/1.1/handset/images/meego-handset-ia32-mtf/meego-handset-ia32-mtf-1.1-boot.bin.bz2> bootloader on moorestown based device, I have noticed that the touch does not work until i restart the Xorg process. But the same works fine with Kboot. So has anyone faced problems related to touch while using meego-handset-ia32-mtf-1.1-boot.bin ???<http://repo.meego.com/MeeGo/releases/1.1/handset/images/meego-handset-ia32-mtf/meego-handset-ia32-mtf-1.1-boot.bin.bz2>
2. This issue also persist on the meego1.1.80 image( meego-handset-ia32-mtf-1.1.80.6.20101116.1-sda.bin.bz2<http://repo.meego.com/MeeGo/builds/1.1.80/1.1.80.6.20101116.1/handset/images/meego-handset-ia32-mtf/meego-handset-ia32-mtf-1.1.80.6.20101116.1-sda.bin.bz2>) while using meego provided bootloader( meego-handset-ia32-mtf-1.1.80.6.20101116.1-boot.bin<http://repo.meego.com/MeeGo/builds/1.1.80/1.1.80.6.20101116.1/handset/images/meego-handset-ia32-mtf/meego-handset-ia32-mtf-1.1.80.6.20101116.1-boot.bin.bz2> ). Workaround to the problem is again by killing and restarting Xorg. so do i need to take care of any configuration changes to be done at meego Filesystem or kernel level that has to be done while migrating from kboot to meego-boot.bin ??? Cheers, John.
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
