Re: [meta-freescale] error(Segmentation fault) when i launch the gstreamer with mfw_isink in the second time
On Sun, Sep 29, 2013 at 12:19 AM, jojo rjie...@gmail.com wrote: Hi, Anyone met this issue ? * The first time i launch the player with isink log as bellow : MAX resolution 1920x1080 set color key MFW_GST_ISINK_PLUGIN 3.0.5 build on Sep 16 2013 14:09:24. stream_mjpeg_init:265:streamer(1c7a00) [INFO] Product Info: i.MX6Q/D/S vpudec versions :) plugin: 3.0.5 wrapper: 1.0.24(VPUWRAPPER_ARM_LINUX Build on Sep 12 2013 10:39:29) vpulib: 5.4.10 firmware: 2.1.8.34588 [INFO] bitstreamMode 1, chromaInterleave 0, mapType 0, tiled2LinearEnable 0 hwbuf allocator zone(2306048) created can not create threadmfw_gst_isink_setcaps:1489 VS0 created. in fmt[I420] win(0,0-1920,800:1920x800) out win(0,140-1920,940:1920x800) set deinterlace mode 0 * The log as bellow when i stop the streaming (stop the gstreamer pipe): VS0 destroyed, force=0! hwbuf allocator zone(2306048) destroied. * The second time i launch the player with isink log as bellow : set color key MFW_GST_ISINK_PLUGIN 3.0.5 build on Sep 16 2013 14:09:24. stream_mjpeg_init:265:streamer(1c8f90) [INFO] Product Info: i.MX6Q/D/S vpudec versions :) plugin: 3.0.5 wrapper: 1.0.24(VPUWRAPPER_ARM_LINUX Build on Sep 12 2013 10:39:29) vpulib: 5.4.10 firmware: 2.1.8.34588 [INFO] bitstreamMode 1, chromaInterleave 0, mapType 0, tiled2LinearEnable 0 hwbuf allocator zone(2306048) created can not create threadmfw_gst_isink_setcaps:1489 VS0 created. in fmt[I420] win(0,0-1920,800:1920x800) out win(0,140-1920,940:1920x800) set deinterlace mode 0 Can not open dll, libgstfsl-0.10.so: cannot open shared object file: No such file or directory. Segmentation fault ... Please try to reproduce it using 'dora' branch so we can know if it still happens or not. I think most of these issues has been fixed in last MM codecs releases so it's worth a try. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Yacto rootfs: multi-touch message cannot handled by close button
From: Peter Hutterer [mailto:peter.hutte...@who-t.net] Sent: Monday, September 30, 2013 9:14 AM To: Duan Fugang-B38611 Cc: Eric Bénard; Burton, Ross; meta-freescale@yoctoproject.org; Rutledge Shawn Subject: Re: [meta-freescale] Yacto rootfs: multi-touch message cannot handled by close button On Thu, Sep 26, 2013 at 01:24:59PM +, Duan Fugang-B38611 wrote: From: Eric Bénard [mailto:e...@eukrea.com] Data: Thursday, September 26, 2013 5:46 PM To: Duan Fugang-B38611 Cc: Burton, Ross; meta-freescale@yoctoproject.org; peter.hutterer@who- t.net; Rutledge Shawn Subject: Re: [meta-freescale] Yacto rootfs: multi-touch message cannot handled by close button Hi Duan, Le Thu, 26 Sep 2013 09:25:12 +, Duan Fugang-B38611 b38...@freescale.com a écrit : There have some xorg log: (Which shows the touch can be recognized by evdev) Ross asked you to launch xev from your console and touch the screen in the xev window so that you can provide xev's log to understand your problem. More info about xev : http://manpages.ubuntu.com/manpages/hardy/man1/xev.1.html Eric I had sent out the test result as the previous email as attached mail. Thanks, Andy Date: Thu, 26 Sep 2013 09:19:12 + From: Duan Fugang-B38611 b38...@freescale.com To: Burton, Ross ross.bur...@intel.com CC: peter.hutte...@who-t.net peter.hutte...@who-t.net, Rutledge Shawn shawn.rutle...@digia.com, meta-freescale@yoctoproject.org meta-freescale@yoctoproject.org Subject: RE: Yacto rootfs: multi-touch message cannot handled by close button From: Burton, Ross [mailto:ross.bur...@intel.com] Data: Thursday, September 26, 2013 4:51 PM To: Duan Fugang-B38611 Cc: peter.hutte...@who-t.net; Rutledge Shawn; meta- freesc...@yoctoproject.org Subject: Re: Yacto rootfs: multi-touch message cannot handled by close button On 26 September 2013 09:46, Duan Fugang-B38611 b38...@freescale.com wrote: Ross, thanks for your quick response. Why the touch can be recognized in the single touch mode ? Since the driver is similar the same except report event types. And, how to validate whether the touch can be recognized ? I don't know why it can't be recognised in multitouch, and unless you send me your hardware I can't tell you. That's what we're attempting to debug over email. My hardware: Board: Imx6q sabresd Touchscreen: hannStar display with egalax i2c touchscreen As far as xev is concerned there should be zero difference between using a mouse to click in the window, and using the touchscreen. Try all combinations of pressing/clicking in the xev window, and report back. Ross ØFor EGALAX MULTI TOUCH: o When click the “X” icon to close window, the window cannot be closed, and print the log: (picture #1) LeaveNotify event, serial 28, synthetic NO, window 0x101, root 0xc2, subw 0x0, time 347181500, (981,-34), root:(981,14), mode NotifyNormal, detail NotifyNonlinear, same_screen YES, focus YES, state 0 o When click the control bar: (picture #2) LeaveNotify event, serial 28, synthetic NO, window 0x101, root 0xc2, subw 0x0, time 348522728, (375,-26), root:(375,22), mode NotifyNormal, detail NotifyNonlinear, same_screen YES, focus YES, state 0 o When click the blank region: (picture #3) MotionNotify event, serial 28, synthetic NO, window 0x101, root 0xc2, subw 0x0, time 348582340, (289,92), root:(289,140), state 0x0, is_hint 0, same_screen YES ButtonPress event, serial 28, synthetic NO, window 0x101, root 0xc2, subw 0x0, time 348582340, (289,92), root:(289,140), state 0x100, button 1, same_screen YES ButtonRelease event, serial 28, synthetic NO, window 0x101, root 0xc2, subw 0x0, time 348582619, (289,92), root:(289,140), state 0x100, button 1, same_screen YES o When click the other icons on the control bar, work fine and there have sub-window pop: (picture #4) FocusOut event, serial 28, synthetic NO, window 0x101, mode NotifyGrab, detail NotifyNonlinear VisibilityNotify event, serial 28, synthetic NO, window 0x101, state VisibilityPartiallyObscured All other operations are right, only clicking X icon cannot close the windows. xev only listens to windows in the white area. the window decorations are provided by the window manager, which should also handle the event on the close button. if your WM is QT based, maybe QT has some debugging options you can enable? I'm not sure off-heart. Yes, the current WM is based QT. Thanks for your suggestion. For single touch, xev can listen the ClientMessage event with message 0x107 (WM_DELETE_WINDOW) when click the X to close the window in
Re: [meta-freescale] Update Kernel and u-boot for GK802
On Sun, Sep 29, 2013 at 11:31 PM, Ajay Ramaswamy a...@ramaswamy.net wrote: Hi, Here is my set of changes to the GK802 support to bring it up to the current kernel, the current u-boot fails to compile 1. Update the u-boot to v2013.04 from freescale with abrasive's patches Just a suggestion: it would be better if you could base your patches against mainline U-boot and send them to the U-boot list for inclusion in the official project repository. ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Update Kernel and u-boot for GK802
The patches provided by abrasive apply cleanly against 2013.07 but beyond that in 2013.10 there are more changes which I don't know how to handle. My biggest problem is with https://github.com/ajayramaswamy/u-boot-gk802/commit/950008d5e714606ead5d5b11ba1b8c92c84d6ee1I don't know what to do about the long long math for the screen resolution stuff so I just commented it out! In fact in the barebox git there is a mostly functional gk802 device tree I have used that and booted a 3.11 kernel but unfortunately the wifi does not work and I dont have any idea about how to fix it I was hoping someone more capabable than me would take this up and push these patches upstream Thanks Ajay On Mon, Sep 30, 2013 at 8:24 AM, Fabio Estevam feste...@gmail.com wrote: On Sun, Sep 29, 2013 at 11:31 PM, Ajay Ramaswamy a...@ramaswamy.net wrote: Hi, Here is my set of changes to the GK802 support to bring it up to the current kernel, the current u-boot fails to compile 1. Update the u-boot to v2013.04 from freescale with abrasive's patches Just a suggestion: it would be better if you could base your patches against mainline U-boot and send them to the U-boot list for inclusion in the official project repository. -- Thanks best regards Ajay ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Update Kernel and u-boot for GK802
On Mon, Sep 30, 2013 at 12:24 AM, Ajay Ramaswamy a...@ramaswamy.net wrote: The patches provided by abrasive apply cleanly against 2013.07 but beyond that in 2013.10 there are more changes which I don't know how to handle. My biggest problem is with https://github.com/ajayramaswamy/u-boot-gk802/commit/950008d5e714606ead5d5b11ba1b8c92c84d6ee1 I don't know what to do about the long long math for the screen resolution stuff so I just commented it out! I would just keep a hard coded resolution in U-boot like we do in other boards. In fact in the barebox git there is a mostly functional gk802 device tree I have used that and booted a 3.11 kernel but unfortunately the wifi does not work and I dont have any idea about how to fix it Which Wifi chipset does this board have and which interface does it connect to (SDIO, USB)? Regards, Fabio Estevam ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [meta-fsl-ppc master][PATCH] fmlib: fix compile error with linux-libc-headers
From: Chunrong Guo b40...@freescale.com
* fix the below error
| NOTE: make -j 48
DESTDIR=/poky/build/tmp/work/ppce500mc-poky-linux/fmlib/git-r1/image
PREFIX=/usr LIB_DEST_DIR=/usr/lib| CROSS_COMPILE=powerpc-poky-linux-
KERNEL_SRC=/poky/build/tmp/sysroots/p4080ds/usr libfm-ppce500mc.a
| (CC) libfm-ppce500mc.o
| src/fm_lib.c:56:23: fatal error: fm_ioctls.h: No such file or directory
Signed-off-by: Chunrong Guo b40...@freescale.com
---
recipes-dpaa/fmlib/fmlib_git.bb |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/recipes-dpaa/fmlib/fmlib_git.bb b/recipes-dpaa/fmlib/fmlib_git.bb
index 7a7b8f2..9d34fcc 100644
--- a/recipes-dpaa/fmlib/fmlib_git.bb
+++ b/recipes-dpaa/fmlib/fmlib_git.bb
@@ -5,7 +5,6 @@ LIC_FILES_CHKSUM =
file://COPYING;md5=3f16fa8e677e45af3127c5c4bafc3c00
PR = r1
-DEPENDS = linux-libc-headers
DEPENDS_virtclass-native =
SRC_URI = git://git.freescale.com/ppc/sdk/fmlib.git
@@ -20,7 +19,7 @@ COMPATIBLE_HOST_fslmachine = .*
COMPATIBLE_HOST ?= (none)
EXTRA_OEMAKE = DESTDIR=${D} PREFIX=${prefix} LIB_DEST_DIR=${libdir} \
-CROSS_COMPILE=${TARGET_PREFIX} KERNEL_SRC=${STAGING_EXECPREFIXDIR}
+CROSS_COMPILE=${TARGET_PREFIX} KERNEL_SRC=${STAGING_KERNEL_DIR}
do_compile () {
oe_runmake libfm-${TARGET_ARCH_FMLIB}.a
--
1.7.5.4
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
