Re: [meta-freescale] Yacto rootfs: multi-touch message cannot handled by close button
On 26 September 2013 09:21, Duan Fugang-B38611 b38...@freescale.com wrote: *So, issue: why there have no “ClientMessage event” for EGALAX MULTI TOUCH ?* You don't get a ClientMessage event because the touch isn't being recognised, but you didn't verify that touches are being recognised correctly. Tap inside the xev window itself. Ross ___ 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
On Sep 26, 2013 at 04:26pM, Ross ross.bur...@intel.commailto:ross.bur...@intel.com wrote: On 26 September 2013 09:21, Duan Fugang-B38611 b38...@freescale.com wrote: So, issue: why there have no “ClientMessage event” for EGALAX MULTI TOUCH ? You don't get a ClientMessage event because the touch isn't being recognised, but you didn't verify that touches are being recognised correctly. Tap inside the xev window itself. Ross 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 ? Thanks very much! Andy ___ 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
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. 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 ___ 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: 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. 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 There have some xorg log: (Which shows the touch can be recognized by evdev) For multi touch: [347101.119] (II) config/udev: Adding input device eGalax Touch Screen (/dev/input/event0) [347101.120] (**) eGalax Touch Screen: Applying InputClass evdev touchscreen catchall [347101.120] (II) Using input driver 'evdev' for 'eGalax Touch Screen' [347101.120] (**) eGalax Touch Screen: always reports core events [347101.120] (**) evdev: eGalax Touch Screen: Device: /dev/input/event0 [347101.120] (II) evdev: eGalax Touch Screen: Using mtdev for this device [347101.120] (--) evdev: eGalax Touch Screen: Vendor 0xeef Product 0x20 [347101.120] (--) evdev: eGalax Touch Screen: Found absolute axes [347101.120] (--) evdev: eGalax Touch Screen: Found absolute multitouch axes [347101.120] (II) evdev: eGalax Touch Screen: No buttons found, faking one. [347101.120] (--) evdev: eGalax Touch Screen: Found x and y absolute axes [347101.120] (--) evdev: eGalax Touch Screen: Found absolute touchscreen [347101.120] (II) evdev: eGalax Touch Screen: Configuring as touchscreen [347101.120] (**) evdev: eGalax Touch Screen: YAxisMapping: buttons 4 and 5 [347101.120] (**) evdev: eGalax Touch Screen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [347101.120] (**) Option config_info udev:/sys/devices/soc0/soc.1/210.aips-bus/21a8000.i2c/i2c-2/2-0004/input/input0/event0 [347101.120] (II) XINPUT: Adding extended input device eGalax Touch Screen (type: TOUCHSCREEN, id 8) [347101.121] (II) evdev: eGalax Touch Screen: initialized for absolute axes. [347101.123] (**) eGalax Touch Screen: (accel) keeping acceleration scheme 1 [347101.123] (**) eGalax Touch Screen: (accel) acceleration profile 0 [347101.123] (**) eGalax Touch Screen: (accel) acceleration factor: 2.000 [347101.123] (**) eGalax Touch Screen: (accel) acceleration threshold: 4 [347101.124] (II) config/udev: Adding input device eGalax Touch Screen (/dev/input/mouse0) For single touch: [347100.954] (II) config/udev: Adding input device eGalax Touch Screen (/dev/input/event0) [347100.954] (**) eGalax Touch Screen: Applying InputClass evdev touchscreen catchall [347100.954] (II) Using input driver 'evdev' for 'eGalax Touch Screen' [347100.954] (**) eGalax Touch Screen: always reports core events [347100.954] (**) evdev: eGalax Touch Screen: Device: /dev/input/event0 [347100.954] (--) evdev: eGalax Touch Screen: Vendor 0xeef Product 0x20 [347100.954] (--) evdev: eGalax Touch Screen: Found absolute axes [347100.954] (--) evdev: eGalax Touch Screen: Found x and y absolute axes [347100.954] (--) evdev: eGalax Touch Screen: Found absolute touchscreen [347100.955] (II) evdev: eGalax Touch Screen: Configuring as touchscreen [347100.955] (**) evdev: eGalax Touch Screen: YAxisMapping: buttons 4 and 5 [347100.955] (**) evdev: eGalax Touch Screen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [347100.955] (**) Option config_info udev:/sys/devices/soc0/soc.1/210.aips-bus/21a8000.i2c/i2c-2/2-0004/input/input0/event0 [347100.955] (II) XINPUT: Adding extended input device eGalax Touch Screen (type: TOUCHSCREEN, id 8) [347100.955] (II) evdev: eGalax Touch Screen: initialized for absolute axes. [347100.966] (**) eGalax Touch Screen: (accel) keeping acceleration scheme 1 [347100.966] (**) eGalax Touch Screen: (accel) acceleration profile 0 [347100.967] (**) eGalax Touch Screen: (accel) acceleration factor: 2.000 [347100.967] (**) eGalax Touch Screen: (accel) acceleration threshold: 4 Thanks Andy ___ 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
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 ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] Master - Perf compile error
Hello We are trying to build Yocto master with linux-fslc for a iMX6Q Sabrelite board and we got this error at perf.c: #include lk/debugfs.h No such file or directory This line from perf tool has changed from dylan to master. At dylan it was: #include util/debugfs.h On the other way, linux-imx must have that header (because it compiles with Yocto master) but I don´t know if I can use them ... or how to use them. Also I looked for and I found some people saying linux-fslc does not provide some headers, but I can not find anyone saying how I can add them. Any clue? Thank you and best regards ___ 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
Le Thu, 26 Sep 2013 13:24:59 +, Duan Fugang-B38611 b38...@freescale.com a écrit : 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. I saw that after as the mails arrived in the wrong order here ;-) Eric ___ 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: Eric Bénard [mailto:e...@eukrea.com] Data: Thursday, September 26, 2013 9:32 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 Le Thu, 26 Sep 2013 13:24:59 +, Duan Fugang-B38611 b38...@freescale.com a écrit : 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. I saw that after as the mails arrived in the wrong order here ;-) Eric Ok, do you have any thinking with the issue ? Thanks, Andy ___ 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
Le Thu, 26 Sep 2013 13:33:41 +, Duan Fugang-B38611 b38...@freescale.com a écrit : Ok, do you have any thinking with the issue ? no idea, I'm not using X nor this display. Eric ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Master - Perf compile error
Hi
We do a ./repo sync and bitbaked again.
After some hours, it give us another compile error at these stddefs.h
lines compilin a qt-x11 module:
enum {
false=0,
true=1
}
The error: undeclared identifier false.
We want to compile the master-branch + linux-fscl to see how last
graphic driver works. Perhaps is it not a good idea since master can be
more unstable? Or must it work mostly of times?
Thanks
El 26/09/2013 14:24, Jose Mª Ferreiro escribió:
Hello
We are trying to build Yocto master with linux-fslc for a iMX6Q
Sabrelite board and we got this error at perf.c:
#include lk/debugfs.h No such file or directory
This line from perf tool has changed from dylan to master. At dylan it
was:
#include util/debugfs.h
On the other way, linux-imx must have that header (because it compiles
with Yocto master) but I don´t know if I can use them ... or how to
use them.
Also I looked for and I found some people saying linux-fslc does not
provide some headers, but I can not find anyone saying how I can add
them.
Any clue?
Thank you and best regards
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] GStreamer: Request a key frame in vpuenc
Hi, this is a quite specific question, so tell me if this is not the correct place to ask I need to generate a keyframe in a specific time. Looking to the code of vpuenc, seems that it doesnt handle events from downstream (GST_EVENT_CUSTOM_DOWNSTREAM) to check if the event request a keyframe: gst_video_event_is_force_key_unit (event) This can be easily implementable but my question is: what is the specific option I have to pass to the vpu to generate a keyframe? I read about encparam-forceIPicture , but Im not sure Im looking in the correct direction Could someone help me with this? Thanks -- Javier Jardón Cabezas ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] GStreamer: Request a key frame in vpuenc
This is probably not the right list. I would push this to the Freescale Community at community.freescale.com. On 9/26/13 7:16 PM, Javier Jardón wrote: Hi, this is a quite specific question, so tell me if this is not the correct place to ask I need to generate a keyframe in a specific time. Looking to the code of vpuenc, seems that it doesnt handle events from downstream (GST_EVENT_CUSTOM_DOWNSTREAM) to check if the event request a keyframe: gst_video_event_is_force_key_unit (event) This can be easily implementable but my question is: what is the specific option I have to pass to the vpu to generate a keyframe? I read about encparam-forceIPicture , but Im not sure Im looking in the correct direction Could someone help me with this? Thanks ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
