Re: [IVI] building tizen ivi with yocto
Hi Joachim, On 29.02.2016 20:55, joachim rodrigues wrote: Hi Thanks Indeed i din't set up my env. OK, you are welcome. But now i'm getting : NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks WARNING: Failed to fetch URL http://downloads.sourceforge.net/project/libpng/libpng16/1.6.13/libpng-1.6.13.tar.xz, attempting MIRRORS if available WARNING: Failed to fetch URL http://www.apache.org/dist/apr/apr-1.5.1.tar.bz2, attempting MIRRORS if available WARNING: Failed to fetch URL ftp://ftp.freedesktop.org/pub/mesa/10.3.4/MesaLib-10.3.4.tar.bz2, attempting MIRRORS if available WARNING: Failed to fetch URL http://www.apache.org/dist/apr/apr-util-1.5.3.tar.gz, attempting MIRRORS if available WARNING: Failed to fetch URL git://review.tizen.org/platform/upstream/libbullet;tag=03875b02d03ae029f38cb35dc90ee3ff6d5fe696;nobranch=1, attempting MIRRORS if available ERROR: Fetcher failure: Fetch command failed with exit code 128, output: Cloning into bare repository '/home/allstar/dev/tizen/tizen-distro/build-modello/downloads/git2/review.tizen.org.platform.upstream.libbullet'... fatal: read error: Connection reset by peer ERROR: Function failed: Fetcher failure for URL: 'git://review.tizen.org/platform/upstream/libbullet;tag=03875b02d03ae029f38cb35dc90ee3ff6d5fe696;nobranch=1'. Unable to fetch URL from any source. ERROR: Logfile of failure stored in: /home/allstar/dev/tizen/tizen-distro/build-modello/tmp-glibc/work/core2-64-oe-linux/bullet/2.81-r0/temp/log.do_fetch.14199 ERROR: Task 3616 (/home/allstar/dev/tizen/tizen-distro/meta-tizen/meta-tizen-common-base/recipes-core/bullet/bullet_git.bb, do_fetch) failed with exit code '1' Waiting for 0 running tasks to finish: NOTE: Tasks Summary: Attempted 818 tasks of which 560 didn't need to be rerun and 1 failed. Waiting for 0 running tasks to finish: Summary: 1 task failed: /home/allstar/dev/tizen/tizen-distro/meta-tizen/meta-tizen-common-base/recipes-core/bullet/bullet_git.bb, do_fetch Summary: There were 5 WARNING messages shown. Summary: There were 2 ERROR messages shown, returning a non-zero exit code. The error log shows a issue while fetching the source code of libbullet from its Git repo in the Tizen project. I just checked that repo manually and I was able to clone it and checkout version03875b02d03ae029f38cb35dc90ee3ff6d5fe696. May be you had a temporary Internet connection issue or something was wrong with your Tizen dev credentials again. Could you please try cleaning the recipe and running it again? Best regards, Leon Thanks in advance Subject: Re: [IVI] building tizen ivi with yocto To: joa_rodrig...@hotmail.com; ivi@lists.tizen.org From: leon.an...@konsulko.com Date: Mon, 29 Feb 2016 00:00:32 +0200 Hi Joachim, On 28.02.2016 22:45, joachim rodrigues wrote: Hi I'm following this wiki : https://wiki.tizen.org/wiki/Build_Tizen_with_Yocto_Project But i'm getting this error : When : bitbake tizen-ivi-Modello-image On a ubunbu 14.04 LTS ERROR: Fetcher failure: Fetch command failed with exit code 128, output: Cloning into bare repository '/home/allstar/dev/tizen/tizen-distro/build-modello/downloads/git2/review.tizen.org.platform.upstream.systemd'... fatal: read error: Connection reset by peer ERROR: Function failed: Fetcher failure for URL: 'git://review.tizen.org/platform/upstream/systemd;tag=95e1a70c5104b47874519b24e12022e878f2572a;nobranch=1'. Unable to fetch URL from any source. ERROR: Logfile of failure stored in: /home/allstar/dev/tizen/tizen-distro/build-modello/tmp-glibc/work/core2-64-oe-linux/systemd/216-r0/temp/log.do_fetch.17301 ERROR: Task 1481 (/home/allstar/dev/tizen/tizen-distro/meta-tizen/meta-tizen-common-base/recipes-core/systemd/systemd_git.bb, do_fetch) failed with exit code '1' Waiting for 0 running tasks to finish: NOTE: Tasks Summary: Attempted 516 tasks of which 7 didn't need to be rerun and 1 failed. Waiting for 0 running tasks to finish: Summary: 1 task failed: /home/allstar/dev/tizen/tizen-distro/meta-tizen/meta-tizen-common-base/recipes-core/systemd/systemd_git.bb, do_fetch Summary: There were 5 WARNING messages shown. Summary: There were 2 ERROR messages shown, returning a non-zero exit code. Can anyone help ? Have you successfully setup your developer environment following this article: https://source.tizen.org/documentation/developer-guide/environment-setup ? Best regards, Leon Thanks ___ IVI mailing list IVI@lists.tizen.org <mailto:IVI@lists.tizen.org> https://lists.tizen.org/listinfo/ivi -- Leon Anavi Software Engineer konsulko.com -- Leon Anavi Software Engineer konsulko.com ___ IVI mailing list IVI@lists.tizen.org
Re: [IVI] About publishing/testing a Tizen IVI application
Hi Karray, Philippe, On 5.02.2016 16:25, Philippe Coval wrote: I am not aware of any Tizen Store for Tizen:IVI can it run on qemu ? https://wiki.tizen.org/wiki/Emulator ? Karray, you have to build QEMU with YAGL to run Tizen IVI on it. The instructions are available at the wiki: https://wiki.tizen.org/wiki/Emulator#Build_QEMU_with_YAGL_from_Scratch After that run Tizen IVI image in the QEMU emulator and deploy your applications. I used the emulator for similar purposes several months ago with HTML5 applications for Tizen. User's manual regarding the installation of wgt files on Tizen Common and Tizen IVI is available here: https://wiki.tizen.org/wiki/Installing_Web_Applications_on_Tizen:Common_and_Tizen_IVI Best regards, Leon If you want to let other know about your app maybe it worth to have it listed there too , https://wiki.tizen.org/wiki/Applications Can you do also add all details on your Tizen version on that page ? And then let you share it to others... I have other ideas/project in my head, I'll talk about later. Later On Fri, Feb 5, 2016 at 3:05 PM, Karray Gargouri <karray.gargo...@esprit.tn <mailto:karray.gargo...@esprit.tn>> wrote: Hello, I am developping a Tizen IVI application using the Tizen IVI SDK, and I would like to know where could I deploy it? and is there any alternative to test it. I look for some news on the Tizen store but I was told to send a mail to the (ivi@lists.tizen.org <mailto:ivi@lists.tizen.org>) Thanks a lot -- /*Karray GARGOURI* -- /Ingénieur en informatique - Assistant Technologue à _ESPRIT__►_ *Membre de l'Equipe ESPRIT Mobile* ___ IVI mailing list IVI@lists.tizen.org <mailto:IVI@lists.tizen.org> https://lists.tizen.org/listinfo/ivi -- -- https://wiki.tizen.org/wiki/User:Pcoval ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi -- Leon Anavi Software Engineer konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
[IVI] Fixes to build Tizen using Yocto/OE when DEBUG_BUILD = "1"
Hi Mauro, All, Please review my changes for meta-tizen related to issues with tizen-common-core-image-crosswalk when DEBUG_BUILD = "1" is set at conf/local.conf: https://review.tizen.org/gerrit/51560 https://review.tizen.org/gerrit/51561 https://review.tizen.org/gerrit/51562 Best regards, Leon -- Leon Anavi Software Engineer konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] Build error about tizen on yocto when building ico image
Hi Ray,
On 20.10.2015 09:17, RayBloodworth wrote:
Hi, Leon
I have built tizen-core-image-dev with tizen on yocto successfully.
But some errors occured when building tizen-ivi-ico-image-dev:
bitbake tizen-ivi-ico-image-dev
Loading cache: 100% |###| ETA:
00:00:00
Loaded 2517 entries from dependency cache.
Parsing recipes: 100% |#|
Time: 00:00:00
Parsing of 1836 .bb files complete (1835 cached, 1 parsed). 2515
targets, 180 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'glibc-native' (but
virtual:native:/home/compile/yocto/imx6qsabresd-ivi/dizzy/tizen-distro/meta-tizen/meta-tizen-common-base/recipes-framework/notification/notification_git.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'glibc-native' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['glibc-native']
NOTE: Runtime target 'ico-uxf-homescreen' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ico-uxf-homescreen',
'pkgmgr-native', 'notification-native', 'glibc-native']
NOTE: Runtime target 'packagegroup-tizen-ivi-ico' is unbuildable,
removing...
Missing or unbuildable dependency chain was:
['packagegroup-tizen-ivi-ico', 'ico-uxf-homescreen', 'pkgmgr-native',
'notification-native', 'glibc-native']
ERROR: Required build target 'tizen-ivi-ico-image-dev' has no
buildable providers.
Missing or unbuildable dependency chain was:
['tizen-ivi-ico-image-dev', 'packagegroup-tizen-ivi-ico',
'ico-uxf-homescreen', 'pkgmgr-native', 'notification-native',
'glibc-native']
Summary: There were 2 ERROR messages shown, returning a non-zero exit
code.
Could you give me any advices?
According to the log there is a runtime dependency issue coming from
glibc-native. I guess these dependency issues are coming from the
automatic generation of Yocto recipes from the spec files for GBS. May
be you will be able to fix it with something like:
RDEPENDS_${PN}_remove_class-native = "glibc-native"
Btw you can browse the existing recipes in meta-tizen for examples.
Best regards,
Leon
BR,
Ray
--
Leon Anavi
Software Engineer
konsulko.com
___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi
Re: [IVI] Build error about tizen on yocto when building ico image
Hi Ray,
On 20.10.2015 13:21, RayBloodworth wrote:
Hi, Leon
Thank you!
This error has been solved in your advice.
OK, you are welcome :)
Now, I got another problem and find that was caused by systemd
package. Some packages named [package name]-native require systemd
items in /sysroot/x86_64-linux/ .
There are two systemd.bb file :
/home/compile/yocto/imx6qsabresd-ivi/dizzy/tizen-distro/meta/recipes-core/systemd
/home/compile/yocto/imx6qsabresd-ivi/dizzy/tizen-distro/meta-tizen/meta-tizen-common-base/recipes-core/systemd
First one would be built by default. How to config files so that
the second one could be built by default ?
I am not exactly sure what is the problem in this case. I guess that the
logs can reveal more details.
As I have described in the Tizen wiki article about building an image
for HummingBoard with Yocto/OE, you should include the following
instructions at conf/local.conf to use systemd on i.MX6 devices:
DISTRO_FEATURES_append = " systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
VIRTUAL-RUNTIME_initscripts = ""
Best regards,
Leon
Thanks!
BR,
Ray
Subject: Re: Build error about tizen on yocto when building ico image
To: k870818...@outlook.com
CC: d...@lists.tizen.org; ivi@lists.tizen.org
From: leon.an...@konsulko.com
Date: Tue, 20 Oct 2015 11:46:23 +0300
Hi Ray,
On 20.10.2015 09:17, RayBloodworth wrote:
Hi, Leon
I have built tizen-core-image-dev with tizen on yocto
successfully.
But some errors occured when building tizen-ivi-ico-image-dev:
bitbake tizen-ivi-ico-image-dev
Loading cache: 100% |###|
ETA: 00:00:00
Loaded 2517 entries from dependency cache.
Parsing recipes: 100% |#|
Time: 00:00:00
Parsing of 1836 .bb files complete (1835 cached, 1 parsed). 2515
targets, 180 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'glibc-native' (but
virtual:native:/home/compile/yocto/imx6qsabresd-ivi/dizzy/tizen-distro/meta-tizen/meta-tizen-common-base/recipes-framework/notification/notification_git.bb
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'glibc-native' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['glibc-native']
NOTE: Runtime target 'ico-uxf-homescreen' is unbuildable, removing...
Missing or unbuildable dependency chain was:
['ico-uxf-homescreen', 'pkgmgr-native', 'notification-native',
'glibc-native']
NOTE: Runtime target 'packagegroup-tizen-ivi-ico' is unbuildable,
removing...
Missing or unbuildable dependency chain was:
['packagegroup-tizen-ivi-ico', 'ico-uxf-homescreen',
'pkgmgr-native', 'notification-native', 'glibc-native']
ERROR: Required build target 'tizen-ivi-ico-image-dev' has no
buildable providers.
Missing or unbuildable dependency chain was:
['tizen-ivi-ico-image-dev', 'packagegroup-tizen-ivi-ico',
'ico-uxf-homescreen', 'pkgmgr-native', 'notification-native',
'glibc-native']
Summary: There were 2 ERROR messages shown, returning a non-zero
exit code.
Could you give me any advices?
According to the log there is a runtime dependency issue coming from
glibc-native. I guess these dependency issues are coming from the
automatic generation of Yocto recipes from the spec files for GBS. May
be you will be able to fix it with something like:
RDEPENDS_${PN}_remove_class-native = "glibc-native"
Btw you can browse the existing recipes in meta-tizen for examples.
Best regards,
Leon
BR,
Ray
--
Leon Anavi
Software Engineer
konsulko.com
--
Leon Anavi
Software Engineer
konsulko.com
___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi
Re: [IVI] Build error about tizen on yocto when building ico image
r otherwise requires it)
NOTE: Runtime target 'glibc-native' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['glibc-native']
NOTE: Runtime target 'ico-uxf-homescreen' is unbuildable,
removing...
Missing or unbuildable dependency chain was:
['ico-uxf-homescreen', 'pkgmgr-native', 'notification-native',
'glibc-native']
NOTE: Runtime target 'packagegroup-tizen-ivi-ico' is
unbuildable, removing...
Missing or unbuildable dependency chain was:
['packagegroup-tizen-ivi-ico', 'ico-uxf-homescreen',
'pkgmgr-native', 'notification-native', 'glibc-native']
ERROR: Required build target 'tizen-ivi-ico-image-dev' has no
buildable providers.
Missing or unbuildable dependency chain was:
['tizen-ivi-ico-image-dev', 'packagegroup-tizen-ivi-ico',
'ico-uxf-homescreen', 'pkgmgr-native', 'notification-native',
'glibc-native']
Summary: There were 2 ERROR messages shown, returning a
non-zero exit code.
Could you give me any advices?
According to the log there is a runtime dependency issue coming
from glibc-native. I guess these dependency issues are coming from
the automatic generation of Yocto recipes from the spec files for
GBS. May be you will be able to fix it with something like:
RDEPENDS_${PN}_remove_class-native = "glibc-native"
Btw you can browse the existing recipes in meta-tizen for examples.
Best regards,
Leon
BR,
Ray
--
Leon Anavi
Software Engineer
konsulko.com
--
Leon Anavi
Software Engineer
konsulko.com
--
Leon Anavi
Software Engineer
konsulko.com
___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi
Re: [IVI] Keyboard issues with Weston and AGL application suite
Hi Derek, On 19.10.2015 22:29, Derek Foreman wrote: On 19/10/15 10:32 AM, Leon Anavi wrote: Hi Derek, On 19.10.2015 17:16, Derek Foreman wrote: On 19/10/15 04:44 AM, Leon Anavi wrote: Hi Derek, On 14.10.2015 23:37, Leon Anavi wrote: Hi Derek, On 14.10.2015 20:11, Derek Foreman wrote: On 14/10/15 05:31 AM, Leon Anavi wrote: Hi Derek, All, Derek, I am experiencing similar issues with weston-keyboard as in your article "When is a Keyboard Not a Keyboard?" which has been published at Samsung OSG blog. Could you please provide me help how to get Weston 1.6 working with the virtual weston-keyboard in the HTML5 apps from the AGL app suite when hardware keyboard is not present? Looks like a bug I fixed last December, actually: http://cgit.freedesktop.org/wayland/weston/commit/?id=f0aaa417 Fairly small so it might be an easy forward port... Thank you for the provided feedback. I applied a patch with this bug fix to Weston 1.6 but I am still experiencing the same issue (as described in my previous email). It is a bit late here so I will continue debugging it tomorrow. After further exploration of various log files I noticed that the issues while running AGL app suite on Tizen with Crosswalk, Wayland and Weston 1.6 do not appear if an event from /dev/input is detected as a keyboard. As a work around a colleague from Konsulko Group defined a GPIO as a key at the device tree. This way the GPIO is detected by Weston as a keyboard: That's quite clever, and I'll try to remember it. :) Yes, thank you, I am lucky to work with experienced kernel developers at Konsulko Group :) Last time someone asked me for a way to create fake keyboard presence, I suggested writing a program with uinput - but if you've got control over your device tree your approach is much simpler. Yes, uinput was next on my list for a work around. [00:00:08.831] input device 'gpio-keys.22', /dev/input/event1 is a keyboard The configuration of Weston is: [input-method] path=/usr/libexec/weston-keyboard [keyboard] keymap_layout=us Derek, in this case we are using the behavior described in your article "When is a Keyboard Not a Keyboard" for the work around. Please let me know how can I help you find and fix the root cause of the problem as it seems to be a Weston issue. It's definitely a weston issue and not one of configuration, but it's hard to tell if it's already been fixed upstream. Do you have (or can you easily build) weston-editor for your platform? It's part of the weston repository... If you can reproduce the crash with that then I can reproduce it on my desktop here and fix it promptly. I've tried weston-editor on my rpi2 and it will crash when no real keyboard is present. The virtual keyboard pops up, but switching between numeric and alphabetic entry crashes. This is the bug I gave you the patch for previously, so I think whatever you've found can't be triggered with weston-editor. This afternoon I also included weston-editor in my image with Weston 1.6. Exactly as you described, it crashed when a real keyboard is not present (of course, for the test I used a device tree without a fake keyboard). After that I applied the patch that you pointed out from the upstream and with it weston-editor is working fine. Furthermore, the Browser from AGL application suite is also working fine. So obviously it is the same problem in both cases and the patch solves it. Somehow last week I did not apply it properly. Thank you for the help. A backtrace of weston when it fails would also be quite helpful. Is it possible to build an image that can reproduce this problem that runs on an intel machine? I have an old laptop I could re-image (I can knock the keyboard device registration bits out of weston to mimic lack of keyboard presence easily enough...) Yes, I can build an image for Intel machines. I am not sure if the bug will appear on them. In general it should be possible to boot this Tizen image from USB stick. Btw, based on my experience Intel NUC and MinnowBoard MAX are useful for testing Tizen 3 on Intel. I will give it a try. I have a NUC here - it probably won't crash because the acpi power button will be enough of a keyboard to mask the bug. Yes, you are right. I did a test on Intel NUC with Tizen:Common (built using Yocto/OE). Weston 1.6 detects the power and the sleep buttons as keyboards: [20:07:59.343] input device 'Power Button', /dev/input/event0 is a keyboard [20:07:59.344] input device 'Sleep Button', /dev/input/event1 is a keyboard Best regards, Leon Weston can be tricked into ignoring keyboards if you comment out the LIBINPUT_DEVICE_CAP_KEYBOARD clause in evdev_device_create() in libinput-device.c hitting a key on a real keyboard will cause a crash, but it should allow mimicking a keyboardless situation on an intel device. If you can supply an image or help me through the build process to get an intel image I can reproduce this on, I can probably get it s
Re: [IVI] IVI System Black screen after boot up with weston
that you should launch Weston with fbdev-backend.
You might be also experiencing incompatibility between the driver
version for Vivante GPU in the kernel and the firmware blobs in the
user space. Which kernel version are you using? Is it 3.14?
Btw I see that weekeyboard is not available. You should either built
it or just replace it with weston-keyboard in weston configuration file.
Best regards,
Leon
Thanks !
BR,
Ray
--
Leon Anavi
Software Engineer
konsulko.com
--
Leon Anavi
Software Engineer
konsulko.com
___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi
Re: [IVI] Keyboard issues with Weston and AGL application suite
Hi Derek, On 14.10.2015 23:37, Leon Anavi wrote: Hi Derek, On 14.10.2015 20:11, Derek Foreman wrote: On 14/10/15 05:31 AM, Leon Anavi wrote: Hi Derek, All, Derek, I am experiencing similar issues with weston-keyboard as in your article "When is a Keyboard Not a Keyboard?" which has been published at Samsung OSG blog. Could you please provide me help how to get Weston 1.6 working with the virtual weston-keyboard in the HTML5 apps from the AGL app suite when hardware keyboard is not present? Looks like a bug I fixed last December, actually: http://cgit.freedesktop.org/wayland/weston/commit/?id=f0aaa417 Fairly small so it might be an easy forward port... Thank you for the provided feedback. I applied a patch with this bug fix to Weston 1.6 but I am still experiencing the same issue (as described in my previous email). It is a bit late here so I will continue debugging it tomorrow. After further exploration of various log files I noticed that the issues while running AGL app suite on Tizen with Crosswalk, Wayland and Weston 1.6 do not appear if an event from /dev/input is detected as a keyboard. As a work around a colleague from Konsulko Group defined a GPIO as a key at the device tree. This way the GPIO is detected by Weston as a keyboard: [00:00:08.831] input device 'gpio-keys.22', /dev/input/event1 is a keyboard The configuration of Weston is: [input-method] path=/usr/libexec/weston-keyboard [keyboard] keymap_layout=us Derek, in this case we are using the behavior described in your article "When is a Keyboard Not a Keyboard" for the work around. Please let me know how can I help you find and fix the root cause of the problem as it seems to be a Weston issue. Best regards, Leon Thanks, Leon Hope that helps a bit, Derek In my case Weston keeps crashing when I type in HTML5 input fields from the AGL apps through the virtual weston-keyboard if no hardware keyboard is attached. I am working on a Tizen image that contains Wayland and Weston 1.6, Crosswalk 11.40.277.0 and libinput 0.6.0. Please have a look at my test cases for more details: * Test case 1, weston.ini: [input-method] path=/usr/libexec/weston-keyboard [keyboard] keymap_layout=wkb Results: 1.1. No hardware keyboard: FAIL Weston crashes when the user tries to launch Browser from the Homescreen app: [00:00:32.676] caught signal: 11 1.2. With hardware keyboard: FAIL Weston detects the hardware keyboard: [00:00:07.480] input device 'SEM USB Keyboard', /dev/input/event0 is a keyboard [00:00:07.481] input device 'SEM USB Keyboard', /dev/input/event1 is a keyboard Weston crashes when the user tries to launch Browser from the Homescreen app: [00:00:49.925] caught signal: 11 * Test case 2, weston.ini: [input-method] path= [keyboard] keymap_layout=wkb Results: 2.1. No hardware keyboard: OK with remark - there is no virtual keyboard (as expected) so there is no way to type. 2.2. With hardware keyboard: FAIL Weston detects the hardware keyboard: [00:00:06.586] input device 'SEM USB Keyboard', /dev/input/event0 is a keyboard [00:00:06.587] input device 'SEM USB Keyboard', /dev/input/event1 is a keyboard Weston fails as soon as the user starts to type in HTML5 input field for URL at the Browser app through the hardware keyboard: [00:00:48.006] caught signal: 11 * Test case 3, weston.ini: [input-method] path=/usr/libexec/weston-keyboard [keyboard] keymap_layout=us Results: 3.1. No hardware keyboard: FAIL Weston crashes when the user tries to launch Browser from the Homescreen app: [00:00:28.391] caught signal: 11 3.2. With hardware keyboard: OK Weston detects the hardware keyboard and both the hardware and virtual weston-keyboard work fine: [00:00:06.767] input device 'SEM USB Keyboard', /dev/input/event0 is a keyboard [00:00:06.771] input device 'SEM USB Keyboard', /dev/input/event1 is a keyboard I want to get weston-keyboard working fine in Weston even if there is no hardware keyboard. Thanks, Leon -- Leon Anavi Software Engineer konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] Keyboard issues with Weston and AGL application suite
Hi Derek, On 19.10.2015 17:16, Derek Foreman wrote: On 19/10/15 04:44 AM, Leon Anavi wrote: Hi Derek, On 14.10.2015 23:37, Leon Anavi wrote: Hi Derek, On 14.10.2015 20:11, Derek Foreman wrote: On 14/10/15 05:31 AM, Leon Anavi wrote: Hi Derek, All, Derek, I am experiencing similar issues with weston-keyboard as in your article "When is a Keyboard Not a Keyboard?" which has been published at Samsung OSG blog. Could you please provide me help how to get Weston 1.6 working with the virtual weston-keyboard in the HTML5 apps from the AGL app suite when hardware keyboard is not present? Looks like a bug I fixed last December, actually: http://cgit.freedesktop.org/wayland/weston/commit/?id=f0aaa417 Fairly small so it might be an easy forward port... Thank you for the provided feedback. I applied a patch with this bug fix to Weston 1.6 but I am still experiencing the same issue (as described in my previous email). It is a bit late here so I will continue debugging it tomorrow. After further exploration of various log files I noticed that the issues while running AGL app suite on Tizen with Crosswalk, Wayland and Weston 1.6 do not appear if an event from /dev/input is detected as a keyboard. As a work around a colleague from Konsulko Group defined a GPIO as a key at the device tree. This way the GPIO is detected by Weston as a keyboard: That's quite clever, and I'll try to remember it. :) Yes, thank you, I am lucky to work with experienced kernel developers at Konsulko Group :) Last time someone asked me for a way to create fake keyboard presence, I suggested writing a program with uinput - but if you've got control over your device tree your approach is much simpler. Yes, uinput was next on my list for a work around. [00:00:08.831] input device 'gpio-keys.22', /dev/input/event1 is a keyboard The configuration of Weston is: [input-method] path=/usr/libexec/weston-keyboard [keyboard] keymap_layout=us Derek, in this case we are using the behavior described in your article "When is a Keyboard Not a Keyboard" for the work around. Please let me know how can I help you find and fix the root cause of the problem as it seems to be a Weston issue. It's definitely a weston issue and not one of configuration, but it's hard to tell if it's already been fixed upstream. Do you have (or can you easily build) weston-editor for your platform? It's part of the weston repository... If you can reproduce the crash with that then I can reproduce it on my desktop here and fix it promptly. A backtrace of weston when it fails would also be quite helpful. Is it possible to build an image that can reproduce this problem that runs on an intel machine? I have an old laptop I could re-image (I can knock the keyboard device registration bits out of weston to mimic lack of keyboard presence easily enough...) Yes, I can build an image for Intel machines. I am not sure if the bug will appear on them. In general it should be possible to boot this Tizen image from USB stick. Btw, based on my experience Intel NUC and MinnowBoard MAX are useful for testing Tizen 3 on Intel. I will give it a try. I also have a beaglebone black and an rpi2 on hand if either of those could reproduce it, but the rpi2 tizen port has some crosswalk issues that will likely make this untestable. Yes, there are some issues with Crosswalk on Raspberry Pi 2 therefore you cannot reproduce the issue on it. The environment in my case is a bit more complicated because I am working on i.MX6 devices and I had to apply some patches on Wayland / Weston 1.6 to get it working with hardware graphics acceleration. You should be able to reproduce the bug on HummingBoard if you had one and if you disable gpio_ir_recv (cause Weston detects it as a keyboard): https://wiki.tizen.org/wiki/HummingBoard#Building_Tizen:Common_with_Yocto Best regards, Leon Best regards, Leon Thanks, Leon Hope that helps a bit, Derek In my case Weston keeps crashing when I type in HTML5 input fields from the AGL apps through the virtual weston-keyboard if no hardware keyboard is attached. I am working on a Tizen image that contains Wayland and Weston 1.6, Crosswalk 11.40.277.0 and libinput 0.6.0. Please have a look at my test cases for more details: * Test case 1, weston.ini: [input-method] path=/usr/libexec/weston-keyboard [keyboard] keymap_layout=wkb Results: 1.1. No hardware keyboard: FAIL Weston crashes when the user tries to launch Browser from the Homescreen app: [00:00:32.676] caught signal: 11 1.2. With hardware keyboard: FAIL Weston detects the hardware keyboard: [00:00:07.480] input device 'SEM USB Keyboard', /dev/input/event0 is a keyboard [00:00:07.481] input device 'SEM USB Keyboard', /dev/input/event1 is a keyboard Weston crashes when the user tries to launch Browser from the Homescreen app: [00:00:49.925] caught signal: 11 * Test case 2, weston.ini: [input-method] path= [keyboard] keymap_layo
Re: [IVI] Couldn't run the Tizen IVI application on the emulator
Hi Karray, On 19.10.2015 13:06, Karray Gargouri wrote: Hello, I am trying to test a new Tizen IVI web application, I just created a new web project, run the emulator and Run my project: Unfortunately, I got this error: Are you getting an error if you try to install the wgt file manually through the command line? This article might be useful: https://wiki.tizen.org/wiki/Installing_Web_Applications_on_Tizen:Common_and_Tizen_IVI Best regards, Leon P.S: I am using Ubuntu 14.04 as OS, and Tizen SDK - Version : 3.0 (developer version) -- /*Karray GARGOURI* -- /Ingénieur en informatique - Assistant Technologue à _ESPRIT__►_ *Membre de l'Equipe ESPRIT Mobile* ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi -- Leon Anavi Software Engineer konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] Keyboard issues with Weston and AGL application suite
Hi Derek, On 14.10.2015 20:11, Derek Foreman wrote: On 14/10/15 05:31 AM, Leon Anavi wrote: Hi Derek, All, Derek, I am experiencing similar issues with weston-keyboard as in your article "When is a Keyboard Not a Keyboard?" which has been published at Samsung OSG blog. Could you please provide me help how to get Weston 1.6 working with the virtual weston-keyboard in the HTML5 apps from the AGL app suite when hardware keyboard is not present? Looks like a bug I fixed last December, actually: http://cgit.freedesktop.org/wayland/weston/commit/?id=f0aaa417 Fairly small so it might be an easy forward port... Thank you for the provided feedback. I applied a patch with this bug fix to Weston 1.6 but I am still experiencing the same issue (as described in my previous email). It is a bit late here so I will continue debugging it tomorrow. Thanks, Leon Hope that helps a bit, Derek In my case Weston keeps crashing when I type in HTML5 input fields from the AGL apps through the virtual weston-keyboard if no hardware keyboard is attached. I am working on a Tizen image that contains Wayland and Weston 1.6, Crosswalk 11.40.277.0 and libinput 0.6.0. Please have a look at my test cases for more details: * Test case 1, weston.ini: [input-method] path=/usr/libexec/weston-keyboard [keyboard] keymap_layout=wkb Results: 1.1. No hardware keyboard: FAIL Weston crashes when the user tries to launch Browser from the Homescreen app: [00:00:32.676] caught signal: 11 1.2. With hardware keyboard: FAIL Weston detects the hardware keyboard: [00:00:07.480] input device 'SEM USB Keyboard', /dev/input/event0 is a keyboard [00:00:07.481] input device 'SEM USB Keyboard', /dev/input/event1 is a keyboard Weston crashes when the user tries to launch Browser from the Homescreen app: [00:00:49.925] caught signal: 11 * Test case 2, weston.ini: [input-method] path= [keyboard] keymap_layout=wkb Results: 2.1. No hardware keyboard: OK with remark - there is no virtual keyboard (as expected) so there is no way to type. 2.2. With hardware keyboard: FAIL Weston detects the hardware keyboard: [00:00:06.586] input device 'SEM USB Keyboard', /dev/input/event0 is a keyboard [00:00:06.587] input device 'SEM USB Keyboard', /dev/input/event1 is a keyboard Weston fails as soon as the user starts to type in HTML5 input field for URL at the Browser app through the hardware keyboard: [00:00:48.006] caught signal: 11 * Test case 3, weston.ini: [input-method] path=/usr/libexec/weston-keyboard [keyboard] keymap_layout=us Results: 3.1. No hardware keyboard: FAIL Weston crashes when the user tries to launch Browser from the Homescreen app: [00:00:28.391] caught signal: 11 3.2. With hardware keyboard: OK Weston detects the hardware keyboard and both the hardware and virtual weston-keyboard work fine: [00:00:06.767] input device 'SEM USB Keyboard', /dev/input/event0 is a keyboard [00:00:06.771] input device 'SEM USB Keyboard', /dev/input/event1 is a keyboard I want to get weston-keyboard working fine in Weston even if there is no hardware keyboard. Thanks, Leon -- Leon Anavi Software Engineer konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
[IVI] Keyboard issues with Weston and AGL application suite
Hi Derek, All, Derek, I am experiencing similar issues with weston-keyboard as in your article "When is a Keyboard Not a Keyboard?" which has been published at Samsung OSG blog. Could you please provide me help how to get Weston 1.6 working with the virtual weston-keyboard in the HTML5 apps from the AGL app suite when hardware keyboard is not present? In my case Weston keeps crashing when I type in HTML5 input fields from the AGL apps through the virtual weston-keyboard if no hardware keyboard is attached. I am working on a Tizen image that contains Wayland and Weston 1.6, Crosswalk 11.40.277.0 and libinput 0.6.0. Please have a look at my test cases for more details: * Test case 1, weston.ini: [input-method] path=/usr/libexec/weston-keyboard [keyboard] keymap_layout=wkb Results: 1.1. No hardware keyboard: FAIL Weston crashes when the user tries to launch Browser from the Homescreen app: [00:00:32.676] caught signal: 11 1.2. With hardware keyboard: FAIL Weston detects the hardware keyboard: [00:00:07.480] input device 'SEM USB Keyboard', /dev/input/event0 is a keyboard [00:00:07.481] input device 'SEM USB Keyboard', /dev/input/event1 is a keyboard Weston crashes when the user tries to launch Browser from the Homescreen app: [00:00:49.925] caught signal: 11 * Test case 2, weston.ini: [input-method] path= [keyboard] keymap_layout=wkb Results: 2.1. No hardware keyboard: OK with remark - there is no virtual keyboard (as expected) so there is no way to type. 2.2. With hardware keyboard: FAIL Weston detects the hardware keyboard: [00:00:06.586] input device 'SEM USB Keyboard', /dev/input/event0 is a keyboard [00:00:06.587] input device 'SEM USB Keyboard', /dev/input/event1 is a keyboard Weston fails as soon as the user starts to type in HTML5 input field for URL at the Browser app through the hardware keyboard: [00:00:48.006] caught signal: 11 * Test case 3, weston.ini: [input-method] path=/usr/libexec/weston-keyboard [keyboard] keymap_layout=us Results: 3.1. No hardware keyboard: FAIL Weston crashes when the user tries to launch Browser from the Homescreen app: [00:00:28.391] caught signal: 11 3.2. With hardware keyboard: OK Weston detects the hardware keyboard and both the hardware and virtual weston-keyboard work fine: [00:00:06.767] input device 'SEM USB Keyboard', /dev/input/event0 is a keyboard [00:00:06.771] input device 'SEM USB Keyboard', /dev/input/event1 is a keyboard I want to get weston-keyboard working fine in Weston even if there is no hardware keyboard. Thanks, Leon -- Leon Anavi Software Engineer konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] [Dev] Differences between open-ivi-core image and tizen-ivi-core image?
Hi Peter, On 13.10.2015 17:07, trungthu6...@gmail.com wrote: Dear Leon, I like Tizen 3 IVI x86-64 fastboot image. It has all wifi usb, 3G modem driver, CSR bluetooth 4.0... However, I cannot connect 3G/LTE and wifi using connmanctl and ofonod. Instructions how to connect to a WiFi using connmanctl are available at Tizen wiki: https://wiki.tizen.org/wiki/IVI/ConnMan_Tips_%26_Tricks#Built-in_tool:_connmanctl Connman is included in both Tizen:Common and Tizen IVI as well as in the Yocto recipes for open-ivi-core and open-ivi-hmi. I like the traditional way to build linux (make menuconfig) rather than bitbake. The recipes processed by bitbake use the traditional technologies to build the source code. The advantage of Yocto/OE is that it allows platform developers to easily customize and maintain embedded Linux distributions for various hardware devices. Furthermore bitbake builds a whole image in a few easy steps. Based on my experience Yocto/OE is the best tool for this job at the moment. Do you have full document to configure drivers, modules, kernel mod... by bitbake way? Yes, of course, please read the official documentation of the Yocto Project: http://www.yoctoproject.org/docs/1.8/mega-manual/mega-manual.html I want to build non-graphic image for IoT devices, how can I do? Use the Tizen distribution for Yocto/OE and build an image without GUI packages such as Wayland, Weston, Crosswalk. Best regards, Leon Thanks much! Peter Kieu Sent from my OS On Oct 13, 2015, at 4:27 PM, Leon Anavi <leon.an...@konsulko.com <mailto:leon.an...@konsulko.com>> wrote: Hi Ray, On 13.10.2015 12:13, RayBloodworth wrote: Hi, Leon I'm trying to build tizen-ivi image with yocto. According to "https://wiki.tizen.org/wiki/HummingBoard;, the open-ivi-core image can be built. Then I build tizen-ivi-core image according to "https://wiki.tizen.org/wiki/Building_Tizen_IVI_for_Freescale_i.MX6; and found some differences. This article is deprecated. Please stick to the instructions for building Tizen 3 using Yocto/OE for Freescale i.MX6 provided here: https://wiki.tizen.org/wiki/HummingBoard#Building_Tizen:Common_with_Yocto If you are building Tizen for a device different from HummingBoard or Cubox-i, please set the appropriate machine at conf/local.conf. You can also find useful information at my slides from Tizen Developer Conference 2015: http://www.slideshare.net/leonanavi/creating-new-tizen-profiles-using-the-yocto-project Could you give me any advices about differences between open-ivi-core image and tizen-ivi-core image? Yes, there are some differences. I created images open-ivi-core and open-ivi-hmi as part of my work at Konsulko Group. Recipe open-ivi-core extends Tizen:Common by adding some packages that we need for IVI. Recipe open-ivi-hmi extends open-ivi-core and includes HTML5 applications from the Automotive Grade Linux application suite. Best regards, Leon Thanks! BR, Ray ___ Dev mailing list d...@lists.tizen.org https://lists.tizen.org/listinfo/dev -- Leon Anavi Software Engineer konsulko.com <http://konsulko.com> ___ IVI mailing list IVI@lists.tizen.org <mailto:IVI@lists.tizen.org> https://lists.tizen.org/listinfo/ivi -- Leon Anavi Software Engineer konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] [agl-discussions] Automotive Grade Linux application suite release
Hi Steve,
Thank you for reviewing and merging my GitHub pull request to the
upstream of the Homescreen app.
Best regards,
Leon
On 30.09.2015 22:04, Mattison, Steven wrote:
Hi Leon,
My personal apologies for the inconvenience. A part of the routine
slipped past me, but this has been rectified.
Your requests on Gerrithub and Github have now been reviewed and
merged to the upstream.
Thank you very much for your contributions to the AGL application
suite so far! I look forward to your continued interest and
involvement with our projects and products.
--
*Steve Mattison*
Open Source Software Engineer
*T: *+1.503.545.7545
*Email:* smatt...@jaguarlandrover.com
<mailto:smatt...@jaguarlandrover.com>
Jaguar Land Rover North America, LLC
1419 NW 14th Ave, Portland, OR 97209
---
Business Details:
Jaguar Land Rover Limited
Registered Office: Abbey Road, Whitley, Coventry CV3 4LF
Registered in England No: 1672070
This e-mail and any attachments contain confidential information for a
specific individual and purpose. The information is private and
privileged and intended solely for the use of the individual to whom
it is addressed. If you are not the intended recipient, please e-mail
us immediately. We apologise for any inconvenience caused but you are
hereby notified that any disclosure, copying or distribution or the
taking of any action in reliance on the information contained herein
is strictly prohibited.
This e-mail does not constitute an order for goods or services unless
accompanied by an official purchase order.
On 30 September 2015 at 01:36, Leon Anavi <leon.an...@konsulko.com
<mailto:leon.an...@konsulko.com>> wrote:
Hi Steve,
I received an email from gerrithub.io <http://gerrithub.io>. I saw
that you have voted +2 for the changes from my GitHub pull request
but it seems that the request is still not merged in the upstream.
In the mean time I pushed another commit about the systemd service
and the launcher script of the DNA Homescreen app. This commit has
been also included in the GitHub pull request:
https://github.com/PDXostc/homescreen/pull/2/commits
Could you please have a look?
Thanks,
Leon
--
Leon Anavi
Software Engineer
konsulko.com <http://konsulko.com>
--
Leon Anavi
Software Engineer
konsulko.com
___
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi
Re: [IVI] [agl-discussions] Automotive Grade Linux application suite release
Hi, I noticed that my GitHub pull request with couple of fixes for the Homescreen app is open and has been waiting for a review since 17 June (aka for 3 months): https://github.com/PDXostc/homescreen/pull/2 Could you please review it? Best regards, Leon On 20.04.2015 18:52, Graham, Forrest wrote: All, Announcing a new release of the AGL application suite and components. Browser 0.0.1 Dashboard 1.0.0 FMRadio 0.0.1 GoogleMaps 0.0.1 HVAC 1.0.0 MediaManager 1.0.1 News 0.0.1 Near Field Communication (NFC) 0.0.1 Phone 0.0.1 Remote Vehicle Interaction (RVI) 0.3.2 Weather 0.0.1 Additional information on these is available on the AGL Wiki <https://wiki.automotivelinux.org/project-agl-demonstrator-crosswalk> page. We have made available the source code for the latest version of our suite of crosswalk applications. See it here with readme: On GitHub via this link to all the repos, AGL_App_Suite <https://github.com/PDXostc> This release is based on the tizen-3.0-ivi_20150201.3/ release. You can build from source with gbs (gbs build -A i586), pointing your .gbs.conf at the tizen.org <http://tizen.org/> repo for Tizen. url = http://download.tizen.org/releases/milestone/tizen/ivi-3.0/tizen-3.0-ivi_20150201.3/repos/atom Kind Regards, *Forrest T. Graham* --- /Project Manager - Infotainment/ *Jaguar Land Rover* Email: fgra...@jaguarlandrover.com <mailto:fgra...@jaguarlandrover.com> Cell: +1 360.975.9321 US: 1419 NW 14th Ave, Portland, Oregon, 97209 --- Business Details: Jaguar Land Rover Limited Registered Office: Abbey Road, Whitley, Coventry CV3 4LF Registered in England No: 1672070 --- This e-mail and any attachments contain confidential information for a specific individual and purpose. The information is private and privileged and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, please e-mail us immediately. We apologize for any inconvenience caused but you are hereby notified that any disclosure, copying or distribution or the taking of any action in reliance on the information contained herein is strictly prohibited. This e-mail does not constitute an order for goods or services unless accompanied by an official purchase order. ___ automotive-discussions mailing list automotive-discussi...@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions -- Leon Anavi Software Engineer konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] about cgroup
Hi Neo, On 6.08.2015 12:38, Neo hong wrote: Hi Guys, I have found that control group is a usefull tool for mangers system resource. But I didn't find libcgroup or related rpm on Tizen source. Can you tell me how to use cgroup to limit system memory resource on my own develop board ? Control Groups are feature of the Linux kernel that have to be enabled for Tizen:Common, Tizen IVI and the other Tizen 3 profiles because of systemd. Some details can be found at the porting guidelines in Tizen wiki: https://wiki.tizen.org/wiki/Porting_Guide/System As far as I know the usage of cgroups and systemd in Tizen 3 profiles is standard, just like in other popular GNU/Linux distributions. Best regards, Leon Thanks a lot . ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi -- Leon Anavi Software Engineer konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] [Crosswalk-dev] Tizen - App_launcher and xwalk Landscape issue
Hi Art, If you remember several weeks ago I had some issues with installing and running HTML5 apps on Tizen:Common which were solved after updating Crosswalk to version 11.40.277.0. Which version of Crosswalk are you using? Is the screen orientation set to landscape at the config.xml of the HTML5 applications? Best regards, Leon On 17.06.2015 01:55, McGee, Art wrote: I have run into a problem that Tizen web apps will not run when the box has been setup in landscape mode. I have been able to launch the same apps in portrate mode. I have been spending quite a bit of time searching. I would input on the app_launch process when it comes to xwalk wigits. I have been able to see that a xwalk 'renderer' process doesn't get started and the app will shutdown after never getting a display. and it timesout on the debus call. Any information on how the launch process works will help me discover where the bug is accually. *Art McGee* Infotainment Engineer Jaguar Land Rover North America, LLC 1419 NW 14th Ave, Portland, Oregon, 97209 Jaguar.com http://jaguar.com | LandRover.com http://landrover.com ___ Crosswalk-dev mailing list crosswalk-...@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] Automotive Grade Linux application suite release 30 Mar 2015
Hi, On 9.06.2015 20:22, Graham, Forrest wrote: Leon, Thanks for asking. See the document attached. I have put in a request with owner of PDXostc to make this available on Github, but until that time here is the information you requested. Thank you for the provided details. I see that you use the standard GitHub workflow with fork pull requests. According to the document signoff must be added to git commits. Fortunately, I have already done it so I am keeping my fingers crossed that my pull request for yesterday will be accepted :) Thanks, Leon P.S. I added Tizen dev ivi mailing lists as CC because this information might be useful to other contributors. Regards, *Forrest T. Graham* - /Project Manager - Infotainment/ *Jaguar Land Rover* *T: *+01 971-256-9707 | *M:* +01 360.975.9321 *E:* fgra...@jaguarlandrover.com mailto:fgra...@jaguarlandrover.com US: 1419 NW 14th Ave, Portland, Oregon, 97209 jaguar.com http://jaguar.com | landrover.com http://landrover.com --- Business Details: Jaguar Land Rover Limited Registered Office: Abbey Road, Whitley, Coventry CV3 4LF Registered in England No: 1672070 --- This e-mail and any attachments contain confidential information for a specific individual and purpose. The information is private and privileged and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, please e-mail us immediately. We apologize for any inconvenience caused but you are hereby notified that any disclosure, copying or distribution or the taking of any action in reliance on the information contained herein is strictly prohibited. This e-mail does not constitute an order for goods or services unless accompanied by an official purchase order. On Tue, Jun 9, 2015 at 6:09 AM, Leon Anavi leon.an...@konsulko.com mailto:leon.an...@konsulko.com wrote: Hi, What is the procedure for contributing back changes to any of these applications? Is it using pull requests in GitHub? I made a minor change to the master branch of Google Maps and I opened a pull request: https://github.com/PDXostc/google_maps/pull/2 Best regards, Leon On 30.03.2015 23:47, Graham, Forrest wrote: All, The following applications are now available via GitHub. Each application on the AGL wiki page has the source pointing to each GitHub repository. *List the apps being released:* Common 0.0.1 Weather 0.0.1 Browser 0.0.1 News 0.0.1 HomeScreen 0.0.1 Commons 0.0.1 Settings Near Field Connection (NFC) 0.0.1 HVAC 1.0.0 Dashboard 1.0.0 Google Maps 0.0.1 FM Radio (new from prior release) 0.0.1 Additional information on these is available on the AGL Wiki https://wiki.automotivelinux.org/project-agl-demonstrator-crosswalk page. We have made available the source code for the latest version of our suite of crosswalk applications. See it here with readme: On GitHub via this link to all the repos, AGL_App_Suite https://github.com/PDXostc This release is based on the tizen-3.0-ivi_20150201.3/ release. You can build from source with gbs (gbs build -A i586), pointing your .gbs.conf at the tizen.org http://tizen.org/ repo for Tizen. url = http://download.tizen.org/releases/milestone/tizen/ivi-3.0/tizen-3.0-ivi_20150201.3/repos/atom Kind Regards *Forrest T. Graham* --- /Project Manager - Infotainment/ *Jaguar Land Rover* Email: fgra...@jaguarlandrover.com mailto:fgra...@jaguarlandrover.com Cell: +1 360.975.9321 US: 1419 NW 14th Ave, Portland, Oregon, 97209 --- Business Details: Jaguar Land Rover Limited Registered Office: Abbey Road, Whitley, Coventry CV3 4LF Registered in England No: 1672070 --- This e-mail and any attachments contain confidential information for a specific individual and purpose. The information is private and privileged and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, please e-mail us immediately. We apologize for any inconvenience caused but you are hereby notified that any disclosure, copying or distribution or the taking of any action in reliance on the information contained herein is strictly prohibited. This e-mail does not constitute an order for goods or services unless accompanied by an official purchase order. ___ IVI mailing list IVI@lists.tizen.org mailto:IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com http://konsulko.com -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com
Re: [IVI] Automotive Grade Linux application suite release 30 Mar 2015
Hi, What is the procedure for contributing back changes to any of these applications? Is it using pull requests in GitHub? I made a minor change to the master branch of Google Maps and I opened a pull request: https://github.com/PDXostc/google_maps/pull/2 Best regards, Leon On 30.03.2015 23:47, Graham, Forrest wrote: All, The following applications are now available via GitHub. Each application on the AGL wiki page has the source pointing to each GitHub repository. *List the apps being released:* Common 0.0.1 Weather 0.0.1 Browser 0.0.1 News 0.0.1 HomeScreen 0.0.1 Commons 0.0.1 Settings Near Field Connection (NFC) 0.0.1 HVAC 1.0.0 Dashboard 1.0.0 Google Maps 0.0.1 FM Radio (new from prior release) 0.0.1 Additional information on these is available on the AGL Wiki https://wiki.automotivelinux.org/project-agl-demonstrator-crosswalk page. We have made available the source code for the latest version of our suite of crosswalk applications. See it here with readme: On GitHub via this link to all the repos, AGL_App_Suite https://github.com/PDXostc This release is based on the tizen-3.0-ivi_20150201.3/ release. You can build from source with gbs (gbs build -A i586), pointing your .gbs.conf at the tizen.org http://tizen.org/ repo for Tizen. url = http://download.tizen.org/releases/milestone/tizen/ivi-3.0/tizen-3.0-ivi_20150201.3/repos/atom Kind Regards *Forrest T. Graham* --- /Project Manager - Infotainment/ *Jaguar Land Rover* Email: fgra...@jaguarlandrover.com mailto:fgra...@jaguarlandrover.com Cell: +1 360.975.9321 US: 1419 NW 14th Ave, Portland, Oregon, 97209 --- Business Details: Jaguar Land Rover Limited Registered Office: Abbey Road, Whitley, Coventry CV3 4LF Registered in England No: 1672070 --- This e-mail and any attachments contain confidential information for a specific individual and purpose. The information is private and privileged and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, please e-mail us immediately. We apologize for any inconvenience caused but you are hereby notified that any disclosure, copying or distribution or the taking of any action in reliance on the information contained herein is strictly prohibited. This e-mail does not constitute an order for goods or services unless accompanied by an official purchase order. ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] [Dev] Common QA for Tizen on Yocto
Hi again, I added an article to Tizen wiki which explains how to set a package stream for Tizen on Yocto and how to manage packages at runtime with the smart package manager: https://wiki.tizen.org/wiki/Runtime_package_management_in_Tizen_on_Yocto_with_Smart I hope that the article will be useful for application development on both Tizen:Common and Tizen IVI built with Yocto. Best regards, Leon On 8.06.2015 14:29, Leon Anavi wrote: Hi Dominig, Carsten, All, On 8.06.2015 11:07, Dominig ar Foll (Intel OTC) wrote: Le 05/06/2015 10:02, Carsten Haitzler a écrit : my question is more one of maybe it should be there by default as a core part of tizen? as it has key value to tizen as an OS. it makes tizen useful. it differentiates tizen. it makes an installed tizen device EASY to extend as a developer of that device or as someone interested in augmmenting it. To be honest, its a nice to have for developper but for a product it provides no value at all. Making zypper mandatory for a product point of view is not a great idea. So likely it should stay out of the compliance requirement. Actually, the smart package manager, which already present in Tizen on Yocto, can replace entirely zypper. Tizen on Yocto package's output directory on the host system can be converted into a package feed with the assistance of a web server, for example apache or something lighter. After that smart channels have to be set on the Tizen device. Finally, new package can be installed with a simple command, for example: smart install -y zip I have just done it and it works :) Best regards, Leon -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] When I launch the application html page not displayed
Hi Claud, On the provided screenshot I see that there is no connection to the page for remote debugging. This means that the web app on the vm is not really running. Have you tried to launch any other web apps? Btw recently I created a wgt package for basic testing of Crosswalk on Tizen:Common from the following source code: https://github.com/leon-anavi/helloTizen I was able to install successfully this wgt and to run it without any issues on Crosswalk 11.40.277.0. May be you can give it a try on the IVI image for your VM too. Best regards, Leon On 1.06.2015 11:36, FAATH Claude wrote: Hello, Thank you for taking your time to answer me. New image Tizen IVI in the hope ... : tizen-ivi_20150529.2_ivi-mbr-i586-sdb crosswalk-11.40.277.0-26.2.i686 | chromium-34.0.1829.0-0.i686.rpm DEVICE : vmware-player 7.1.0.2496824 | VMware Tools for Linux 9.9.2.2496824 Virtual Machine Settings | Display | Accelerate 3D graphics OK Application : xwalk-simple.xpk ( The hello world Crosswalk ) app@ivi_box:~$ app_launcher -s xwalk.flakgaanpffafekcjomadghnepnpljhj -d ... successfully launched whit debug 1 // No display LOG : identical Remote Debugging Thank you for reading me, Claude. Le 31/05/2015 11:53, Leon Anavi a écrit : Hi Claude, On what device are you trying to run the application and is hardware acceleration enabled for Wayland? I noticed that you are launching the application in debug mode. Have you tried to locate any JavaScript errors with remote debugging? Best regards, Leon On Sat, May 30, 2015 at 8:03 AM, FAATH Claude claude.fa...@gmail.com mailto:claude.fa...@gmail.com wrote: Hello, New to Tizen IVI | Crosswalk I followed the tutorial : https://crosswalk-project.org/documentation/getting_started/run_on_tizen.html. When I launch the application html page not displayed. An idea of the problem, BUG, solution ? Please note that the chromium-browser 34.0.1829.0-0.i686 work properly. ... tizen-ivi_20150204.1_ivi-mbr-i586-sdb + crosswalk-11.40.277.0-26.2.i686 app@ivi_box:~$ pkgcmd -i -t xpk -p /home/app/xwalk-simple.xpk -q path is /home/app/xwalk-simple.xpk __return_cb req_id[1] pkg_type[wgt] pkgid[flakgaanpffafekcjomadghnepnpljhj] key[start] val[install] __return_cb req_id[1] pkg_type[wgt] pkgid[flakgaanpffafekcjomadghnepnpljhj] key[end] val[ok] spend time for pkgcmd is [2198]ms app@ivi_box:~$ ail_list Application List for user 5000 User's Application APPIDNAME EXEPATH ... 'xwalk.flakgaanpffafekcjomadghnepnpljhj' 'simple' '//home/app/apps_rw/xwalk-service// applications/xwalk.flakgaanpffafekcjomadghnepnpljhj/bin/ xwalk.flakgaanpffafekcjomadghnepnpljhj' ... app@ivi_box:~$ app_launcher -s xwalk.flakgaanpffafekcjomadghnepnpljhj ... successfully launched whit debug 0 // No display app@ivi_box:~$ app_launcher -s xwalk.flakgaanpffafekcjomadghnepnpljhj -d ... successfully launched whit debug 1 // No display app@ivi_box:~$ xwalkctl Application ID Application Name - xwalk.flakgaanpffafekcjomadghnepnpljhj simple - app@ivi_box:~$ xwalk-launcher xwalk.flakgaanpffafekcjomadghnepnpljhj call 'EnableRemoteDebugging' method: sucess Application launched with path '/running1/xwalk_flakgaanpffafekcjomadghnepnpljhj' event 'AE_RESET' Application '/running1/xwalk_flakgaanpffafekcjomadghnepnpljhj' disappeared, exiting. properties changed org.crosswalkproject.Running.Application1 // No display ... LOG : bash-4.3# journalctl -b ... May 25 09:53:51 ivi_box xwalk[333]: [0525/095351:ERROR:gpu_watchdog_thread.cc(253)] The GPU process hung. Terminating after 10 May 25 09:53:51 ivi_box kernel: Watchdog[365]: segfault at 0 ip 0aff89d7 sp b603bbd0 error 6 in xwalk[804+3ffa000] May 25 09:53:52 ivi_box xwalk[333]: [0525/095352:ERROR:gpu_channel_host.cc(136)] GpuChannelHost::CreateViewCommandBuffer faile May 25 09:53:52 ivi_box xwalk[333]: [0525/095352:ERROR:webgraphicscontext3d_command_buffer_impl.cc(230)] Failed to initialize May 25 09:53:52 ivi_box xwalk[333]: [0525/095352:INFO:desktop_factory_wayland.cc(17)] Ozone: DesktopFactoryWayland May 25 09:53:52 ivi_box kernel: xwalk[391]: segfault at 0 ip 0a80a1eb sp bfcc55d0 error 4 in xwalk[804+3ffa000] May 25 09:53:52 ivi_box xwalk[333]: [0525/095352:ERROR:webgraphicscontext3d_command_buffer_impl.cc(274)] Failed to initialize May 25 09:53:52 ivi_box xwalk[333]: [0525/095352:ERROR:command_buffer_proxy_impl.cc(150)] Could not send GpuCommandBufferMsg_I May 25 09:53:52 ivi_box xwalk[333]: [0525/095352:ERROR:webgraphicscontext3d_command_buffer_impl.cc(213)] CommandBufferProxy::I May 25 09:53
Re: [IVI] When I launch the application html page not displayed
org.crosswalkproject.Running.Application1 May 25 09:53:57 ivi_box systemd[159]: xwalk.service: main process exited, code=dumped, status=6/ABRT May 25 09:53:57 ivi_box systemd[159]: Unit xwalk.service entered failed state. May 25 09:54:09 ivi_box systemd-coredump[397]: Process 391 (xwalk) of user 5000 dumped core. May 25 09:54:10 ivi_box systemd-coredump[404]: Process 398 (xwalk) of user 5000 dumped core. May 25 09:54:12 ivi_box systemd-coredump[390]: Process 359 (xwalk) of user 5000 dumped core. May 25 09:54:19 ivi_box systemd-coredump[405]: Process 333 (xwalk) of user 5000 dumped core. Thank you for reading me, Claude. ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] request of information on tizen ivi with yocto.
Hi Novello, According to my experience the upstream Tizen on Yocto is not in good shape and you will encounter numerous issue if you want to build an image for ARM. As I mentioned in my previous email for Freescale i.MX6 you should start from the article about HummingBoard. It contains instructions how to build Tizen:Common using Yocto from a fork of Tizen on Yocto which has bee adapted for i.MX6: https://wiki.tizen.org/wiki/HummingBoard#Building_Tizen:Common_with_Yocto Check the changes in the Git log of the fork and if you want you can apply similar changes to the IVI profile and try to get it working too. Best regards, Leon On Sat, May 30, 2015 at 9:42 PM, Novello Giampiero novellog...@gmail.com wrote: ello@qc:/media/novello/hd5/ae/tizen/tizen-distro2/tizen-distro$ source ./tizen-ivi-init-build-env buildivi/ ### Shell environment set up for builds. ### You can now run 'bitbake target' Tizen images: tizen-ivi-core-image tizen-ivi-core-image-dev tizen-ivi-ico-image tizen-ivi-ico-image-dev tizen-ivi-Modello-image tizen-ivi-Modello-image-dev You can also run generated qemu images with a command like 'runqemu qemux86' novello@qc:/media/novello/hd5/ae/tizen/tizen-distro2/tizen-distro/buildivi$ bitbake tizen-ivi-Modello-image Loading cache: 100% |###| ETA: 00:00:00 Loaded 2568 entries from dependency cache. NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'qt5-plugin-bearer-nm' (but /media/novello/hd5/ae/tizen/tizen-distro2/tizen-distro/meta-tizen/meta-tizen-ivi/recipes-extended/automotive-message-broker/ automotive-message-broker_git.bb DEPENDS on or otherwise requires it) NOTE: Runtime target 'automotive-message-broker' is unbuildable, removing... Missing or unbuildable dependency chain was: ['automotive-message-broker', 'qt5-plugin-bearer-nm'] ERROR: Required build target 'tizen-ivi-Modello-image' has no buildable providers. Missing or unbuildable dependency chain was: ['tizen-ivi-Modello-image', 'automotive-message-broker', 'qt5-plugin-bearer-nm'] Summary: There were 2 ERROR messages shown, returning a non-zero exit code. I see that with tizen-common for imx6 work... Sorry I have find this mistake may some one help me. Best regards Novello G. ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] [Dev] with the ivi tizen-distro
Hi, On 26.05.2015 23:29, novello wrote: I have try a tizen build for ivi ... not common and if geve an error soon I'm trying to use an imx board 3.14 kernel .. My experience shows that at the moment Tizen on Yocto does not work out of the box for ARM machines. Numerous changes have to be applied to make it work and to build an image for device with ARM SoC. I have shared some patches for Freescale i.MX6 at the GitHub repo of Konsulko Group and I have described the step by step procedure for building Tizen:Common using Yocto for HummingBoard-i2eX at the Tizen wiki: https://wiki.tizen.org/wiki/HummingBoard#Building_Tizen:Common_with_Yocto Best regards, Leon P.S. Please note that I have added Tizen IVI mailing list in CC because your question is related to the IVI profile. Best Regards ___ Dev mailing list d...@lists.tizen.org https://lists.tizen.org/listinfo/dev -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] [Dev] Yocto Tizen - patch for gstreamer
Hi Sami, Kevin, I saw that several months ago you were discussing an issue related to gst-ffmpeg while building Tizen image using Yocto for MinnowBoard. According to your comments gst-ffmpeg is not part of Tizen images but no solution has been posted. Recently I experienced the same issue with gst-ffmpeg recipes while I building Tizen:Common and IVI images for machine: intel-corei7-64 and would like to share my solution. I found out that gst-ffmpeg is involved by recipes for Intel specific hardware codecs. The following line has to be added to conf/local.conf to remove the hardware codecs and not to encounter the errors related to gst-ffmpeg: MACHINE_HWCODECS_remove = va-intel gst-va-intel gst-va-intel-general gst-va-intel-video gst-va-intel-vaapi I have described this approach at Tizen wiki article for MinnowBoard MAX as well as at the corresponding bug report in JIRA: https://wiki.tizen.org/wiki/MinnowMax#Building_Tizen_with_Yocto https://bugs.tizen.org/jira/browse/BTY-105 Best regards, Leon -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] [Dev] Yocto Tizen - patch for gstreamer
Hi Baptiste, On 19.05.2015 16:16, Baptiste Durand wrote: Hi Leon, The issue is due to wrong MACHINE_HWCODEC set. Indeed Tizen use Gstreamer 1.0 not gstreamer 0.10 So please cherry pick this commit from master branch of intel and apply it to dizzy. Thank you for the valuable feedback. Dizzy is the code name of Yocto project 1.7 which was released in October 2014. The latest version Fido, Yocto project 1.8, was released in April. Applying any changes to Intel meta layer for Dizzy may have a negative impact on people who already use it with the same release of Poky. In my opinion the issue that we are facing with MinnowBoard MAX is specific for “Tizen on Yocto” and I suggest to apply a change of the codecs through conf/local.conf and to describe it at our Wiki article. I am doing a clear build of Tizen:Common from scratch with Yocto for intel-corei7-64 and I will report the results when it is ready. Best regards, Leon dcb2710376c832d3a450748f997b6fc5c13a82f7 commit dcb2710376c832d3a450748f997b6fc5c13a82f7 Author: Ross Burton ross.bur...@intel.com mailto:ross.bur...@intel.com Date: Fri Feb 27 18:00:36 2015 + intel-core*: use gstreamer-vaapi-1.0 directly instead of gst-va-intel No need for a layer of indirection when that layer only has one option. Previously with EMGD there was a choice, but not anymore. Signed-off-by: Ross Burton ross.bur...@intel.com mailto:ross.bur...@intel.com Signed-off-by: Darren Hart dvh...@linux.intel.com mailto:dvh...@linux.intel.com diff --git a/conf/machine/intel-core2-32.conf b/conf/machine/intel-core2-32.conf index 699d757..2b79165 100644 --- a/conf/machine/intel-core2-32.conf +++ b/conf/machine/intel-core2-32.conf @@ -15,7 +15,7 @@ MACHINE_FEATURES += va-impl-intel MACHINE_FEATURES += wifi 3g MACHINE_FEATURES += intel-ucode -MACHINE_HWCODECS ?= va-intel gst-va-intel +MACHINE_HWCODECS ?= va-intel gstreamer-vaapi-1.0 MACHINE_EXTRA_RRECOMMENDS += linux-firmware diff --git a/conf/machine/intel-corei7-64.conf b/conf/machine/intel-corei7-64.conf index d3da826..491ef04 100644 --- a/conf/machine/intel-corei7-64.conf +++ b/conf/machine/intel-corei7-64.conf @@ -15,7 +15,7 @@ MACHINE_FEATURES += va-impl-intel MACHINE_FEATURES += wifi 3g MACHINE_FEATURES += intel-ucode -MACHINE_HWCODECS ?= va-intel gst-va-intel +MACHINE_HWCODECS ?= va-intel gstreamer-vaapi-1.0 MACHINE_EXTRA_RRECOMMENDS += linux-firmware lms8 BR Baptiste 2015-05-19 10:07 GMT+02:00 Leon Anavi leon.an...@konsulko.com mailto:leon.an...@konsulko.com: Hi Sami, Kevin, I saw that several months ago you were discussing an issue related to gst-ffmpeg while building Tizen image using Yocto for MinnowBoard. According to your comments gst-ffmpeg is not part of Tizen images but no solution has been posted. Recently I experienced the same issue with gst-ffmpeg recipes while I building Tizen:Common and IVI images for machine: intel-corei7-64 and would like to share my solution. I found out that gst-ffmpeg is involved by recipes for Intel specific hardware codecs. The following line has to be added to conf/local.conf to remove the hardware codecs and not to encounter the errors related to gst-ffmpeg: MACHINE_HWCODECS_remove = va-intel gst-va-intel gst-va-intel-general gst-va-intel-video gst-va-intel-vaapi I have described this approach at Tizen wiki article for MinnowBoard MAX as well as at the corresponding bug report in JIRA: https://wiki.tizen.org/wiki/MinnowMax#Building_Tizen_with_Yocto https://bugs.tizen.org/jira/browse/BTY-105 Best regards, Leon -- Leon Anavi Software Engineer Mob :+359 88 527 7901 tel:%2B359%2088%20527%207901 konsulko.com http://konsulko.com ___ Dev mailing list d...@lists.tizen.org mailto:d...@lists.tizen.org https://lists.tizen.org/listinfo/dev -- Baptiste DURAND Eurogiciel Vannes/FR -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] [Dev] Yocto Tizen - patch for gstreamer
Hi Baptiste, On 19.05.2015 18:19, Baptiste Durand wrote: Hi Leon, Take care that Tizen-distro was initalized with the content of *dizzy* release of yocto. Moving to fido can lead to make unconsistant image Making this cherry pick solve your issue... I have been faced to this issue yesteday. I prefer to overwrite the value of MACHINE_HWCODECS at local.conf. I added it the following line to conf/local.conf: MACHINE_HWCODECS = va-intel gstreamer-vaapi-1.0 As you suggested, with this change related to the hardware codecs I am able to build tizen-core-image-minimal (from branch origin/tizen) successfully but I am getting a kernel panic when I try to boot it on MinnowBoard MAX. I am following the steps at the Wiki: https://wiki.tizen.org/wiki/MinnowMax#Building_Tizen_with_Yocto Are you able to boot MinnowBoard MAX with tizen-core-image-minimal image for machine intel-corei7-64 successfully? Thanks, Leon BR Baptiste 2015-05-19 16:21 GMT+02:00 Leon Anavi leon.an...@konsulko.com mailto:leon.an...@konsulko.com: Hi Baptiste, On 19.05.2015 16:16, Baptiste Durand wrote: Hi Leon, The issue is due to wrong MACHINE_HWCODEC set. Indeed Tizen use Gstreamer 1.0 not gstreamer 0.10 So please cherry pick this commit from master branch of intel and apply it to dizzy. Thank you for the valuable feedback. Dizzy is the code name of Yocto project 1.7 which was released in October 2014. The latest version Fido, Yocto project 1.8, was released in April. Applying any changes to Intel meta layer for Dizzy may have a negative impact on people who already use it with the same release of Poky. In my opinion the issue that we are facing with MinnowBoard MAX is specific for “Tizen on Yocto” and I suggest to apply a change of the codecs through conf/local.conf and to describe it at our Wiki article. I am doing a clear build of Tizen:Common from scratch with Yocto for intel-corei7-64 and I will report the results when it is ready. Best regards, Leon dcb2710376c832d3a450748f997b6fc5c13a82f7 commit dcb2710376c832d3a450748f997b6fc5c13a82f7 Author: Ross Burton ross.bur...@intel.com mailto:ross.bur...@intel.com Date: Fri Feb 27 18:00:36 2015 + intel-core*: use gstreamer-vaapi-1.0 directly instead of gst-va-intel No need for a layer of indirection when that layer only has one option. Previously with EMGD there was a choice, but not anymore. Signed-off-by: Ross Burton ross.bur...@intel.com mailto:ross.bur...@intel.com Signed-off-by: Darren Hart dvh...@linux.intel.com mailto:dvh...@linux.intel.com diff --git a/conf/machine/intel-core2-32.conf b/conf/machine/intel-core2-32.conf index 699d757..2b79165 100644 --- a/conf/machine/intel-core2-32.conf +++ b/conf/machine/intel-core2-32.conf @@ -15,7 +15,7 @@ MACHINE_FEATURES += va-impl-intel MACHINE_FEATURES += wifi 3g MACHINE_FEATURES += intel-ucode -MACHINE_HWCODECS ?= va-intel gst-va-intel +MACHINE_HWCODECS ?= va-intel gstreamer-vaapi-1.0 MACHINE_EXTRA_RRECOMMENDS += linux-firmware diff --git a/conf/machine/intel-corei7-64.conf b/conf/machine/intel-corei7-64.conf index d3da826..491ef04 100644 --- a/conf/machine/intel-corei7-64.conf +++ b/conf/machine/intel-corei7-64.conf @@ -15,7 +15,7 @@ MACHINE_FEATURES += va-impl-intel MACHINE_FEATURES += wifi 3g MACHINE_FEATURES += intel-ucode -MACHINE_HWCODECS ?= va-intel gst-va-intel +MACHINE_HWCODECS ?= va-intel gstreamer-vaapi-1.0 MACHINE_EXTRA_RRECOMMENDS += linux-firmware lms8 BR Baptiste 2015-05-19 10:07 GMT+02:00 Leon Anavi leon.an...@konsulko.com mailto:leon.an...@konsulko.com: Hi Sami, Kevin, I saw that several months ago you were discussing an issue related to gst-ffmpeg while building Tizen image using Yocto for MinnowBoard. According to your comments gst-ffmpeg is not part of Tizen images but no solution has been posted. Recently I experienced the same issue with gst-ffmpeg recipes while I building Tizen:Common and IVI images for machine: intel-corei7-64 and would like to share my solution. I found out that gst-ffmpeg is involved by recipes for Intel specific hardware codecs. The following line has to be added to conf/local.conf to remove the hardware codecs and not to encounter the errors related to gst-ffmpeg: MACHINE_HWCODECS_remove = va-intel gst-va-intel gst-va-intel-general gst-va-intel-video gst-va-intel-vaapi I have described this approach at Tizen wiki article for MinnowBoard MAX as well as at the corresponding bug report in JIRA: https://wiki.tizen.org/wiki/MinnowMax#Building_Tizen_with_Yocto https://bugs.tizen.org/jira/browse/BTY-105 Best regards
[IVI] Update of the Tutorial for Building Tizen with Yocto for MinnowBoard MAX
Hi, I noticed that tutorial about building Tizen:Common or IVI using Yocto for MinnowBoard MAX fails due to the recent updates of meta-intel layer with the following error: ERROR: No recipes available for: /home/leon/tizen-ivi-intel/meta-intel/common/recipes-kernel/lttng/lttng-modules_2.6.%.bbappend /home/leon/tizen-ivi-intel/meta-intel/common/recipes-kernel/linux/linux-yocto_3.19.bbappend According to my experience, to avoid this error branch dizzy of meta-intel layer has to be used with the existing recipes in Tizen on Yocto. I have updated the wiki article and now I am doing a build from scratch to verify that the procedures is working fine again. For more details please have a look at my changes at: https://wiki.tizen.org/wiki/MinnowMax#Building_Tizen_with_Yocto Best regards, Leon -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] tizen ivi for the Renesas R-Car M2 ARM platform using yocto?
Hi Vitaly, Patrick, On 12.05.2015 10:42, Vitaly Chernooky wrote: Hi Patrick, On Mon, May 11, 2015 at 4:49 PM, Patrick Ohly patrick.o...@intel.com mailto:patrick.o...@intel.com wrote: On Mon, 2015-05-11 at 15:55 +0300, Vitaly Chernooky wrote: Hi Leon, On Fri, May 8, 2015 at 4:32 PM, Leon Anavi leon.an...@konsulko.com mailto:leon.an...@konsulko.com wrote: Hi Pedro, On 8.05.2015 14:59, pedro.quei...@elektrobit.com mailto:pedro.quei...@elektrobit.com wrote: Hi all, I have started an attempt to build tizen ivi for the Renesas R-Car M2 ARM platform (Koelsch board), one of the goals would be to attempt graphics hw acceleration with the proprietary drivers. There are some instructions available in the wiki regarding using gbs. Nevertheless I wonder whether someone did or is in the process going the same using yocto? Building Tizen:Common or any of the Tizen profiles based on it (like IVI) for ARM using Yocto isn't easy task. In my opinion the Yocto recipes are not perfect and you will have numerous challenges if you try to build them for any devices with CPU different from Intel. I have different opinion on it. According to my experience with Yocto, it is much more easier to build for ARM with Yocto than with gbs ;) The comment was about the Tizen on Yocto recipes, not Yocto. The recipes have issues that you don't see when building recipes manually written for Yocto. These recipes get converted from .spec files to .bb files based on the build configuration for x86. All architecture specific tweaks in Tizen get lost at that point and have to be added back manually to the generated .bb files. The spec2yocto conversion tool also does not have enough information available in the .spec files about dependencies (is a tool needed or something to link against?) and has to use heuristics, which fail in some cases when doing cross-compilation. It looks like you have skipped my announce of successful building of Tizen IVI on Yocto for ARM-based board DRA7XX. And as far as I recall Leon have used few my recipes changes in his buildings. It was the reason why I expected than Leon would understand me :) Vitaly, yes I used parts of your recipes. Actually similar fixes exist for the recipes in the fork of Tizen:Common for Raspberry Pi 2 which is maintained by Samsung Open Source Group. In my opinion the main problem at the moment is that building Tizen:Common or Tizen IVI using Yocto for ARM does not work out of the box. As far as I remember your changes related to DRA7XX were pushed into a sandbox. Do you plan to merge them with tizen-distro upstream and to support both ARM Intel machines with the same recipes? Thanks, Leon With best regards, -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. -- *Vitaly Chernooky | Senior Developer - Product Engineering and Development* GlobalLogic P _+380.44.4929695 ext.1136_ M _+380.63.6011802_ S cvv_2k www.globallogic.com http://www.globallogic.com http://www.globallogic.com/email_disclaimer.txt -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] tizen ivi for the Renesas R-Car M2 ARM platform using yocto?
Hi Vitaly, On 12.05.2015 11:26, Vitaly Chernooky wrote: Hi Leon, On Tue, May 12, 2015 at 11:02 AM, Leon Anavi leon.an...@konsulko.com mailto:leon.an...@konsulko.com wrote: Hi Vitaly, Patrick, On 12.05.2015 10:42, Vitaly Chernooky wrote: Hi Patrick, On Mon, May 11, 2015 at 4:49 PM, Patrick Ohly patrick.o...@intel.com mailto:patrick.o...@intel.com wrote: On Mon, 2015-05-11 at 15:55 +0300, Vitaly Chernooky wrote: Hi Leon, On Fri, May 8, 2015 at 4:32 PM, Leon Anavi leon.an...@konsulko.com mailto:leon.an...@konsulko.com wrote: Hi Pedro, On 8.05.2015 14:59, pedro.quei...@elektrobit.com mailto:pedro.quei...@elektrobit.com wrote: Hi all, I have started an attempt to build tizen ivi for the Renesas R-Car M2 ARM platform (Koelsch board), one of the goals would be to attempt graphics hw acceleration with the proprietary drivers. There are some instructions available in the wiki regarding using gbs. Nevertheless I wonder whether someone did or is in the process going the same using yocto? Building Tizen:Common or any of the Tizen profiles based on it (like IVI) for ARM using Yocto isn't easy task. In my opinion the Yocto recipes are not perfect and you will have numerous challenges if you try to build them for any devices with CPU different from Intel. I have different opinion on it. According to my experience with Yocto, it is much more easier to build for ARM with Yocto than with gbs ;) The comment was about the Tizen on Yocto recipes, not Yocto. The recipes have issues that you don't see when building recipes manually written for Yocto. These recipes get converted from .spec files to .bb files based on the build configuration for x86. All architecture specific tweaks in Tizen get lost at that point and have to be added back manually to the generated .bb files. The spec2yocto conversion tool also does not have enough information available in the .spec files about dependencies (is a tool needed or something to link against?) and has to use heuristics, which fail in some cases when doing cross-compilation. It looks like you have skipped my announce of successful building of Tizen IVI on Yocto for ARM-based board DRA7XX. And as far as I recall Leon have used few my recipes changes in his buildings. It was the reason why I expected than Leon would understand me :) Vitaly, yes I used parts of your recipes. Actually similar fixes exist for the recipes in the fork of Tizen:Common for Raspberry Pi 2 which is maintained by Samsung Open Source Group. In my opinion the main problem at the moment is that building Tizen:Common or Tizen IVI using Yocto for ARM does not work out of the box. But, is building Tizen IVI for ARM using GBS working now? About half of year ago it doesn't work and amount of efforts to made it working was much-more bigger than insignificant efforts to made Tizen IVI on Yocto for ARM working. I haven't built any Tizen profiles with GBS recently. I think that the daily images of Tizen:Common are built using GBS. New Tizen:Common images for ARM are available so I assume it should be working: http://download.tizen.org/snapshots/tizen/common/latest/images/ As far as I remember your changes related to DRA7XX were pushed into a sandbox. Do you plan to merge them with tizen-distro upstream As far as I understand Tizen maintainers they will do it themselves when they will be interesting in it. I doubt that the maintainers have the resources to do it right now. According to git log there have been almost no changes for several months in the upstream of Tizen on Yocto for Tizen:Common and Tizen IVI. Best regards, Leon and to support both ARM Intel machines with the same recipes? I do not know. I'm deallocated from Tizen activity so I do not have any ideas about it. With best regards, Thanks, Leon With best regards, -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. -- *Vitaly Chernooky | Senior Developer
Re: [IVI] tizen ivi for the Renesas R-Car M2 ARM platform using yocto?
Hi Vitaly, Patrick, On 11.05.2015 16:49, Patrick Ohly wrote: On Mon, 2015-05-11 at 15:55 +0300, Vitaly Chernooky wrote: Hi Leon, On Fri, May 8, 2015 at 4:32 PM, Leon Anavi leon.an...@konsulko.com wrote: Hi Pedro, On 8.05.2015 14:59, pedro.quei...@elektrobit.com wrote: Hi all, I have started an attempt to build tizen ivi for the Renesas R-Car M2 ARM platform (Koelsch board), one of the goals would be to attempt graphics hw acceleration with the proprietary drivers. There are some instructions available in the wiki regarding using gbs. Nevertheless I wonder whether someone did or is in the process going the same using yocto? Building Tizen:Common or any of the Tizen profiles based on it (like IVI) for ARM using Yocto isn't easy task. In my opinion the Yocto recipes are not perfect and you will have numerous challenges if you try to build them for any devices with CPU different from Intel. I have different opinion on it. According to my experience with Yocto, it is much more easier to build for ARM with Yocto than with gbs ;) The comment was about the Tizen on Yocto recipes, not Yocto. The recipes have issues that you don't see when building recipes manually written for Yocto. These recipes get converted from .spec files to .bb files based on the build configuration for x86. All architecture specific tweaks in Tizen get lost at that point and have to be added back manually to the generated .bb files. The spec2yocto conversion tool also does not have enough information available in the .spec files about dependencies (is a tool needed or something to link against?) and has to use heuristics, which fail in some cases when doing cross-compilation. Yes, my previous comment was about Tizen on Yocto, not Yocto. Patrick, thank you for the provided details regarding the existing Tizen recipes. It seems that a lot of developers are interested in building Tizen using Yocto. I hope that together we can improve step by step the existing recipes. It will be nice if building Tizen using Yocto for both Intel and ARM is as straight-forward as building Poky (the reference system of the Yocto project). Best regards, Leon -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] tizen ivi for the Renesas R-Car M2 ARM platform using yocto?
Hi Pedro, On 8.05.2015 14:59, pedro.quei...@elektrobit.com wrote: Hi all, I have started an attempt to build tizen ivi for the Renesas R-Car M2 ARM platform (Koelsch board), one of the goals would be to attempt graphics hw acceleration with the proprietary drivers. There are some instructions available in the wiki regarding using gbs. Nevertheless I wonder whether someone did or is in the process going the same using yocto? Building Tizen:Common or any of the Tizen profiles based on it (like IVI) for ARM using Yocto isn't easy task. In my opinion the Yocto recipes are not perfect and you will have numerous challenges if you try to build them for any devices with CPU different from Intel. Recently my colleagues and I have managed to build Tizen:Common with hardware acceleration in Wayland/Weston for HummingBoard-i2eX using Yocto. I am still working on improvements of the recipes. You can find all the details at Tizen wiki: https://wiki.tizen.org/wiki/HummingBoard Another very useful article is the tutorial from Samsung Open Source Group about building Tizen:Common for Raspberry Pi 2 (without hardware acceleration): http://blogs.s-osg.org/bringing-tizen-to-a-raspberry-pi-2-near-you/ Best regards, Leon Motivation behind yocto is that yocto meta-layers for the r-car-m2 already exist, which could ease the integration of the proprietary drivers. Looking forward to have news from you. Best Regards, Pedro Q. Please note: This e-mail may contain confidential information intended solely for the addressee. If you have received this e-mail in error, please do not disclose it to anyone, notify the sender promptly, and delete the message from your system. Thank you. ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] Tizen:Common on HummingBoard-i2eX (Freescale i.MX6) using Yocto
Hi, A short video of Tizen:Common for HummingBoard-i2eX has been uploaded at YouTube: https://youtu.be/cEYrwipFKOg I have added more details to the article at Tizen wiki, including a section about flashing with bmaptool: https://wiki.tizen.org/wiki/HummingBoard#Using_bmaptool Best regards, Leon On 7.05.2015 21:28, Leon Anavi wrote: Hi, Using Yocto my colleagues from Konsulko Group and I have successfully built Tizen:Common with Linux kernel 3.14.14 and hardware accelerated graphics in Wayland/Weston for HummingBoard-i2eX (Freescale i.MX6 SoC). The procedure is described at: https://wiki.tizen.org/wiki/HummingBoard#Building_Tizen:Common_with_Yocto We used the existing fixes at the tizen-distro for Raspberry Pi 2 and we applied several changes: - EGL support was enabled in Wayland/Weston recipes, - Vivante EGL and GAL2D compositor support was added, - Systemd services were modified to launch Weston with hardware graphics acceleration. Best regards, Leon -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
[IVI] Tizen:Common on HummingBoard-i2eX (Freescale i.MX6) using Yocto
Hi, Using Yocto my colleagues from Konsulko Group and I have successfully built Tizen:Common with Linux kernel 3.14.14 and hardware accelerated graphics in Wayland/Weston for HummingBoard-i2eX (Freescale i.MX6 SoC). The procedure is described at: https://wiki.tizen.org/wiki/HummingBoard#Building_Tizen:Common_with_Yocto We used the existing fixes at the tizen-distro for Raspberry Pi 2 and we applied several changes: - EGL support was enabled in Wayland/Weston recipes, - Vivante EGL and GAL2D compositor support was added, - Systemd services were modified to launch Weston with hardware graphics acceleration. Best regards, Leon -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] Tizen Wiki Article about Wayland Weston on Tizen for Freescale i.MX6 SoC
Hi Ray, Last week, following the guidelines from your previous email, I have successfully built and configured Wayland and Weston 1.6 on HummingBoard-i2eX using Tizen IVI with Linux kernel 3.14 and GPU drivers from BSP L3.10.17. The procedure is described in details at Tizen wiki: https://wiki.tizen.org/wiki/Building_Wayland_and_Weston_on_Tizen_Device_with_Freescale_i.MX6_SoC Thanks, Leon On 26.03.2015 13:10, Leon Anavi wrote: Hi Ray, On 26.03.2015 12:30, RayBloodworth wrote: Hi Leon, Since this GPU lib using fb-backend, multi-seat seems like not working. In weston.ini the output section is not working. No mater how I modify config files, weston always using default seat for video output and input device... I think multi-seat is for drm-backend. Do you have any ideas about this? I have not tried out the multi-seat configuration. Btw the following presentations about Tizen multi user support might provide some useful information for this particular case: * FOSDEM 2014: Tizen 3 Application Framework: A multi User App Framework for IVI, Dominig ar Foll https://archive.fosdem.org/2014/schedule/event/tizen3appframework/ video: http://mirrors.dotsrc.org/fosdem/2014/H1309_Van_Rijn/Sunday/Tizen_3_Application_Framework.webm * FOSDEM 2015: Multi User support in an embedded secured environment: Pratical return of experience from Tizen 3 in Automotive, Kévin Thierry https://fosdem.org/2015/schedule/event/embedded_multiuser/ video: http://ftp.osuosl.org/pub/fosdem//2015/devroom-embedded/embedded_multiuser.mp4 Best regards, Leon BR, Ray Date: Thu, 26 Mar 2015 11:17:25 +0200 From: leon.an...@konsulko.com To: k870818...@outlook.com; ivi@lists.tizen.org CC: d...@lists.tizen.org Subject: Re: Tizen Wiki Article about Wayland Weston on Tizen for Freescale i.MX6 SoC Hi Ray, Thank you for the merged pull request and the provide information about Wayland/Weston 1.6. We should describe all these details at Tizen Wiki. I will give it a try and I will provide feedback. Thanks, Leon On 26.03.2015 07:24, RayBloodworth wrote: Hi, Leon Your pull request has been merged. After reading your links, I find that there are some notices you should know. 1. The BSP version you used were 3.0.10, the latest version is 3.10.53 which support wayland-1.6.0. git://git.freescale.com/imx/fsl-arm-yocto-bsp.git -b imx-3.10.53-1.1.0_ga After this version, fsl will move to 3.14.xx. 2. With BSP 3.10.53, once build wayland-image, symbol links are no need to be added. 3. In Tizen IVI, weston-launch should be enabled with removing--disable-weston-launch option. 4. In Tizen IVI, weston-launch should be +s using chmod +s /usr/bin/weston-launch after make install. 5. In Tizen IVI, /usr/lib/systemd/user/weston.service should be modified: -ExecStart=/usr/bin/weston-launch --i0 -current-mode +ExecStart=/usr/bin/weston-launch --i0 6. users should have permission rw to access /dev/galcore. 7. The most important point is sfp/hfp.(soft float point and hard float point). fsl support hfp, but current tizen image is build with sfp, so these gpu libs and other libs should be sfp. :) Ray Date: Wed, 25 Mar 2015 16:15:42 +0200 From: leon.an...@konsulko.com mailto:leon.an...@konsulko.com To: ivi@lists.tizen.org mailto:ivi@lists.tizen.org CC: d...@lists.tizen.org mailto:d...@lists.tizen.org; k870818...@outlook.com mailto:k870818...@outlook.com Subject: Re: Tizen Wiki Article about Wayland Weston on Tizen for Freescale i.MX6 SoC Hi Ray, All, Today I have build from scratch and launched Wayland and Weston 1.5 on Tizen IVI for HummingBoard-i2eX with Freescale i.MX6 Dual SoC. I have updated the step by step tutorial that I published yesterday at Tizen Wiki: https://wiki.tizen.org/wiki/Building_Wayland_and_Weston_on_Tizen_Device_with_Freescale_i.MX6_SoC Ray, I have send you a pull request at GitHub with an update of the README file of your repository porting_tizen_to_imx6q. I hope you will accept and merge it as it contains links to the Tizen Wiki which will facilitate other developer: https://github.com/RayBloodworth/porting_tizen_to_imx6q/pull/1 Best regards, Leon On 24.03.2015 20:18, Leon Anavi wrote: Hi, I have created a new wiki article about building from scratch Wayland and Weston on Tizen IVI (and Tizen:Common) for devices with Freescale i.MX6 ARM SoC: https://wiki.tizen.org/wiki/Building_Wayland_and_Weston_on_Tizen_Device_with_Freescale_i.MX6_SoC I spotted that other Tizen developers are also working on the i.MX6 and have discussed some
Re: [IVI] Tizen Wiki Article about Wayland Weston on Tizen for Freescale i.MX6 SoC
Hi Ray, Thank you for the merged pull request and the provide information about Wayland/Weston 1.6. We should describe all these details at Tizen Wiki. I will give it a try and I will provide feedback. Thanks, Leon On 26.03.2015 07:24, RayBloodworth wrote: Hi, Leon Your pull request has been merged. After reading your links, I find that there are some notices you should know. 1. The BSP version you used were 3.0.10, the latest version is 3.10.53 which support wayland-1.6.0. git://git.freescale.com/imx/fsl-arm-yocto-bsp.git -b imx-3.10.53-1.1.0_ga After this version, fsl will move to 3.14.xx. 2. With BSP 3.10.53, once build wayland-image, symbol links are no need to be added. 3. In Tizen IVI, weston-launch should be enabled with removing--disable-weston-launch option. 4. In Tizen IVI, weston-launch should be +s using chmod +s /usr/bin/weston-launch after make install. 5. In Tizen IVI, /usr/lib/systemd/user/weston.service should be modified: -ExecStart=/usr/bin/weston-launch --i0 -current-mode +ExecStart=/usr/bin/weston-launch --i0 6. users should have permission rw to access /dev/galcore. 7. The most important point is sfp/hfp.(soft float point and hard float point). fsl support hfp, but current tizen image is build with sfp, so these gpu libs and other libs should be sfp. :) Ray Date: Wed, 25 Mar 2015 16:15:42 +0200 From: leon.an...@konsulko.com To: ivi@lists.tizen.org CC: d...@lists.tizen.org; k870818...@outlook.com Subject: Re: Tizen Wiki Article about Wayland Weston on Tizen for Freescale i.MX6 SoC Hi Ray, All, Today I have build from scratch and launched Wayland and Weston 1.5 on Tizen IVI for HummingBoard-i2eX with Freescale i.MX6 Dual SoC. I have updated the step by step tutorial that I published yesterday at Tizen Wiki: https://wiki.tizen.org/wiki/Building_Wayland_and_Weston_on_Tizen_Device_with_Freescale_i.MX6_SoC Ray, I have send you a pull request at GitHub with an update of the README file of your repository porting_tizen_to_imx6q. I hope you will accept and merge it as it contains links to the Tizen Wiki which will facilitate other developer: https://github.com/RayBloodworth/porting_tizen_to_imx6q/pull/1 Best regards, Leon On 24.03.2015 20:18, Leon Anavi wrote: Hi, I have created a new wiki article about building from scratch Wayland and Weston on Tizen IVI (and Tizen:Common) for devices with Freescale i.MX6 ARM SoC: https://wiki.tizen.org/wiki/Building_Wayland_and_Weston_on_Tizen_Device_with_Freescale_i.MX6_SoC I spotted that other Tizen developers are also working on the i.MX6 and have discussed some of the issues in the mailing list but so far there was no Tizen wiki article. I hope that the new article will help other developers. So far I have successfully build and run demo applications on the latest Tizen IVI image (from 4 February) with Wayland (version 1.1.0) and Weston (version 1.1.1). I plan to explore and update the process for building and running newer version of Wayland and Weston (1.5 and 1.6). Best regards, Leon -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] Tizen Wiki Article about Wayland Weston on Tizen for Freescale i.MX6 SoC
Hi Ray, On 26.03.2015 12:30, RayBloodworth wrote: Hi Leon, Since this GPU lib using fb-backend, multi-seat seems like not working. In weston.ini the output section is not working. No mater how I modify config files, weston always using default seat for video output and input device... I think multi-seat is for drm-backend. Do you have any ideas about this? I have not tried out the multi-seat configuration. Btw the following presentations about Tizen multi user support might provide some useful information for this particular case: * FOSDEM 2014: Tizen 3 Application Framework: A multi User App Framework for IVI, Dominig ar Foll https://archive.fosdem.org/2014/schedule/event/tizen3appframework/ video: http://mirrors.dotsrc.org/fosdem/2014/H1309_Van_Rijn/Sunday/Tizen_3_Application_Framework.webm * FOSDEM 2015: Multi User support in an embedded secured environment: Pratical return of experience from Tizen 3 in Automotive, Kévin Thierry https://fosdem.org/2015/schedule/event/embedded_multiuser/ video: http://ftp.osuosl.org/pub/fosdem//2015/devroom-embedded/embedded_multiuser.mp4 Best regards, Leon BR, Ray Date: Thu, 26 Mar 2015 11:17:25 +0200 From: leon.an...@konsulko.com To: k870818...@outlook.com; ivi@lists.tizen.org CC: d...@lists.tizen.org Subject: Re: Tizen Wiki Article about Wayland Weston on Tizen for Freescale i.MX6 SoC Hi Ray, Thank you for the merged pull request and the provide information about Wayland/Weston 1.6. We should describe all these details at Tizen Wiki. I will give it a try and I will provide feedback. Thanks, Leon On 26.03.2015 07:24, RayBloodworth wrote: Hi, Leon Your pull request has been merged. After reading your links, I find that there are some notices you should know. 1. The BSP version you used were 3.0.10, the latest version is 3.10.53 which support wayland-1.6.0. git://git.freescale.com/imx/fsl-arm-yocto-bsp.git -b imx-3.10.53-1.1.0_ga After this version, fsl will move to 3.14.xx. 2. With BSP 3.10.53, once build wayland-image, symbol links are no need to be added. 3. In Tizen IVI, weston-launch should be enabled with removing--disable-weston-launch option. 4. In Tizen IVI, weston-launch should be +s using chmod +s /usr/bin/weston-launch after make install. 5. In Tizen IVI, /usr/lib/systemd/user/weston.service should be modified: -ExecStart=/usr/bin/weston-launch --i0 -current-mode +ExecStart=/usr/bin/weston-launch --i0 6. users should have permission rw to access /dev/galcore. 7. The most important point is sfp/hfp.(soft float point and hard float point). fsl support hfp, but current tizen image is build with sfp, so these gpu libs and other libs should be sfp. :) Ray Date: Wed, 25 Mar 2015 16:15:42 +0200 From: leon.an...@konsulko.com mailto:leon.an...@konsulko.com To: ivi@lists.tizen.org mailto:ivi@lists.tizen.org CC: d...@lists.tizen.org mailto:d...@lists.tizen.org; k870818...@outlook.com mailto:k870818...@outlook.com Subject: Re: Tizen Wiki Article about Wayland Weston on Tizen for Freescale i.MX6 SoC Hi Ray, All, Today I have build from scratch and launched Wayland and Weston 1.5 on Tizen IVI for HummingBoard-i2eX with Freescale i.MX6 Dual SoC. I have updated the step by step tutorial that I published yesterday at Tizen Wiki: https://wiki.tizen.org/wiki/Building_Wayland_and_Weston_on_Tizen_Device_with_Freescale_i.MX6_SoC Ray, I have send you a pull request at GitHub with an update of the README file of your repository porting_tizen_to_imx6q. I hope you will accept and merge it as it contains links to the Tizen Wiki which will facilitate other developer: https://github.com/RayBloodworth/porting_tizen_to_imx6q/pull/1 Best regards, Leon On 24.03.2015 20:18, Leon Anavi wrote: Hi, I have created a new wiki article about building from scratch Wayland and Weston on Tizen IVI (and Tizen:Common) for devices with Freescale i.MX6 ARM SoC: https://wiki.tizen.org/wiki/Building_Wayland_and_Weston_on_Tizen_Device_with_Freescale_i.MX6_SoC I spotted that other Tizen developers are also working on the i.MX6 and have discussed some of the issues in the mailing list but so far there was no Tizen wiki article. I hope that the new article will help other developers. So far I have successfully build and run demo applications on the latest Tizen IVI image (from 4 February) with Wayland (version 1.1.0) and Weston (version 1.1.1). I plan to explore and update the process for building and running newer version of Wayland
Re: [IVI] Tizen Wiki Article about Wayland Weston on Tizen for Freescale i.MX6 SoC
Hi Ray, All, Today I have build from scratch and launched Wayland and Weston 1.5 on Tizen IVI for HummingBoard-i2eX with Freescale i.MX6 Dual SoC. I have updated the step by step tutorial that I published yesterday at Tizen Wiki: https://wiki.tizen.org/wiki/Building_Wayland_and_Weston_on_Tizen_Device_with_Freescale_i.MX6_SoC Ray, I have send you a pull request at GitHub with an update of the README file of your repository porting_tizen_to_imx6q. I hope you will accept and merge it as it contains links to the Tizen Wiki which will facilitate other developer: https://github.com/RayBloodworth/porting_tizen_to_imx6q/pull/1 Best regards, Leon On 24.03.2015 20:18, Leon Anavi wrote: Hi, I have created a new wiki article about building from scratch Wayland and Weston on Tizen IVI (and Tizen:Common) for devices with Freescale i.MX6 ARM SoC: https://wiki.tizen.org/wiki/Building_Wayland_and_Weston_on_Tizen_Device_with_Freescale_i.MX6_SoC I spotted that other Tizen developers are also working on the i.MX6 and have discussed some of the issues in the mailing list but so far there was no Tizen wiki article. I hope that the new article will help other developers. So far I have successfully build and run demo applications on the latest Tizen IVI image (from 4 February) with Wayland (version 1.1.0) and Weston (version 1.1.1). I plan to explore and update the process for building and running newer version of Wayland and Weston (1.5 and 1.6). Best regards, Leon -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] Tizen IVI on a tablet?
Hi Philippe, On 23.03.2015 23:35, Philippe Coval wrote: Do you expect to have GPU support on wayland too ? This is a blocking point for us, so any hints are welcome Yes, indeed. As far as I remember we saw Tizen:Common and Weston running with graphical acceleration on hardware development boards with Allwinner A20 SoC during Tizen Developer Summit 2014 but as far as I know these drivers are not freely available. I am currently working on running Wayland Weston with graphical acceleration for Tizen IVI for another ARM board with i.MX6 but I am facing several issues. I will keep you updated. Best regards, Leon -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] ABOUT [Build Tizen with Yocto Project]=====https://wiki.tizen.org/wiki/Build_Tizen_with_Yocto_Project
On 17.03.2015 12:06, Vitaly Chernooky wrote: Ok, Thanks. I re-synced my repository and now I see your changes. You are welcome. I added a note to the wiki article to avoid any confusions in future: https://wiki.tizen.org/wiki/Build_Tizen_with_Yocto_Project#For_Tizen_IVI Best regards, Leon With best regards, On Tue, Mar 17, 2015 at 12:00 PM, Leon Anavi leon.an...@konsulko.com mailto:leon.an...@konsulko.com wrote: Hi Vitaly, On 17.03.2015 11:57, Vitaly Chernooky wrote: Leon, Is that changes already propagated to tizen-distro? Yes, it was merged three weeks ago. For details please have a look at: https://review.tizen.org/gerrit/#/c/35644/ Best regards, Leon With best regards, On Tue, Mar 17, 2015 at 11:48 AM, Leon Anavi leon.an...@konsulko.com mailto:leon.an...@konsulko.com wrote: Hi, On 17.03.2015 11:37, 1034659...@qq.com mailto:1034659...@qq.com wrote: export: CFLAGS+ My guess is that you are building on machine with Ubuntu or Debian and you are experiencing bashism issues. Are you using the latest version of Tizen Yocto? I recently fixed several similar issues and contributed them the upstream. For more details please have a look at: https://bugs.tizen.org/jira/browse/BTY-104 Best regards, Leon -- Leon Anavi Software Engineer Mob : +359 88 527 7901 tel:%2B359%2088%20527%207901 konsulko.com http://konsulko.com ___ IVI mailing list IVI@lists.tizen.org mailto:IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi -- *Vitaly Chernooky | Senior Developer - Product Engineering and Development* GlobalLogic P _+380.44.4929695 tel:%2B380.44.4929695 ext.1136_ M _+380.63.6011802 tel:%2B380.63.6011802_ S cvv_2k www.globallogic.com http://www.globallogic.com http://www.globallogic.com/email_disclaimer.txt -- Leon Anavi Software Engineer Mob :+359 88 527 7901 tel:%2B359%2088%20527%207901 konsulko.com http://konsulko.com -- *Vitaly Chernooky | Senior Developer - Product Engineering and Development* GlobalLogic P _+380.44.4929695 ext.1136_ M _+380.63.6011802_ S cvv_2k www.globallogic.com http://www.globallogic.com http://www.globallogic.com/email_disclaimer.txt -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] ABOUT [Build Tizen with Yocto Project]=====https://wiki.tizen.org/wiki/Build_Tizen_with_Yocto_Project
Hi, On 17.03.2015 11:37, 1034659...@qq.com wrote: export: CFLAGS+ My guess is that you are building on machine with Ubuntu or Debian and you are experiencing bashism issues. Are you using the latest version of Tizen Yocto? I recently fixed several similar issues and contributed them the upstream. For more details please have a look at: https://bugs.tizen.org/jira/browse/BTY-104 Best regards, Leon -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] Automotive Grade Linux application suite release
Hi Kenneth, On 10.03.2015 01:59, Smith, Kenneth wrote: We have made available the source code for the latest version of our suite of crosswalk applications. See it here: AGL_App_Suite https://gerrit.automotivelinux.org/gerrit/gitweb?p=POC-HTML5-UI/AGL_App_Suite.git;a=summary Thank you for sharing the source code of these applications. What is the procedure for contributing changes to the AGL App Suite at gerrit.automotivelinux.org? I noticed that the makefiles of the DNA HMI applications rely on xwalkctl -i to install wgt files. On latest Tizen IVI version this command fails with option parsing failed: Unknown option -i because recently xwalkctl has been replaced by pkgcmd. Please have a look at the official documentation of Crosswalk and/or Tizen Wiki for more details: https://crosswalk-project.org/documentation/getting_started/run_on_tizen.html#Install-the-application-package https://wiki.tizen.org/wiki/Installing_Web_Applications_on_Tizen:Common_and_Tizen_IVI In my opinion it is recommended to replace xwalkctl -i with pkgcmd -i -t wgt -q -p in the makefiles and to ensure that they will be working on targets with the latest version of Tizen IVI. Best regards, Leon -- Kind Regards, *Kenneth F. Smith* Linux C++ Engineer *T:* 971.256.9740 | *M:* 503-880-6256 *Email:* ksmit...@jaguarlandrover.com mailto:ksmit...@jaguarlandrover.com Jaguar Land Rover North America, LLC Open Source Technology Center 1419 Northwest 14th Avenue, Portland, OR 97209 JaguarUSA.com http://www.jaguarusa.com/index.html | LandRoverUSA.com http://www.landrover.com/us/en/lr/ Email: ksmit...@jaguarlandrover.com mailto:x...@jaguarlandrover.com PGP: RSA 2048/2048 979C6B958B89909D --- Business Details: Jaguar Land Rover Limited Registered Office: Abbey Road, Whitley, Coventry CV3 4LF Registered in England No: 1672070 This e-mail and any attachments contain confidential information for a specific individual and purpose. The information is private and privileged and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, please e-mail us immediately. We apologise for any inconvenience caused but you are hereby notified that any disclosure, copying or distribution or the taking of any action in reliance on the information contained herein is strictly prohibited. This e-mail does not constitute an order for goods or services unless accompanied by an official purchase order. ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] Automotive Grade Linux application suite release
Hi Art, On 10.03.2015 16:43, McGee, Art wrote: Leon, This is probably an error on my part. The Make files do have the xwalkctl and the pkgcmd for installation and run. To use the pkgcmd use 'run.feb1' or 'install.feb1'. I could update the makefile but the other will work on the October Milestone. I tend to make stepping stones instead of removing an older way entirely. OK, I see. I will use 'run.feb1' or 'install.feb1' for the latest versions. Thank you for the provided feedback. Thanks, Leon Thanks, Art McGee On 10 March 2015 at 07:30, Leon Anavi leon.an...@konsulko.com mailto:leon.an...@konsulko.com wrote: Hi Kenneth, On 10.03.2015 01:59, Smith, Kenneth wrote: We have made available the source code for the latest version of our suite of crosswalk applications. See it here: AGL_App_Suite https://gerrit.automotivelinux.org/gerrit/gitweb?p=POC-HTML5-UI/AGL_App_Suite.git;a=summary Thank you for sharing the source code of these applications. What is the procedure for contributing changes to the AGL App Suite at gerrit.automotivelinux.org http://gerrit.automotivelinux.org? I noticed that the makefiles of the DNA HMI applications rely on xwalkctl -i to install wgt files. On latest Tizen IVI version this command fails with option parsing failed: Unknown option -i because recently xwalkctl has been replaced by pkgcmd. Please have a look at the official documentation of Crosswalk and/or Tizen Wiki for more details: https://crosswalk-project.org/documentation/getting_started/run_on_tizen.html#Install-the-application-package https://wiki.tizen.org/wiki/Installing_Web_Applications_on_Tizen:Common_and_Tizen_IVI In my opinion it is recommended to replace xwalkctl -i with pkgcmd -i -t wgt -q -p in the makefiles and to ensure that they will be working on targets with the latest version of Tizen IVI. Best regards, Leon -- Kind Regards, *Kenneth F. Smith* Linux C++ Engineer *T:* 971.256.9740 | *M:* 503-880-6256 *Email:* ksmit...@jaguarlandrover.com mailto:ksmit...@jaguarlandrover.com Jaguar Land Rover North America, LLC Open Source Technology Center 1419 Northwest 14th Avenue, Portland, OR 97209 JaguarUSA.com http://www.jaguarusa.com/index.html | LandRoverUSA.com http://www.landrover.com/us/en/lr/ Email: ksmit...@jaguarlandrover.com mailto:x...@jaguarlandrover.com PGP: RSA 2048/2048 979C6B958B89909D --- Business Details: Jaguar Land Rover Limited Registered Office: Abbey Road, Whitley, Coventry CV3 4LF Registered in England No: 1672070 This e-mail and any attachments contain confidential information for a specific individual and purpose. The information is private and privileged and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, please e-mail us immediately. We apologise for any inconvenience caused but you are hereby notified that any disclosure, copying or distribution or the taking of any action in reliance on the information contained herein is strictly prohibited. This e-mail does not constitute an order for goods or services unless accompanied by an official purchase order. ___ IVI mailing list IVI@lists.tizen.org mailto:IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com http://konsulko.com -- *Art McGee* Infotainment Engineer Jaguar Land Rover North America, LLC 1419 NW 14th Ave, Portland, Oregon, 97209 JaguarUSA.com http://www.jaguarusa.com/index.html | LandRoverUSA.com http://www.landrover.com/us/en/lr/ -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] Running Tizen IVI on VMware and/or VirtualBox
Hi Philippe, On 6.03.2015 22:29, Philippe Coval wrote: On Fri, Mar 6, 2015 at 5:56 PM, Leon Anavi leon.an...@konsulko.com mailto:leon.an...@konsulko.com wrote: Hi Art, On 6.03.2015 18:48, McGee, Art wrote: Leon, I have not tried the latest release of Tizen in a VM yet but I have done it before. I used this for reference. I would like to know if you get it to work. I'll give it a shot myself sometime when I get a chance. Yes, latest Tizen IVI images work fine with VMware Player on Linux (and VMware Fusion for Mac). Do you have accelerated graphics on it ? Yes, I have accelerated graphics of the Tizen IVI image on the VMware Player on Ubuntu and on VMware Fusion for Mac. Would it help if I share vmware image of tizen:common that works with accelerated graphics before we upgrade mesa ? Thank you for your support but there is no need to do it at the moment. Tizen IVI image also seems fine. Best regards, Leon If yes I'll do that next week if you don't mind later -- mailto:philippe.co...@eurogiciel.fr mailto:philippe.co...@eurogiciel.fr -- gpg:0x467094BC xmpp:philippe.coval@gmail.com mailto:xmpp%3aphilippe.coval@gmail.com https://dockr.eurogiciel.fr/blogs/embedded/author/pcl/ . -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
[IVI] Running Tizen IVI on VMware and/or VirtualBox
Hi, I need to run Tizen IVI in a virtual machine so I explored the available options and I updated the Tizen wiki: https://wiki.tizen.org/wiki/Emulator I was able to run successfully Tizen IVI on my desktop with Ubuntu 14.10 using VMware Player and with VMware Fusion I got working on Mac OS X Yosemite. As of the moment on VirtualBox there are no guest additions with Wayland support which makes it impossible to run Weston and Crosswalk applications. But It is possible to convert Tizen IVI image to vdi and to run Tizen in console mode on VirtualBox. With a Linux kernel and a module for Frame Buffer it might be possible to run Tizen IVI image with Weston in software mode. Best regards, Leon -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
[IVI] Unable to build Tizen IVI image with Yocto for haswell-wc (MinnowBoard MAX)
Hi, I am unable to build Tizen IVI image with Yocto for MinnowBoard MAX using machine configuration haswell-wc due to a problem with the recipe for FFmpeg-based GStreamer plug-in (gst-ffmpeg_0.10.13.bb). If you have experienced the same issue or if you want to learn details please have a look at Tizen JIRA: https://bugs.tizen.org/jira/browse/BTY-105 The Yocto built for valleyisland-64 finished successfully. Tizen wiki contains instructions about building Tizen IVI with Yocto for MinnowBoard on two separate locations. I don't think it is a good approach to duplicate content as it requires more efforts to maintain it. There were some differences with I fixed at one on the artciles: https://wiki.tizen.org/wiki/Yocto_Tizen_on_MinnowBoard_Max https://wiki.tizen.org/wiki/MinnowMax#Build_Tizen_with_Yocto Best regards, Leon -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] Issues with Tizen IVI on Yocto
Hi Patrick, All, I am happy to announce that on Monday my changes were accepted and merged in the Tizen IVI branch: https://review.tizen.org/gerrit/35644 At the moment my tests show it is possible to build Tizen IVI image using Yocto the default configuration at local.conf on Debian and Ubuntu without the need to modify build.py. For more details please visit Tizen JIRA: https://bugs.tizen.org/jira/browse/BTY-104 Best regards, Leon On 20.02.2015 18:21, Leon Anavi wrote: Hi Patrick, On 20.02.2015 17:11, Patrick Ohly wrote: On Fri, 2015-02-20 at 15:27 +0200, Leon Anavi wrote: On 20.02.2015 12:31, Patrick Ohly wrote: These bashism issues should indeed be better fixed in the .spec files and not the .inc files derived from them, so this guide applies. However, it is uncertain whether working with non-bash shell interpreters is a goal for Tizen; at the moment it is not tested for consistently, neither in OBS nor in Tizen on Yocto. So it is unclear whether maintainers will accept such patches. Worse, such issues may get re-introduced. Overall I think it's easier to accept that .inc files depend on bash and patch build.py in tizen-distro as suggested above. As far as I know Ubuntu is among the supported platforms for both Tizen IVI application and platform development and its default system shell is dash. In my opinion the change at the python scripts seems as a work around. It will be more user/developer friendly and more convenient if the Tizen build with Yocto works out of the box on Ubuntu. Patching build.py in tizen-distro would achieve that, too. I know that this looks like avoiding the issue, but it's simply less work and more likely to succeed. OK, may be a patch for build.py that automatically detects and replaces /bin/sh with /bin/bash depending on the distro makes sense. For the moment I will try to submit what I have when Tizen Gerrit is up and running again. If we want spec files to be free of bashisms (which is not needed for OBS and gbs, at least as far as I know), then this needs to be communicated clearly as a project goal, and it needs to be enforced as part of patch acceptance into the distro. As you noticed, Ronan has already tried for a long time to get spec files fixed, without success. Yocto is quite popular and a lot of people would rather use it than GBS. May be it is worth discussing this as a new project goal. Thanks, Leon -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
[IVI] Issues with Tizen IVI on Yocto
Hi, Recently I have built Tizen IVI with Yocto and I noted several issues related to the recipes for libmm-common, libmm-log and crosswalk. I have posted details at JIRA as well as information about the fixes that I applied locally: https://bugs.tizen.org/jira/browse/BTY-104 I am interested in contributing these fixes upstream. Is the following guide for contributions up to date and valid for changes related to Tizen on Yocto? https://wiki.tizen.org/wiki/How_to_contribute_to_Tizen_IVI Btw at the moment Tizen Gerrit is not available (504 Server Error) and I am unable to register my new SSH key. Best regards, Leon -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [IVI] Issues with Tizen IVI on Yocto
Hi Patrick, On 20.02.2015 17:11, Patrick Ohly wrote: On Fri, 2015-02-20 at 15:27 +0200, Leon Anavi wrote: On 20.02.2015 12:31, Patrick Ohly wrote: These bashism issues should indeed be better fixed in the .spec files and not the .inc files derived from them, so this guide applies. However, it is uncertain whether working with non-bash shell interpreters is a goal for Tizen; at the moment it is not tested for consistently, neither in OBS nor in Tizen on Yocto. So it is unclear whether maintainers will accept such patches. Worse, such issues may get re-introduced. Overall I think it's easier to accept that .inc files depend on bash and patch build.py in tizen-distro as suggested above. As far as I know Ubuntu is among the supported platforms for both Tizen IVI application and platform development and its default system shell is dash. In my opinion the change at the python scripts seems as a work around. It will be more user/developer friendly and more convenient if the Tizen build with Yocto works out of the box on Ubuntu. Patching build.py in tizen-distro would achieve that, too. I know that this looks like avoiding the issue, but it's simply less work and more likely to succeed. OK, may be a patch for build.py that automatically detects and replaces /bin/sh with /bin/bash depending on the distro makes sense. For the moment I will try to submit what I have when Tizen Gerrit is up and running again. If we want spec files to be free of bashisms (which is not needed for OBS and gbs, at least as far as I know), then this needs to be communicated clearly as a project goal, and it needs to be enforced as part of patch acceptance into the distro. As you noticed, Ronan has already tried for a long time to get spec files fixed, without success. Yocto is quite popular and a lot of people would rather use it than GBS. May be it is worth discussing this as a new project goal. Thanks, Leon -- Leon Anavi Software Engineer Mob : +359 88 527 7901 konsulko.com ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: tizen IVI on raspberry pi (and others)
Hi Grigory, On 2014-11-06 10:33, Grigory Ptashko wrote: Thank you very much for the hints. I've decided to take an easier way for now and install Tizen IVI on the Cubieboard 2 A20 with ARMv7. Just to get used to gbs, obs, applications and all the stuff.. In my opinion a board with A20 is a good choice. Hints for sunxi devices and download links for Tizen images for A20-OLinuXino-MICRO are available at: https://github.com/leon-anavi/tizen-sunxi The Tizen wiki also contains useful information: https://wiki.tizen.org/wiki/Sunxi Best regards, Leon -- http://anavi.org/ ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: IVI Digest, Vol 33, Issue 9
Hi Grigory, On 2014-11-06 14:00, ivi-requ...@lists.tizen.org wrote: 1. U-boot version for Tizen? Is there a special version of U-boot for Tizen which is located somewhere in the Tizen source tree? Or will the Sunxi's U-boot version will be enough to boot Tizen? It is recommended to use the linux-sunxi fork of Das U-Boot: https://github.com/linux-sunxi/u-boot-sunxi There is a version of U-Boot for Tizen but so far it is targeting Odroid and the Tizen developer devices trats (RD-210) and trats2 (PR-PQ) only. Information about U-Boot for Tizen has been revealed during LinuxCon Europe: http://sched.co/1xmhyG4 In another talk during the same event Hans de Goede revealed the status of U-Boot for Sunxi devices. As far as I remember he announced that the mainline U-Boot is (or will be soon) compatible with A10 A20. More details regarding his presentation are available at: http://sched.co/1xmrE9N 2. Tizen kernel source? As far as I understood (and I actuallty installed it myself) the freshest version of the Sunxi's kernel for A20 is 3.4. There are no kernels above 3.4 that will work with all the Cubieboard 2's hardware features. Is this also true for Tizen? Or there is some newer kernel version somewhere in the Tizen's source tree? Tizen:Common and IVI require kernel 3.14 LTSI but at the moment the latest stable version of the kernel for Sunxi devices is 3.4. There are ongoing initiatives among the linux-sunxi community to support mainline kernel on A20 but a lot of things are still not working properly. Anyway, you can boot Tizen:Common (and most probably IVI) using linux-sunxi kernel 3.4 on A20 devices. Pay attention that you have to adjust the FEX configuration file and to generate script.bin that matches the hardware of your board. Check this wiki article for hints: http://linux-sunxi.org/Fex_Guide In other words where should I take the sources for the U-boot and the kernel to boot latest Tizen IVI 3.0 on an A20 board? OK, long story short: please check the following links :) https://github.com/linux-sunxi/u-boot-sunxi https://github.com/linux-sunxi/linux-sunxi More information about Tizen on sunxi devices and open-source hardware is available at the talk that Phil and I did during Tizen Developer Summit last month: http://www.slideshare.net/leonanavi/tizen-oshwtds14sh20141021 Best regards, Leon -- http://anavi.org/ ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: tizen IVI on raspberry pi (and others)
Hi Phil, Grigory, tizen uses ARMv7 at least so you need to rebuild it all your own But, I remember ARMv6 work in progress where revealed at TdcSf14 check page 6 http://www.slideshare.net/MyungJooHam/tdc-mjham-armkernelintizen3noani armv6 support (Raspberry Pi) coming soon. (Thanks to Univ. of Warsaw) I also remember this presentation but I have seen any Tizen images for Raspberry Pi. Is there any new information about the status and the progress of the work on ARMv6 support of the Tizen toolchain? Best regards, Leon -- http://anavi.org/ ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: Issue with Tizen:Common X11 on Intel NUC
Hi Phil, On 2014-09-28 16:43, Philippe Coval wrote: On Sun, Sep 28, 2014 at 6:50 AM, Leon Anavi l...@anavi.org wrote: Hi All, I have also installed the package qt-tizen-demo but it seems that launch_video_qt.sh is not working fine. I see some colored lines moving around on monitor but there is no clean image. I guess this is not the expected result. yes this is a known issue check the bug tracker you can make QtMultimedia + Gst 1.x work w/out hw accell by uninstalling libva may work even without mesa , same with Qt designer I tested this month ago Good luck and keep us up to date if you manage to load mali driver on tizen-sunxi I did the same exercise but this time I cooked Tizen:Common ARM image for X11 with Linux-sunxi 3.4 kernel for A20-OLinuXino-MICRO. When I started X for the first time I got the following errors: _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/tizen:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 I was able to avoid these security problems by adding the following arguments to the command: -nolisten tcp The other issues that I experience with X on this image are: [ 1730.564] (EE) Failed to load module modesetting (module does not exist, 0) [ 1730.565] (EE) Failed to load module fbdev (module does not exist, 0) [ 1730.565] (EE) No drivers available. [ 1730.565] (EE) Fatal server error: [ 1730.576] (EE) no screens found(EE) [ 1730.581] (EE) Do you have any ideas what is causing the no screens found(EE) problem and how can it be solved? Thanks, Leon -- http://anavi.org/ ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: Mali support on Sunxi (ws Re: FW: Weston-launch failed in Tizen IVI 3.0-M3-June2014)
Hi, On 14/08/2014 13:22, kongling wrote: Hi, Is there anybody know anyting about this? Thanks! Yea I know what you mean, I would invite you to file a bug on jira to track integration of ARM mali-ddk on sunxi devices I'll may forward this elsewhere where we could get support since AllWinner is supporting FLOSS communities, but AFAIK mali blobs are comming from ARM Inc. Yes, the MALI driver is the blocking point at the moment for Tizen-sunxi. Note at the date of today , A10 and sunxi linux is unsupported by tizen project Let me invite you to consider exynos targets, or use fbdev as fallback it worked for my A20 Some hints over there : https://wiki.tizen.org/wiki/ARM https://wiki.tizen.org/wiki/Sunxi I have A10 and A10S devices and when I have some free time I will try to prepare Tizen:Common images for them based on the one working for A20. Best regards, Leon -- http://anavi.org/ ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: Tizen:Common can boot on armv7l sunxi ~ Re: [Dev] Activation of ARM Arch support in Tizen3
Hi Philippe, On 2014-05-22 20:07, Philippe Coval wrote: Also I can share demo sdcard images, just request it by email or find me a demo at TdcSf2014, I'll bring my toys... Could you please upload and provide the images in public (for example in Google Drive) so that anyone can download and try them? I can boot them on my A20-LinuXino. Btw I plan to visit Olimex office next week and to buy A10-OLinuXino-LIME (if they have the board in stock). Thanks, Leon -- http://anavi.org/ ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: [Dev] Activation of ARM Arch support in Tizen3
Hi Philippe, Dominig, All, On Fri, May 16, 2014 at 2:28 PM, Philippe Coval philippe.co...@eurogiciel.fr wrote: Would I suggest to evaluate this openhardware board, https://www.olimex.com/Products/OLinuXino/A20/ [3] I have one home for DIY and will be exited to help Tizen:Common working on it.. The interesting point here is that SOC ships ARM mali GPU which is the same familly as tizen mobile rdpq / rd210 Not to mention, that I met those bulgarian at fosdem 2014, and they supporting FLOSS communities... Let me add my hacker friend leon in the loop who will be at TDC too Thank you for adding me to the loop. Philippe and I discussed the idea in private email and chats during the past couple of days. I also support the Philippe's proposition to use A20-OLinuXino because it is open-source hardware development board and once the port is stable it can be easily adapted for other devices with Allwinner processors. A20-OLinuXino is manufactured by Olimex. Their office is based in my hometown Plovdiv, Bulgaria and I often get dedicated support when I have any hardware issues or questions. Olimex publishes complete schematics for their open-source hardware boards from the OLinuXino series in GitHub: https://github.com/OLIMEX/OLINUXINO I own a couple of development boards from Olimex and I have successfully booted Tizen IVI 2.0 on them by porting Tizen IVI images for Pandaboard. Their new board A10-OLinuXino-LIME also deserves attention and I plan to buy it in new future but it is less powerful than A20-OLinuXino. So as Philippe state at the moment A20-OLinuXino seems the most appropriate board from the Olimex product catalog for porting Tizen IVI 3.0. I would like to provide some useful resources: * Building Linux Kernel 3.4 and Uboot for A20-OLinuXino: timate-debian-sd-card-for-linux-with-kernel-3-4-for-a20-olinuxino-micro/ * Formatting the SD card for Pandaboard (the process is similar for OLinuXino boards): ki/Tizen_IVI_Getting_Started_Guide_For_PandaBoard#Formatting_the_SD_card * Tizen-sunxi: https://github.com/leon-anavi/tizen-sunxi Best regards, Leon -- http://anavi.org/ ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
