[Bug 511491] Re: X crash when using touch screen on Freescale MX51 in Karmic
This issue still exists in lucid. Jason has found one fix for it. Will attach soon. ** Changed in: xf86-input-evtouch (Ubuntu) Status: Expired = In Progress ** Changed in: xf86-input-evtouch (Ubuntu) Assignee: (unassigned) = Zhang Lily (r58066) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/511491 Title: X crash when using touch screen on Freescale MX51 in Karmic -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559065] Re: ifconfig eth0 down will cause system hang after fec.c driver update
Regarding phylib resume issue, see one fix under http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=541cd3ee00a4fe975b22fac6a3bc846bacef37f7 -- ifconfig eth0 down will cause system hang after fec.c driver update https://bugs.launchpad.net/bugs/559065 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 511491] [NEW] X crash when using touch screen on Freescale MX51 in Karmic
Public bug reported: HW configuration: MX51 EVK board SW configuration: 1. Install xserver-xorg-input-evtouch page (version: 0.8.8-0ubuntu6.1) 2. Add fdi file by vi /usr/share/hal/fdi/policy/20thirdparty/50-mxc-ts.fdi: ?xml version=1.0 encoding=ISO-8859-1? deviceinfo version=0.2 device match key=info.product contains=mxc_ts merge key=input.x11_driver type=stringevtouch/merge /match /device /deviceinfo 3. reboot the board, X crash. The backtrace is as follows: Program received signal SIGSEGV, Segmentation fault. 0x402edae4 in strlen () from /lib/libc.so.6 (gdb) backtrace #0 0x402edae4 in strlen () from /lib/libc.so.6 #1 0x00096a4c in xf86optionListCreate () #2 0x0008f8d8 in xf86CollectInputOptions () #3 0x42d46b0c in EVTouchPreInit (drv=value optimized out, dev=0x329b88, flags=value optimized out) at evtouch.c:1167 #4 0x000861c8 in ?? () #5 0x000861c8 in ?? () However if i down-grade xserver-xorg-input-evtouch to version 0.8.8-0ubuntu3, Touch screen works fine. So what's the possible difference cause this issue? ** Affects: xf86-input-evtouch (Ubuntu) Importance: Undecided Status: New -- X crash when using touch screen on Freescale MX51 in Karmic https://bugs.launchpad.net/bugs/511491 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 507416] Re: CONFIG_NEON=y causes platform lockups with certain application/platform combinations
Regarding wrong board version for EVK3.0, it was fixed before. The attachment is the patch. ** Attachment added: 0069-ENGR00118739-Correct-the-board-version-of-MX51-EVK.patch http://launchpadlibrarian.net/38213403/0069-ENGR00118739-Correct-the-board-version-of-MX51-EVK.patch -- CONFIG_NEON=y causes platform lockups with certain application/platform combinations https://bugs.launchpad.net/bugs/507416 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 507416] Re: CONFIG_NEON=y causes platform lockups with certain application/platform combinations
Regarding wrong board version for EVK3.0, it was fixed before. The attachment is the patch. ** Attachment added: 0069-ENGR00118739-Correct-the-board-version-of-MX51-EVK.patch http://launchpadlibrarian.net/38213404/0069-ENGR00118739-Correct-the-board-version-of-MX51-EVK.patch -- CONFIG_NEON=y causes platform lockups with certain application/platform combinations https://bugs.launchpad.net/bugs/507416 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 506761] Re: lucid uboot hangs on fatload uImage on fsl TO2 TO2.5 and TO3
Since we use LTIB for building (do mkimage operation), all documents you got did not mention it. Sorry for inconvencience. In FSL document for android platform, the following information is mentioned: $ cd myandroid/kernel_imx/arch/arm/boot $ ~/myandroid/bootable/bootloader/uboot-imx/tools/mkimage -A arm -O linux -T kernel -C none -a 0x90008000 -e 0x90008000 -n Android Linux Kernel -d ./zImage ./uImage We will add similar information in all documents. -- lucid uboot hangs on fatload uImage on fsl TO2 TO2.5 and TO3 https://bugs.launchpad.net/bugs/506761 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 506761] Re: lucid uboot hangs on fatload uImage on fsl TO2 TO2.5 and TO3
To build uImage, can change build target from zImage to uImage. For example, make ARCH=arm CROSS_COMPILE=/opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi- uImage You can copy mkimage to /usr/bin/mkimage -- lucid uboot hangs on fatload uImage on fsl TO2 TO2.5 and TO3 https://bugs.launchpad.net/bugs/506761 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 427289] Re: hardware clock not saved if board power is removed on babbage 2.5
Please note BBG2.0 coin-cell battery can not be chargable. If the voltage of coin-cell battery is lower than 1.8V, it can not maintain RTC any more. You can replace another coin-cell battery or use BBG2.5/BBG3.0 whose coin-cell battery can be chargable for tests. -- hardware clock not saved if board power is removed on babbage 2.5 https://bugs.launchpad.net/bugs/427289 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
