From dominig.arfoll at fridu.net Thu Feb 1 11:29:51 2018 From: dominig.arfoll at fridu.net (Dominig ar Foll (Intel Open Source)) Date: Thu, 1 Feb 2018 12:29:51 +0100 Subject: [agl-discussions] Failed to load module module-alsa-sink (trick to start pulse on Intel) In-Reply-To: References: Message-ID: An HTML attachment was scrubbed... URL: From fulup.arfoll at iot.bzh Thu Feb 1 14:18:29 2018 From: fulup.arfoll at iot.bzh (Fulup Ar Foll) Date: Thu, 1 Feb 2018 15:18:29 +0100 Subject: [agl-discussions] FYI: Today (1st/Feb) SAT meeting Cancel Message-ID: <4205384c-0604-fdeb-ac8b-5fd1c8f3c6e5@iot.bzh> FYI, Just had Walt on his mobile. His trip is delay more than expected and he unfortunately has to cancel the call. He apologises for the short notice, but he is still lock in a taxi and cannot open the call while moving. Fulup0 From Michael.Fabry at microchip.com Thu Feb 1 14:22:22 2018 From: Michael.Fabry at microchip.com (Michael.Fabry at microchip.com) Date: Thu, 1 Feb 2018 14:22:22 +0000 Subject: [agl-discussions] FYI: Today (1st/Feb) SAT meeting Cancel In-Reply-To: <4205384c-0604-fdeb-ac8b-5fd1c8f3c6e5@iot.bzh> References: <4205384c-0604-fdeb-ac8b-5fd1c8f3c6e5@iot.bzh> Message-ID: <131438561D29EC4A86762ADA6AE2B11B85330F61@CHN-SV-EXMX03.mchp-main.com> Hi Fulup, Thanks for notifying! Best regards, Michael -----Original Message----- From: automotive-discussions-bounces at lists.linuxfoundation.org [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On Behalf Of Fulup Ar Foll Sent: Donnerstag, 1. Februar 2018 15:18 To: automotive-discussions at lists.linuxfoundation.org Subject: [agl-discussions] FYI: Today (1st/Feb) SAT meeting Cancel FYI, Just had Walt on his mobile. His trip is delay more than expected and he unfortunately has to cancel the call. He apologises for the short notice, but he is still lock in a taxi and cannot open the call while moving. Fulup0 _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From fulup.arfoll at iot.bzh Fri Feb 2 10:40:17 2018 From: fulup.arfoll at iot.bzh (Fulup Ar Foll) Date: Fri, 2 Feb 2018 11:40:17 +0100 Subject: [agl-discussions] Xen integration In-Reply-To: References: Message-ID: Oleksandr, For audio with Eel & 4A the audio policy while technical possible, some real work needs to be done before moving to a production ready system. For a POC accessing audio policy from an other user domain should be relativity simple. 4A high level API is exposed through a standard AGL binder/binding and if you enable TCP on the audio binder you can request it from outside AGL. This behing said two things remains to be done: - 4A handle signalling but not the stream. 4A will return you with a sound URI, potentially an ALSA PCM or something more specific to your virtualisation environment. - AGL security model relies on SMACK and API protection does not cross operating systems boundaries. While be have as project to extend API protection to OpenID-connect for vehicule to cloud, as today nothing as been decided to extend AGL application framework capabilities to a virtualized environment. I thing this would be a nice discution topic for next AMM in Japan, will you attend ? Fulup On 31/01/18 15:41, Oleksandr Grytsov wrote: > Hi All, > > I'm from EPAM company? and we are working on integration Xen for automotive solutions. Recently we did some demo running Xen with AGL and Android on same board. From HW point of view it is Renesas board with two displays. One display is dedicated for AGL HomeScreen second one for Android. Basically AGL related tasks were to integrate our Display and Sound backends.? Display backend is a user space application with multiple wayland surfaces. Also Sound backend is a user space application with multiple pulse audio streams. For Sound backend we did nothing special as it works in AGL dab branch without interaction with AudioManager or adjusting any audio policies. But for Display beckend we did some tricks to make it works. > > Now I'm looking for proper backends integration. And have following questions: > > Display: > > * Multiple display support: I see some issue recently created to support it. Is there any draft spec? > * Multiple surface support: is there any possibility to support one application with multiple surfaces? If not is there plan to support it? > * Is it possible to work with WindowManager and HomeScreen if the application is not AGL widget but system daemon, for example? > > Sound: > > * What is proper way to integrate the application with AudioManager? > * Shell this application be AGL widget or it could be any user space application? > > Thanks. > > Oleksandr Grytsov > Lead Software Engineer > > Office:?+380 44 390 5457 x?66834 ? Cell:?+380 67 751 0148?? Email:?oleksandr_grytsov at epam.com > Kyiv,?Ukraine?(GMT+3)?? epam.com > > CONFIDENTIALITY CAUTION AND DISCLAIMER > This message is intended only for the use of the individual(s) or entity(ies) to which it is addressed and contains information that is legally privileged and confidential. If you are not the intended recipient, or the person responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. All unintended recipients are obliged to delete this message and destroy any printed copies. > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > From leon.anavi at konsulko.com Fri Feb 2 12:29:07 2018 From: leon.anavi at konsulko.com (Leon Anavi) Date: Fri, 2 Feb 2018 14:29:07 +0200 Subject: [agl-discussions] Meta-updater and OSTree demo at AGL stand at FOSDEM 2018 Message-ID: <0fa8ef5a-ad58-963a-554c-3f3aef2494b2@konsulko.com> Hi, I have prepared a demonstration of software updates for Automotive Grade Linux based on the Yocto/OE layer meta-updater and OSTree which I plan to show this weekend at the AGL stand at building AW during FOSDEM 2018. I will be at the stand on Saturday late afternoon and Sunday afternoon. Yocto/OE layer meta-updater includes recipes for OSTree and Aktualizr, an open source SOTA client implemented in C++ by ATS Advanced Telematic Systems GmbH. The straight-forward way to use meta-updater is through ATS Garage but it is also possible to use directly OSTree for deploying images. My demonstration will focus on the simple steps to perform a software update of agl-image-minimal on Raspberry Pi 3 using the ostree admin tool. Please stop by at AGL stand to have a look at my demo :) For more details about the technologies please have a look at following links: https://github.com/advancedtelematic/meta-updater https://docs.atsgarage.com/quickstarts/automotive-grade-linux.html https://wiki.automotivelinux.org/agl-distro/agl-raspberrypi http://docs.automotivelinux.org/docs/getting_started/en/dev/ Thanks, Leon -- Leon Anavi Software Engineer konsulko.com From wminer at linuxfoundation.org Fri Feb 2 17:38:41 2018 From: wminer at linuxfoundation.org (wminer at linuxfoundation.org) Date: Fri, 02 Feb 2018 17:38:41 +0000 Subject: [agl-discussions] Updated invitation: [AGL-SAT] Biweekly Call @ Wed Feb 7, 2018 3pm - 4pm (CET) (automotive-discussions@lists.linuxfoundation.org) Message-ID: <001a1145aec0e71acc05643e2ed3@google.com> This event has been changed. Title: [AGL-SAT] Biweekly Call AGL-SAT Biweekly Meeting Please join my meeting from your computer, tablet or smartphone. https://global.gotomeeting.com/join/796425741 You can also dial in using your phone. United States (Toll-free) 1 877 309 2070 United States +1 (312) 757-3119 Access Code: 796-425-741 More phone numbers Australia +61 2 8355 1034 Austria +43 7 2088 0716 Belgium +32 (0) 28 93 7002 Canada (Toll-free) 1 877 777 3281 Canada +1 (647) 497-9372 Denmark +45 69 91 84 58 Finland +358 (0) 923 17 0556 France +33 (0) 170 950 590 Germany +49 (0) 692 5736 7206 India (Toll-free) 000 800 100 8227 Ireland +353 (0) 19 030 053 Italy +39 0 699 26 68 65 Japan (Toll-free) 0 120 242 200 Korea, Republic of (Toll-free) 0806180880 Netherlands +31 (0) 208 080 759 New Zealand +64 9 974 9579 Norway +47 21 04 30 59 Spain +34 931 76 1534 Sweden +46 (0) 852 500 691 Switzerland +41 (0) 435 0026 89 United Kingdom +44 (0) 20 3713 5011 First GoToMeeting? Try a test session: http://help.citrix.com/getready When: Wed Feb 7, 2018 3pm ? 4pm Brussels (changed) Where: https://global.gotomeeting.com/join/796425741 Calendar: automotive-discussions at lists.linuxfoundation.org Who: * Walt Miner - creator * dcauchy at linuxfoundation.org * automotive-discussions at lists.linuxfoundation.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=N2hibjdnN2tqMnBtNGwzc2J0bXZ2bm92dXNfMjAxODAyMDFUMTQwMDAwWiBhdXRvbW90aXZlLWRpc2N1c3Npb25zQGxpc3RzLmxpbnV4Zm91bmRhdGlvbi5vcmc&tok=NzIjbGludXhmb3VuZGF0aW9uLm9yZ19pMHJzOGFta20wZmxkZTdrcTV1NGI5dGVmNEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tOWU1MzA4OTFkYzBkYzBmODkwMTViZDEyZmZlYjIwN2I0ZjZhZmM1Mw&ctz=Europe/Brussels&hl=en Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account automotive-discussions at lists.linuxfoundation.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3813 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3900 bytes Desc: not available URL: From wminer at linuxfoundation.org Fri Feb 2 18:34:12 2018 From: wminer at linuxfoundation.org (Walt Miner) Date: Fri, 2 Feb 2018 19:34:12 +0100 Subject: [agl-discussions] FYI: Today (1st/Feb) SAT meeting Cancel In-Reply-To: <131438561D29EC4A86762ADA6AE2B11B85330F61@CHN-SV-EXMX03.mchp-main.com> References: <4205384c-0604-fdeb-ac8b-5fd1c8f3c6e5@iot.bzh> <131438561D29EC4A86762ADA6AE2B11B85330F61@CHN-SV-EXMX03.mchp-main.com> Message-ID: Thank you Fulup. I rescheduled the SAT meeting to next Wednesday. Regards, Walt On Thu, Feb 1, 2018 at 3:22 PM, wrote: > Hi Fulup, > > Thanks for notifying! > > Best regards, > Michael > > -----Original Message----- > From: automotive-discussions-bounces at lists.linuxfoundation.org [mailto: > automotive-discussions-bounces at lists.linuxfoundation.org] On Behalf Of > Fulup Ar Foll > Sent: Donnerstag, 1. Februar 2018 15:18 > To: automotive-discussions at lists.linuxfoundation.org > Subject: [agl-discussions] FYI: Today (1st/Feb) SAT meeting Cancel > > FYI, > > Just had Walt on his mobile. > > His trip is delay more than expected and he unfortunately has to cancel > the call. He apologises for the short notice, but he is still lock in a > taxi and cannot open the call while moving. > > Fulup0 > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > -- Walt Miner Engineering Project Manager The Linux Foundation mobile: +1.847.502.7087 Visit us at: automotive.linuxfoundation.org www.linuxfoundation.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.douheret at iot.bzh Sat Feb 3 11:45:06 2018 From: sebastien.douheret at iot.bzh (Sebastien Douheret) Date: Sat, 3 Feb 2018 12:45:06 +0100 Subject: [agl-discussions] Automotive community dinner at FOSDEM 2018 In-Reply-To: References: Message-ID: ?Hi, same restaurant as last year has been booked : Le Delecta [1] . If not already done, please register using Google form link sent by Leon (see email below). Join us at AGL stand (building AW) or directly at restaurant (approximately 7:45 PM / 8:00 PM) Thanks, Sebastien. [1]: http://ledelecta.be/en On 30/01/2018 16:44, Leon Anavi wrote: > Hi, > > Following a discussion about FOSDEM 2018 during the AGL weekly dev call, > I have the pleasure to kindly invite you to the automotive community > dinner on Saturday night, 3 February 2018 in Brussels, Belgium, right > after the first day of FOSDEM. I am sending the invitation to the > mailing lists of AGL, GDP and Tizen. > > If you would like to attend please register before 1 February at: > https://goo.gl/forms/SnZ6T7ZP8Dwrp3Pg2 > > Depending on the number of registered people Jan-Simon and Sebastien > will book a restaurant with enough places and announce further details. > > Thanks, > Leon > -- sebastien.douheret at iot.bzh - www.iot.bzh -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsmoeller at linuxfoundation.org Sat Feb 3 11:51:47 2018 From: jsmoeller at linuxfoundation.org (Jan-Simon Moeller) Date: Sat, 3 Feb 2018 12:51:47 +0100 Subject: [agl-discussions] Automotive community dinner at FOSDEM 2018 In-Reply-To: References: Message-ID: Forwarding to all lists ... Hi, same restaurant as last year has been booked : Le Delecta [1] . If not already done, please register using Google form link sent by Leon (see email below). Join us in front of AW / H building at 7pm or directly at restaurant (approximately 7:45 PM / 8:00 PM)! [1] www.delecta.be Besteht, Jan-Simon Am 30.01.2018 4:44 nachm. schrieb "Leon Anavi" : Hi, Following a discussion about FOSDEM 2018 during the AGL weekly dev call, I have the pleasure to kindly invite you to the automotive community dinner on Saturday night, 3 February 2018 in Brussels, Belgium, right after the first day of FOSDEM. I am sending the invitation to the mailing lists of AGL, GDP and Tizen. If you would like to attend please register before 1 February at: https://goo.gl/forms/SnZ6T7ZP8Dwrp3Pg2 Depending on the number of registered people Jan-Simon and Sebastien will book a restaurant with enough places and announce further details. Thanks, Leon -- Leon Anavi Software Engineer konsulko.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsmoeller at linuxfoundation.org Sat Feb 3 11:53:01 2018 From: jsmoeller at linuxfoundation.org (Jan-Simon Moeller) Date: Sat, 3 Feb 2018 12:53:01 +0100 Subject: [agl-discussions] Automotive community dinner at FOSDEM 2018 In-Reply-To: References: Message-ID: Sri, wrong URL: http://ledelecta.be/en Am 03.02.2018 12:51 nachm. schrieb "Jan-Simon Moeller" < jsmoeller at linuxfoundation.org>: > Forwarding to all lists ... > > > Hi, > > same restaurant as last year has been booked : Le Delecta [1] > . > If not already done, please register using Google form link sent by Leon > (see email below). > > Join us in front of AW / H building at 7pm or directly at restaurant > (approximately 7:45 PM / 8:00 PM)! > > > > > [1] www.delecta.be > > > Besteht, > > Jan-Simon > > Am 30.01.2018 4:44 nachm. schrieb "Leon Anavi" : > > Hi, > > Following a discussion about FOSDEM 2018 during the AGL weekly dev call, > I have the pleasure to kindly invite you to the automotive community > dinner on Saturday night, 3 February 2018 in Brussels, Belgium, right > after the first day of FOSDEM. I am sending the invitation to the > mailing lists of AGL, GDP and Tizen. > > If you would like to attend please register before 1 February at: > https://goo.gl/forms/SnZ6T7ZP8Dwrp3Pg2 > > Depending on the number of registered people Jan-Simon and Sebastien > will book a restaurant with enough places and announce further details. > > Thanks, > Leon > > -- > Leon Anavi > Software Engineer > konsulko.com > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsmoeller at linuxfoundation.org Sat Feb 3 17:10:07 2018 From: jsmoeller at linuxfoundation.org (Jan-Simon Moeller) Date: Sat, 3 Feb 2018 18:10:07 +0100 Subject: [agl-discussions] Automotive community dinner at FOSDEM 2018 In-Reply-To: References: Message-ID: Here is the map link. 19:30 / 7:30 p.m. Delecta Rue Lannoy 5, 1050 Ixelles, Belgien +32 2 644 19 49 https://goo.gl/maps/cDQXLDgBKNP2 Am 03.02.2018 12:53 nachm. schrieb "Jan-Simon Moeller" < jsmoeller at linuxfoundation.org>: > Sri, wrong URL: > http://ledelecta.be/en > > > > Am 03.02.2018 12:51 nachm. schrieb "Jan-Simon Moeller" < > jsmoeller at linuxfoundation.org>: > >> Forwarding to all lists ... >> >> >> Hi, >> >> same restaurant as last year has been booked : Le Delecta [1] >> . >> If not already done, please register using Google form link sent by Leon >> (see email below). >> >> Join us in front of AW / H building at 7pm or directly at restaurant >> (approximately 7:45 PM / 8:00 PM)! >> >> >> >> >> [1] www.delecta.be >> >> >> Besteht, >> >> Jan-Simon >> >> Am 30.01.2018 4:44 nachm. schrieb "Leon Anavi" : >> >> Hi, >> >> Following a discussion about FOSDEM 2018 during the AGL weekly dev call, >> I have the pleasure to kindly invite you to the automotive community >> dinner on Saturday night, 3 February 2018 in Brussels, Belgium, right >> after the first day of FOSDEM. I am sending the invitation to the >> mailing lists of AGL, GDP and Tizen. >> >> If you would like to attend please register before 1 February at: >> https://goo.gl/forms/SnZ6T7ZP8Dwrp3Pg2 >> >> Depending on the number of registered people Jan-Simon and Sebastien >> will book a restaurant with enough places and announce further details. >> >> Thanks, >> Leon >> >> -- >> Leon Anavi >> Software Engineer >> konsulko.com >> >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From rday at linuxfoundation.org Sat Feb 3 17:26:56 2018 From: rday at linuxfoundation.org (Ryan F Day) Date: Sat, 3 Feb 2018 09:26:56 -0800 Subject: [agl-discussions] [it-infrastructure-alerts] AGL maintenance 2018-02-03 @ 18:00 - 20:00 UTC In-Reply-To: References: Message-ID: <25f4d4ab-bdc1-4ab1-bfcb-1888bafd7aaa@linuxfoundation.org> This maintenance will be starting soon. On 01/19/2018 11:54 AM, Ryan F Day wrote: > What: The Linux Foundation will be performing needed maintenance on > AGL systems > > When: Saturday, February 3, 2018 @ 10:00 - 12:00 PST (18:00 - 20:00 UTC) > > Why: Security updates are available for all AGL systems > > Impact: During the maintenance window, AGL systems will be upgraded and > rebooted. This will cause brief outages for Jenkins, Jenkins sandbox, > Gerrit, Jira, KernelCI, the download server, and the firewall. Jenkins > will be put in shutdown mode about an hour prior to the maintenance > window to prevent job failures. > > Notices will be posted here before and after the maintenance. > > > > > > > > > > > > > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From rday at linuxfoundation.org Sat Feb 3 18:00:17 2018 From: rday at linuxfoundation.org (Ryan F Day) Date: Sat, 3 Feb 2018 10:00:17 -0800 Subject: [agl-discussions] [it-infrastructure-alerts] AGL maintenance 2018-02-03 @ 18:00 - 20:00 UTC In-Reply-To: References: Message-ID: <6a2fdcf5-f165-4b86-994f-18698e2ced89@linuxfoundation.org> This maintenance is starting now. On 01/19/2018 11:54 AM, Ryan F Day wrote: > What: The Linux Foundation will be performing needed maintenance on > AGL systems > > When: Saturday, February 3, 2018 @ 10:00 - 12:00 PST (18:00 - 20:00 UTC) > > Why: Security updates are available for all AGL systems > > Impact: During the maintenance window, AGL systems will be upgraded and > rebooted. This will cause brief outages for Jenkins, Jenkins sandbox, > Gerrit, Jira, KernelCI, the download server, and the firewall. Jenkins > will be put in shutdown mode about an hour prior to the maintenance > window to prevent job failures. > > Notices will be posted here before and after the maintenance. > > > > > > > > > > > > > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From rday at linuxfoundation.org Sat Feb 3 18:44:57 2018 From: rday at linuxfoundation.org (Ryan F Day) Date: Sat, 3 Feb 2018 10:44:57 -0800 Subject: [agl-discussions] [it-infrastructure-alerts] AGL maintenance 2018-02-03 @ 18:00 - 20:00 UTC In-Reply-To: References: Message-ID: This maintenance is now complete. On 01/19/2018 11:54 AM, Ryan F Day wrote: > What: The Linux Foundation will be performing needed maintenance on > AGL systems > > When: Saturday, February 3, 2018 @ 10:00 - 12:00 PST (18:00 - 20:00 UTC) > > Why: Security updates are available for all AGL systems > > Impact: During the maintenance window, AGL systems will be upgraded and > rebooted. This will cause brief outages for Jenkins, Jenkins sandbox, > Gerrit, Jira, KernelCI, the download server, and the firewall. Jenkins > will be put in shutdown mode about an hour prior to the maintenance > window to prevent job failures. > > Notices will be posted here before and after the maintenance. > > > > > > > > > > > > > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From gengdongjiu at huawei.com Mon Feb 5 04:16:53 2018 From: gengdongjiu at huawei.com (gengdongjiu) Date: Mon, 5 Feb 2018 04:16:53 +0000 Subject: [agl-discussions] =?utf-8?b?562U5aSNOiAgZnVuY3Rpb25hbCBzYWZldHkg?= =?utf-8?q?and_hard_real-time_in_the_kernel_for_autonomous_driving?= In-Reply-To: References: <0184EA26B2509940AA629AE1405DD7F201AA5B48@DGGEMA503-MBS.china.huawei.com> <0184EA26B2509940AA629AE1405DD7F201AABA1B@DGGEMA503-MBS.china.huawei.com> <0184EA26B2509940AA629AE1405DD7F201AAF00B@DGGEMA503-MBS.china.huawei.com> Message-ID: <0184EA26B2509940AA629AE1405DD7F201AC5969@DGGEMA503-MBS.china.huawei.com> Dear Stefano?Tiejun Thanks for these points, we will check it. -----????----- ???: Stefano Stabellini [mailto:sstabellini at kernel.org] ????: 2018?2?1? 7:46 ???: Tiejun Chen ??: gengdongjiu ; Michele Paolino ; liubo (CU) ; automotive-discussions at lists.linuxfoundation.org; Linqiangmin ; Dingtianhong ; Dengwenbin (Arthur, Turing) ; Liushi (Ivan) ??: Re: [agl-discussions] functional safety and hard real-time in the kernel for autonomous driving Tiejun has good points. In my experience with the Xen hypervisor, people that are using it in environments with real time constraints usually configure it so that: - a real time scheduler is used to schedule the workloads with real time constraints (for example, add sched=arinc653 on the xen command line) - or, better, workloads with real time constrains have their vcpus statically assigned to pcpus - there is no hypervisor paging: all the memory of the VM is allocated upfront (of course ballooning is still possible) - there are no PV drivers, hardware devices are statically assigned to the VM with real time constraints (this requires an IOMMU) - minimize interrupt latency: physical interrupts should be delivered to the pcpu running the vcpu that needs to receive the corresponding virtual interrupts. This is important. It is done by default by Xen on ARM. This way, the scheduler overhead is null, the IO and memory overhead is down to stage2 translations in hardware, and the interrupt latency overhead is 5us (measured on a Xilinx Zynq MPSoC). This is usually within the workload's real time constraints. I hope you find this useful. Cheers, Stefano On Wed, 31 Jan 2018, Tiejun Chen wrote: > Gengdong, > > ? > > What I?m trying to say is that we should understand what these challenges are faced with RT virtualization. > > ? > > With hypervisor, > > ? > > #1. CPU resource > > ? > > we can see two levels scheduling: > > * Hypervisor scheduler: vCPU over pCPU > * Guest OS scheduler: RT application over CPU (vCPU) > > ? > > #2. Memory resource. Again, guest OS memory allocation vs hypervisor memory allocation. What if hypervisor cannot allocate memory to GOS at one given time? > > ? > > #3. Timer accuracy > > #4. Interrupt dispatch > > #5. ? > > ? > > In terms of #1 and #2, I think the way of partitioning CPU/Memory > resources might be a good approach. Certainly, besides this, there are a lot of solutions we can do. I think you can find more papers via Google. > > ? > > Thanks > > Tiejun > > ? > > From: gengdongjiu [mailto:gengdongjiu at huawei.com] > Sent: Tuesday, January 30, 2018 4:01 PM > To: Tiejun Chen ; Michele Paolino > > Cc: automotive-discussions at lists.linuxfoundation.org; Linqiangmin > ; Liushi (Ivan) ; liubo > (CU) ; Dingtianhong ; > Dengwenbin (Arthur, Turing) > Subject: ??: [agl-discussions] functional safety and hard real-time in > the kernel for autonomous driving > > ? > > Tiejun? > > ???? > > Thanks for this clarification. > > ???? Yes,? the ARMv8(Cortex-A53,A57,A72) support HW virtualization > extensions, my platform even support the armv8.1 VHE(VIRTUALIZATION HOST EXTENSIONS[1]), ?so your main suggestion is isolating some resources including CPU/Memory, as shown [2], right? > > If so, I will checked it in detailed about it. By the way, could you share more materials about the real-time virtualization? > > ????? > > [1]: https://lwn.net/Articles/650524/ > > [2]: > https://events.static.linuxfound.org/sites/events/files/slides/LinuxCo > nNA-2015-Jailhouse_0.pdf > > ? > > ???: Tiejun Chen [mailto:tiejunc at vmware.com] > ????: 2018?1?30? 10:08 > ???: gengdongjiu ; Michele Paolino > > ??: automotive-discussions at lists.linuxfoundation.org; Linqiangmin > ; Liushi (Ivan) ; liubo > (CU) ; Dingtianhong ; > Dengwenbin (Arthur, Turing) > ??: RE: [agl-discussions] functional safety and hard real-time in the > kernel for autonomous driving > > ? > > Gengdong, > > ? > > Sorry, what I said might get you confused. > > ? > > It?s not such a classic nested virtualization like hypervisor A running over hypervisor B. But ARMv8(Cortex-A53,A57,A72) should support HW virtualization extensions, IIRC. > Simple speaking, the partitioning hypervisor means you can isolate some resources including CPU/Memory, and then you can run any real-time workload easily. > > ? > > Generally, real-time virtualization is a topic about how to run > real-time workload after introducing virtualization. You know, > hypervisor has no any knowledge about RT workload within VM, and just schedules RT workload like such a black box. This is a key issue to RT Virtualization. Besides, we have to consider more like memory, timer, lock-holder preemption problem and so on. > > ? > > Thanks > > Tiejun > > ? > > From: gengdongjiu [mailto:gengdongjiu at huawei.com] > Sent: Monday, January 29, 2018 8:43 PM > To: Tiejun Chen ; Michele Paolino > > Cc: automotive-discussions at lists.linuxfoundation.org; Linqiangmin > ; Liushi (Ivan) ; liubo > (CU) ; Dingtianhong ; > Dengwenbin (Arthur, Turing) > Subject: ??: [agl-discussions] functional safety and hard real-time in > the kernel for autonomous driving > > ? > > Tiejun, > > ???? Sorry for my late response and thank you very much for your > detailed answer to me, appreciate that, > > I am interested and curious how the Real Time Virtualization make OS real-time. > > ? > > https://events.static.linuxfound.org/sites/events/files/slides/LinuxCo > nNA-2015-Jailhouse_0.pdf > > ? > > I see you mentioned Jailhouse, ?My platform CPU is armv8 which does > not support nested virtualization, May be Jailhouse+ KVM/Xen need ? > nested virtualization > > Whether Jailhouse already support armv8 CPU without nested virtualization? > > Is the ?Real Time Virtualization? that you mentioned is based on Jailhouse? > > ? > > ? > > ???: Tiejun Chen [mailto:tiejunc at vmware.com] > ????: 2018?1?27? 7:47 > ???: gengdongjiu ; Michele Paolino > > ??: automotive-discussions at lists.linuxfoundation.org > ??: RE: [agl-discussions] functional safety and hard real-time in the > kernel for autonomous driving > > ? > > Real Time Virtualization is my favorite topic, if you?re interested in > this we can talk more ? > > ? > > Thanks > > Tiejun > > ? > > From: automotive-discussions-bounces at lists.linuxfoundation.org > [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On > Behalf Of Tiejun Chen > Sent: Saturday, January 27, 2018 7:41 AM > To: gengdongjiu ; Michele Paolino > > Cc: automotive-discussions at lists.linuxfoundation.org > Subject: Re: [agl-discussions] functional safety and hard real-time in > the kernel for autonomous driving > > ? > > Gengdong, > > ? > > I think you want to first understand why we need to put virtualization into embedded system. > > ? > > Our embedded systems or later face ?some challenges: > > ? > > # How can we further enhance security? > > # How can system performance be increased while reducing cost as possible? > > # How can any existing functions across various devices or new devices be supported easily? > > # How can we consolidate either hardware like ECU or software? > > # How can we enable applications based on different certifications? > > # How can we bring new novel technologies to edge side? Like edge computing. > > ? > > ? > > It should have more but I hope these questions are good start of > helping you understand why we probably need virtualization. ?VM > decreases performance more or less. But there are some approaches > there. ?For example, you can take a look at the partitioning > hypervisor like, > > https://events.static.linuxfound.org/sites/events/files/slides/LinuxCo > nNA-2015-Jailhouse_0.pdf > > ? > > ? > > ?We are doing the autonomous driving, you know the safety is important, do you have any suggestion to make Linux reach hard real-time(RT)?? > > ? > > Preempt-RT is not the classic hard real time Linux. But ?PREEMPT_RT is > a ?hardening? of Linux. It?s far from mathematically provable, but if > there?s an unbounded latency that?s in PREEMPT_RT, we consider that a > bug, and work hard to fix it. Our goal is to make Linux as hard as > possible. ? That?s probably what they meant about Linux not being able to handle real-time, as the mainline Linux kernel is filled with unbounded latencies. With unbounded latencies comes non-deterministic behavior. Mainline Linux can do things really fast most of the time, but every so often, you get that outlier that could cause a large delay. Ever see your mouse jitter? With a properly setup PREEMPT_RT kernel, your desktop experience can be made much smoother.? > > ? > > Thanks > > Tiejun > > ? > > ? > > From: automotive-discussions-bounces at lists.linuxfoundation.org > [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On > Behalf Of gengdongjiu > Sent: Friday, January 26, 2018 10:47 PM > To: Michele Paolino > Cc: automotive-discussions at lists.linuxfoundation.org > Subject: Re: [agl-discussions] functional safety and hard real-time in > the kernel for autonomous driving > > ? > > Hi Michele, > > ? > > ?? Thank you very much for your mail and reply, I have attend your conference, but my headphone has some problem(sorry for that). > > ? > > [1]: > https://events.static.linuxfound.org/sites/events/files/slides/als15_p > aolino.pdf > [2]: > https://schd.ws/hosted_files/aglammeu17/33/AGL_EGVIRT_VOSYS_Paolino_pl > ans-objectives-2018.pdf > > ? > > I have checked the EG Virtualization, > > For [1], it based on trust zone, it uses the real-time OS as the security OS to run real-time application, and use Linux as non-security OS.to run non real-time application. > > For such design, I do not know what?s the reason to use KVM.? The > real-time OS which is not a VM is not based on KVM > > ? > > For [2], if the real-time OS is based on KVM, maybe the application > performance will drop because it is a VM. I do not know how it reach > the real-time, > > if possible, could you share me more introduction materials for it? such as the ?virtualization white paper?. Thank you so much. > > ? > > We are doing the autonomous driving, you know the safety is important, do you have any suggestion to make Linux reach hard real-time(RT)? > > ? > > ? > > ? > > ???: Michele Paolino [mailto:m.paolino at virtualopensystems.com] > ????: 2018?1?25? 21:11 > ???: gengdongjiu > ??: automotive-discussions at lists.linuxfoundation.org > ??: Re: functional safety and hard real-time in the kernel for > autonomous driving > > ? > > Hello Dongjiu Geng, > > it is true that Linux is not certified nor hard real time (RT), and > there is no solution to make AGL a hard real time OS today. I know > that Linux Foundation is exploring the possibility to make Linux both certifiable and RT. However, if this will be addressed (and it does not depend only on technical matters) it will not happen in the short term and I imagine the result as something different from Linux as we know it today (to address certification only a small subset of functions can be targeted). > > For this reason the way I see the AGL support for autonomous driving is through virtualization. > > ? > > In fact, virtualization splits the problem in smaller chunks and opens the door to the coexistence of multiple AGL profiles with a certified RT OS which can be: > > - Linux based, eventually in the long term > > - Non Linux based, already in the short-mid term, where existing open > source hard real time operating systems can be enhanced with > certification > > ? > > This of course means that the hypervisor has to be certified. However, > being much simpler/smaller than a complete OS, (non type-2) > hypervisors are in general easier than Linux to certify. Additionally, > in order to enable communication between these different AGL profiles and virtualized operating systems, there is a need to specify and standardize common communication interfaces and mechanisms. Lastly, another point which makes virtualization important for ADAS in AGL is that it gives the possibility to third party legacy/proprietary solutions to be part of the system, thus widening the possible applications of AGL. > > ? > > All the above are topics we discuss in the VIRT expert group. We have > biweekly meetings and during the the next one (scheduled for tomorrow), we will discuss about the community virtualization white paper and the 2018 roadmap. I invite you and all the people interested in these matters to join! > > ? > > Regards, > > ? > > ? > > On Thu, Jan 25, 2018 at 6:02 AM, gengdongjiu wrote: > > ?Hi paolino > ? ?I am Dongjiu Geng from huawei's company, recently I am investigating the real-time kernel solution for autonomous driving, > ?and see AGL(Automotive Grade Linux) has plan to support autonomous driving, if AGL supports autonomous driving, the Linux > ?kernel should be hard real-time, but I see the AGL kernel only applied some PREEMPT_RT patches, not do much others. PREEMPT_RT > ?patches can only make kernel soft real-time, not hard real-time. Have you any solution to make AGL reach the hard real-time? > ?By the way, Linux as the autonomous driving OS can not pass the ISO 26262 certification, what do you think about that? > > ? > > -- > > Michele Paolino > Virtualization Architect > Virtual Open Systems > > ? > > > From Oleksandr_Grytsov at epam.com Mon Feb 5 10:48:34 2018 From: Oleksandr_Grytsov at epam.com (Oleksandr Grytsov) Date: Mon, 5 Feb 2018 10:48:34 +0000 Subject: [agl-discussions] Xen integration In-Reply-To: References: , Message-ID: Hi Fulup, Thanks for your explanation. I will check 4A and how to integrate our backend with it. I personally will not attend AMM in Japan but my colleague Artem Mygaiev will. So, it would be good to discuss. From: Fulup Ar Foll Sent: Friday, February 2, 2018 12:40:17 PM To: Oleksandr Grytsov; automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] Xen integration ? Oleksandr, For audio with Eel & 4A the audio policy while technical possible, some real work needs to be done before moving to a production ready system. For a POC accessing audio policy from an other user domain should be relativity simple. 4A high level API is exposed through a standard AGL binder/binding and if you enable TCP on the audio binder you can request it from outside AGL. This behing said two things remains to be done: ? - 4A handle signalling but not the stream. 4A will return you with a sound URI, potentially an ALSA PCM or something more specific to your virtualisation environment. ? - AGL security model relies on SMACK and API protection does not cross operating systems boundaries. While be have as project to extend API protection to OpenID-connect for vehicule to cloud, as today nothing as been decided to extend AGL application framework capabilities to a virtualized environment. I thing this would be a nice discution topic for next AMM in Japan, will you attend ? Fulup On 31/01/18 15:41, Oleksandr Grytsov wrote: > Hi All, > > I'm from EPAM company? and we are working on integration Xen for automotive solutions. Recently we did some demo running Xen with AGL and Android on same board. From HW point of view it is Renesas board with two displays. One display is dedicated for AGL HomeScreen second one for Android. Basically AGL related tasks were to integrate our Display and Sound backends.? Display backend is a user space application with multiple wayland surfaces. Also Sound backend is a user space application with multiple pulse audio streams. For Sound backend we did nothing special as it works in AGL dab branch without interaction with AudioManager or adjusting any audio policies. But for Display beckend we did some tricks to make it works. > > Now I'm looking for proper backends integration. And have following questions: > > Display: > > * Multiple display support: I see some issue recently created to support it. Is there any draft spec? > * Multiple surface support: is there any possibility to support one application with multiple surfaces? If not is there plan to support it? > * Is it possible to work with WindowManager and HomeScreen if the application is not AGL widget but system daemon, for example? > > Sound: > > * What is proper way to integrate the application with AudioManager? > * Shell this application be AGL widget or it could be any user space application? > > Thanks. >??? >?? Oleksandr Grytsov >?? Lead Software Engineer >???? >?? Office:?+380? 44 390 5457 x?66834? ? Cell:?+380? 67 751 0148?? Email:?oleksandr_grytsov at epam.com >?? Kyiv,?Ukraine?(GMT+3)?? epam.com >??? > CONFIDENTIALITY CAUTION AND DISCLAIMER > This message is intended only for the use of the individual(s) or entity(ies) to which it is addressed and contains information that is legally privileged? and confidential. If you are not the intended recipient, or the person responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. All? unintended recipients are obliged to delete this message and destroy any printed copies. > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions automotive-discussions Info Page - Linux Foundation lists.linuxfoundation.org This list is the primary community list for the Automotive Grade Linux (AGL) Collaboration Project. Everyone is welcome to subscribe to this list and participate in ... > From sebastien.douheret at iot.bzh Mon Feb 5 15:14:43 2018 From: sebastien.douheret at iot.bzh (Sebastien Douheret) Date: Mon, 5 Feb 2018 16:14:43 +0100 Subject: [agl-discussions] Fosdem 2018 Message-ID: <738cab80-1d1a-ed06-90bf-4c49ca844756@iot.bzh> Here a photo of 7 guys of IoT.bzh team at Fosdem: https://www.linkedin.com/feed/update/urn:li:activity:6365937877095841793 Fosdem 2018 was a really good year : crowded and many people know AGL or had already hear about. Many thanks to all those who participated to build and setup the demo for CES and then for Fosdem. BR, Sebastien. -- sebastien.douheret at iot.bzh -www.iot.bzh -------------- next part -------------- An HTML attachment was scrubbed... URL: From jung at drimaes.com Tue Feb 6 04:33:52 2018 From: jung at drimaes.com (=?UTF-8?B?7KCV7JiB66y4?=) Date: Tue, 6 Feb 2018 13:33:52 +0900 Subject: [agl-discussions] QEMU resolution isuue. Message-ID: Hi All, Now I,m testing AGL 5.0 on QEMU. I have a problem on my testing. QEMU resolution is not currects like attachments[attach1]. So, I tried 2 way. First, I modified mode to 1080x1920 weston.ini files. ( weston.ivi dir : /etc/xdg/weston/weston.ini ) But, It was not still working well. Second, I added transform=270 to weston.ini files. ( weston.ivi dir : /etc/xdg/weston/weston.ini ) resolution is little bit OK like attatchments[attatch2], but mouse point did not operate normally. Please help me in this regard. Thanks & Regards, Josh. ( reference site : http://docs.automotivelinux.org/docs/getting_started/en/dev/reference/homescreen/ ) ( refetence site : https://lists.linuxfoundation.org/pipermail/automotive-discussions/2017-January/003335.html ) -- *Jung Young Moon DrimAES Inc.* *Address* ?? ??? ???? 273 ???????2? 803? ????? *Mobile* 010-4907-2117 *Mail* jung at drimaes.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: [attatch2]qemu_transform_270.png Type: image/png Size: 960197 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: [attach1]agl_on_qemu_resolution.png Type: image/png Size: 543440 bytes Desc: not available URL: From matt.ranostay at konsulko.com Tue Feb 6 04:44:35 2018 From: matt.ranostay at konsulko.com (Matt Ranostay) Date: Mon, 5 Feb 2018 20:44:35 -0800 Subject: [agl-discussions] QEMU resolution isuue. In-Reply-To: References: Message-ID: On Mon, Feb 5, 2018 at 8:33 PM, ??? wrote: > Hi All, > > Now I,m testing AGL 5.0 on QEMU. > > I have a problem on my testing. > QEMU resolution is not currects like attachments[attach1]. > > > So, I tried 2 way. > First, I modified mode to 1080x1920 weston.ini files. ( weston.ivi dir : > /etc/xdg/weston/weston.ini ) > But, It was not still working well. > > Second, I added transform=270 to weston.ini files. ( weston.ivi dir : > /etc/xdg/weston/weston.ini ) > resolution is little bit OK like attatchments[attatch2], but mouse point did > not operate normally. > > > Please help me in this regard. > You need to pass "-show-cursor" on your qemu command line. - Matt > > Thanks & Regards, > Josh. > > > ( reference site : > http://docs.automotivelinux.org/docs/getting_started/en/dev/reference/homescreen/ > ) > ( refetence site : > https://lists.linuxfoundation.org/pipermail/automotive-discussions/2017-January/003335.html > ) > > > -- > Jung Young Moon DrimAES Inc. > > Address ?? ??? ???? 273 ???????2? 803? ????? > Mobile 010-4907-2117 > Mail jung at drimaes.com > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > From jung at drimaes.com Tue Feb 6 04:51:12 2018 From: jung at drimaes.com (=?UTF-8?B?7KCV7JiB66y4?=) Date: Tue, 6 Feb 2018 13:51:12 +0900 Subject: [agl-discussions] QEMU resolution isuue. In-Reply-To: References: Message-ID: Hi Matt, Thanks your reply. I used "-show-cursor" command like below. # sudo qemu-system-x86_64 -enable-kvm -m 2048 -hda agl-demo-platform-crosssdk-qemux86-64-20180107080143.v qemu64,+ssse3,+sse4.1,+sse4.2,+popcnt -vga std -show-cursor -device virtio-rng-pci -serial mon:stdio -serial null -soundhw hda -net nic,vlan=0 -net user,hostfwd=tcp::2222-:22 -netdev bridge,br=br0,id=net0 -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:59 2018-02-06 13:44 GMT+09:00 Matt Ranostay : > On Mon, Feb 5, 2018 at 8:33 PM, ??? wrote: > > Hi All, > > > > Now I,m testing AGL 5.0 on QEMU. > > > > I have a problem on my testing. > > QEMU resolution is not currects like attachments[attach1]. > > > > > > So, I tried 2 way. > > First, I modified mode to 1080x1920 weston.ini files. ( weston.ivi dir : > > /etc/xdg/weston/weston.ini ) > > But, It was not still working well. > > > > Second, I added transform=270 to weston.ini files. ( weston.ivi dir : > > /etc/xdg/weston/weston.ini ) > > resolution is little bit OK like attatchments[attatch2], but mouse point > did > > not operate normally. > > > > > > Please help me in this regard. > > > > You need to pass "-show-cursor" on your qemu command line. > > - Matt > > > > > > Thanks & Regards, > > Josh. > > > > > > ( reference site : > > http://docs.automotivelinux.org/docs/getting_started/en/ > dev/reference/homescreen/ > > ) > > ( refetence site : > > https://lists.linuxfoundation.org/pipermail/automotive- > discussions/2017-January/003335.html > > ) > > > > > > -- > > Jung Young Moon DrimAES Inc. > > > > Address ?? ??? ???? 273 ???????2? 803? ????? > > Mobile 010-4907-2117 > > Mail jung at drimaes.com > > > > _______________________________________________ > > automotive-discussions mailing list > > automotive-discussions at lists.linuxfoundation.org > > https://lists.linuxfoundation.org/mailman/listinfo/ > automotive-discussions > > > -- *Jung Young Moon DrimAES Inc.* *Address* ?? ??? ???? 273 ???????2? 803? ????? *Mobile* 010-4907-2117 *Mail* jung at drimaes.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From tanikawa.tadao at jp.panasonic.com Tue Feb 6 07:14:27 2018 From: tanikawa.tadao at jp.panasonic.com (tanikawa.tadao at jp.panasonic.com) Date: Tue, 6 Feb 2018 07:14:27 +0000 Subject: [agl-discussions] QEMU resolution isuue. In-Reply-To: References: Message-ID: <182eb92ecf844e23898c4b2a8cad13a5@JPA000SECMN07.palet.jp.panasonic.com> Hi, You might need ?-vga virtio? and ?-usbdevice tablet?. You can also use ?runqemu? if you built your own yocto/agl environment. Here is my instructions to run QEMU. $ cd $ source poky/oe-init-build-env $ runqemu tmp/deploy/images/qemux86-64/agl-demo-platform-qemux86-64.qemuboot.conf kvm serial For your reference, following is the part of log of runqemu.. runqemu - INFO - Running tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin//qemu-system-x86_64 -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:02 -netdev tap,id=net0,ifname=tap0,script=no,downscript=no -drive file=tmp/deploy/images/qemux86-64/agl-demo-platform-qemux86-64-20180206055341.rootfs.ext4,if=virtio,format=raw -show-cursor -usb -usbdevice tablet -device virtio-rng-pci -vga virtio -machine q35 -cpu kvm64 -cpu qemu64,+ssse3,+sse4.1,+sse4.2,+popcnt -enable-kvm -m 2048 -serial mon:vc -serial mon:stdio -serial null -kernel tmp/deploy/images/qemux86-64/bzImage--4.10.17+git0+40ee48ac09_c1d8c4408b-r0-qemux86-64-20171214150211.bin -append 'root=/dev/vda rw highres=off console=ttyS0 mem=2048M ip=192.168.7.2::192.168.7.1:255.255.255.0 vga=0 uvesafb.mode_option=1024x768-32 oprofile.timer=1 uvesafb.task_timeout=-1 ' Regards, Tadao Tanikawa From: automotive-discussions-bounces at lists.linuxfoundation.org [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On Behalf Of ??? Sent: Tuesday, February 06, 2018 1:51 PM To: Matt Ranostay Cc: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] QEMU resolution isuue. Hi Matt, Thanks your reply. I used "-show-cursor" command like below. # sudo qemu-system-x86_64 -enable-kvm -m 2048 -hda agl-demo-platform-crosssdk-qemux86-64-20180107080143.v qemu64,+ssse3,+sse4.1,+sse4.2,+popcnt -vga std -show-cursor -device virtio-rng-pci -serial mon:stdio -serial null -soundhw hda -net nic,vlan=0 -net user,hostfwd=tcp::2222-:22 -netdev bridge,br=br0,id=net0 -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:59 2018-02-06 13:44 GMT+09:00 Matt Ranostay >: On Mon, Feb 5, 2018 at 8:33 PM, ??? > wrote: > Hi All, > > Now I,m testing AGL 5.0 on QEMU. > > I have a problem on my testing. > QEMU resolution is not currects like attachments[attach1]. > > > So, I tried 2 way. > First, I modified mode to 1080x1920 weston.ini files. ( weston.ivi dir : > /etc/xdg/weston/weston.ini ) > But, It was not still working well. > > Second, I added transform=270 to weston.ini files. ( weston.ivi dir : > /etc/xdg/weston/weston.ini ) > resolution is little bit OK like attatchments[attatch2], but mouse point did > not operate normally. > > > Please help me in this regard. > You need to pass "-show-cursor" on your qemu command line. - Matt > > Thanks & Regards, > Josh. > > > ( reference site : > http://docs.automotivelinux.org/docs/getting_started/en/dev/reference/homescreen/ > ) > ( refetence site : > https://lists.linuxfoundation.org/pipermail/automotive-discussions/2017-January/003335.html > ) > > > -- > Jung Young Moon DrimAES Inc. > > Address ?? ??? ???? 273 ???????2? 803? ????? > Mobile 010-4907-2117 > Mail jung at drimaes.com > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > -- Jung Young Moon DrimAES Inc. Address ?? ??? ???? 273 ???????2? 803? ????? Mobile 010-4907-2117 Mail jung at drimaes.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dominig.arfoll at fridu.net Tue Feb 6 11:14:07 2018 From: dominig.arfoll at fridu.net (Dominig ar Foll (Intel Open Source)) Date: Tue, 6 Feb 2018 12:14:07 +0100 Subject: [agl-discussions] AGL netboot NDB client configuration in initrd Message-ID: <33b876d0-b067-8a28-1bab-fc4071a1e8da@fridu.net> An HTML attachment was scrubbed... URL: From dominig.arfoll at fridu.net Tue Feb 6 15:42:57 2018 From: dominig.arfoll at fridu.net (Dominig ar Foll (Intel Open Source)) Date: Tue, 6 Feb 2018 16:42:57 +0100 Subject: [agl-discussions] AGL netboot NDB client configuration in initrd In-Reply-To: <33b876d0-b067-8a28-1bab-fc4071a1e8da@fridu.net> References: <33b876d0-b067-8a28-1bab-fc4071a1e8da@fridu.net> Message-ID: <1d8097f9-c48d-abb4-0148-f129c1a3fb9a@fridu.net> An HTML attachment was scrubbed... URL: From jsmoeller at linuxfoundation.org Tue Feb 6 20:27:08 2018 From: jsmoeller at linuxfoundation.org (Jan-Simon =?ISO-8859-1?Q?M=F6ller?=) Date: Tue, 06 Feb 2018 21:27:08 +0100 Subject: [agl-discussions] AGL netboot NDB client configuration in initrd In-Reply-To: <1d8097f9-c48d-abb4-0148-f129c1a3fb9a@fridu.net> References: <33b876d0-b067-8a28-1bab-fc4071a1e8da@fridu.net> <1d8097f9-c48d-abb4-0148-f129c1a3fb9a@fridu.net> Message-ID: <47436827.FDvlNaYZ9c@elrond> Hi Dominig, Here are the answers inline: Am Dienstag, 6. Februar 2018, 16:42:57 CET schrieb Dominig ar Foll (Intel Open Source): > Hello, > > I have found an init script that should do the magic but is does NOT. > Could someone pass me a working set of configuration files: > - ndb server xnbd-server: xnbd-server --logpath /tmp/xnbd.log --daemon \ --target --lport 12345 /path/to/filesystem/image.ext4 e.g.: xnbd-server --logpath /tmp/xnbd.log.55931 --daemon --target --lport 55931 \ /var/lib/lava/dispatcher/tmp/5256/agl-image-ivi-crosssdk-m3ulcb.ext4 linux cmdline: add: nbd.server= nbd.port= e.g.: setenv nbdkbootargs ' ip=dhcp nbd.server=192.168.111.1 nbd.port=55931 root=/ dev/ram0 ramdisk_size=16384 rootdelay=7 rw ip=dhcp' HTH, Jan-Simon > - linux command line > > Thanks. > Dominig > > On 06/02/2018 12:14, Dominig ar Foll (Intel Open Source) wrote: > Hello, > > I am reactivating the netboot for Intel. pxe and grub2 collaborate well > enough to get my kernel and initrd loaded and started. I can see that the > initnetbootramfs provide the ndb client, but I would be interesting by an > example of a working config. I do not understand what starts the ndb > client. The only systemd target in /etc is a broken link. > > Hints are welcome. > Dominig ar Foll > Senior Software Architect > Intel Open Source Technology Centre From srinath.duraisamy at intel.com Wed Feb 7 04:59:25 2018 From: srinath.duraisamy at intel.com (Duraisamy, Srinath) Date: Wed, 7 Feb 2018 04:59:25 +0000 Subject: [agl-discussions] Reg; USB GPS receiver Message-ID: Hi, I am building AGL for Intel platforms. We would like to demo with Navigation app working. We are planning to get a USB GPS receiver, any recommendations or a USB GPS receiver ?? And does AGL navigation app supports US region ?? Thanks in advance. Regards Srinath -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt.ranostay at konsulko.com Wed Feb 7 06:03:07 2018 From: matt.ranostay at konsulko.com (Matt Ranostay) Date: Tue, 6 Feb 2018 22:03:07 -0800 Subject: [agl-discussions] Reg; USB GPS receiver In-Reply-To: References: Message-ID: On Tue, Feb 6, 2018 at 8:59 PM, Duraisamy, Srinath wrote: > Hi, > > > > I am building AGL for Intel platforms. We would like to demo with Navigation > app working. > > > > We are planning to get a USB GPS receiver, any recommendations or a USB GPS > receiver ?? Anything U-Blox should work out of the box with gpsd and the agl-service-gps binding. > > And does AGL navigation app supports US region ?? > Yes but the default navigation application doesn't use the GPS binding. You have to switch to the navigation-demo package > > > Thanks in advance. > > Regards > > Srinath > > > > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > From tmatsuzawa at xevo.com Wed Feb 7 07:21:23 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Wed, 7 Feb 2018 07:21:23 +0000 Subject: [agl-discussions] haptic touch panel. Message-ID: I can see an example deisgn of haptic feedback touch panel: http://www.ti.com/lit/ug/tidu968/tidu968.pdf It uses DRV2667 chip to drive piezo actuators which are attached to a WVGA touch panel. On the document how-to DIY information is available, but it is not available as kit to purchse. This is giving feedback by actuator vibration, actuators are controlled by I2C signals from the host. I can see hobbiest I2C breakout board for DRV2667 is available (they sell this wit piezo actuators as set), so it may not be too difficult to make up something to give touch vibration on panel. (Since AGL uses Full HD palnel, you may need multiples of actuators?) https://hackaday.io/project/3086-piezo-haptic-flex-module I think this might be very primitive demo. (Not really sure - since I have not tried it yet. Perhaps choice of waveform and number of actuators may give you good result.) Alternative (not necessarily the choice is binary) option might be that going with mor professional and high-quality devices, maybe collaborating with special device manufactureres. There may be more complex or advanced haptic solution available. e.g. simulating the surface by ultrasonic wave or static electricity, so that you can "feel" buttons on the panel. But they may need very special hardware or panels, which probably be difficult to get or hard to control. But it may mean the demo systm becomes very expensive, and not all of the members can easily try. From dominig.arfoll at fridu.net Wed Feb 7 07:50:30 2018 From: dominig.arfoll at fridu.net (Dominig Ar Foll) Date: Wed, 7 Feb 2018 08:50:30 +0100 Subject: [agl-discussions] Video of CES AGL demo from Intel Message-ID: Hello, as many of you could not visit CES, I am pleased to pass you some link of d?mos from AGL done by Intel (and so running on Intel HW :-) They are quite short but well done and quite informative. I'll be honest by saying that the demo form LG is the one that has impressed me the most. I would certainly encourage all of you to have a look at it. If you want to see only one, look at that one. https://vimeopro.com/cmdvideogroup/intelces2018/video/254070500 The demo from Denso is on mixing realtime OS and AGL with a hypervisor. Nice and clean. https://vimeopro.com/cmdvideogroup/intelces2018/video/254394087 Finally my demo is about Intel HW and AGL. What would you expect else. https://vimeopro.com/cmdvideogroup/intelces2018/video/254584552 If you have a bit more time, you will also find some other demos on this video page related to Automotive solution (but not AGL) that were presented during CES. Enjoy. -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre From tmatsuzawa at xevo.com Wed Feb 7 09:41:55 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Wed, 7 Feb 2018 09:41:55 +0000 Subject: [agl-discussions] Video of CES AGL demo from Intel In-Reply-To: References: Message-ID: Not sure how much % they overlap though. https://www.youtube.com/watch?v=4cmYCK9PBkM ________________________________________ From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Dominig Ar Foll Sent: Wednesday, February 7, 2018 4:50:30 PM To: automotive-discussions at lists.linuxfoundation.org Subject: [agl-discussions] Video of CES AGL demo from Intel Hello, as many of you could not visit CES, I am pleased to pass you some link of d?mos from AGL done by Intel (and so running on Intel HW :-) They are quite short but well done and quite informative. I'll be honest by saying that the demo form LG is the one that has impressed me the most. I would certainly encourage all of you to have a look at it. If you want to see only one, look at that one. https://vimeopro.com/cmdvideogroup/intelces2018/video/254070500 The demo from Denso is on mixing realtime OS and AGL with a hypervisor. Nice and clean. https://vimeopro.com/cmdvideogroup/intelces2018/video/254394087 Finally my demo is about Intel HW and AGL. What would you expect else. https://vimeopro.com/cmdvideogroup/intelces2018/video/254584552 If you have a bit more time, you will also find some other demos on this video page related to Automotive solution (but not AGL) that were presented during CES. Enjoy. -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From stephane.desneux at iot.bzh Wed Feb 7 10:06:01 2018 From: stephane.desneux at iot.bzh (Stephane Desneux) Date: Wed, 7 Feb 2018 11:06:01 +0100 Subject: [agl-discussions] AGL netboot NDB client configuration in initrd In-Reply-To: <1d8097f9-c48d-abb4-0148-f129c1a3fb9a@fridu.net> References: <33b876d0-b067-8a28-1bab-fc4071a1e8da@fridu.net> <1d8097f9-c48d-abb4-0148-f129c1a3fb9a@fridu.net> Message-ID: <970c8844-debc-ce25-e821-d26b7de2eb86@iot.bzh> Dominig, Everything related to netboot on image side is in meta-agl/meta-netboot. You'll find there the initscript responsible for mounting the nbd device exposed by the server side. Note that the nbd client is currently provided by busybox which may not be ideal for advanced features. For example, having a server that exposes multiples images is possible with xnbd but nbd client in busybox is not able to request a given named image. As a consequence, you'll have to stick with the simple model: * 1 TFTP instance that serves kernel + initrd + ... * 1 xnbd server instance that serves 1 image on 1 TCP port * 1 board boots on the xnbd server instance (nbd device is NOT shared by multiple boards) On the server side, I'm using xnbd server, available on debian. So the tool is embedded in the docker worker image that can be used to build AGL. After a successful build, it's easy to run the script [1] to start the TFTP server on the appropriate deploy folder and start xnbd server with the right ext4 image. And finally, for the command line, adding nbd.server=${serverip} should be enough. That said, more parameters are parsed by the initscript [2]. Reading the README [3] should also help a lot :) Last tip from my experience: nbd devices are sensible to filesystem corruption due to network latencies. So you may lose your ext4 image if you reboot too abruptly. So I do 2 things: * backup the initial ext4 file before booting (see run_xnbd_server script). If a corruption occurs, I can still copy the backup file without re-running bitbake. * to reboot fast & clean, I use "reboot -f" to reboot the boards: that runs a sync() but skips the systemd shutdown sequence (that may fail): this works like a charm on M3. HTH Steph [1]: https://git.automotivelinux.org/AGL/docker-worker-generator/tree/INSTALL/tools/scripts_netboot/run_xnbd_server [2]: https://git.automotivelinux.org/AGL/meta-agl/tree/meta-netboot/recipes-core/initramfs-netboot/files/init.sh#n76 [3]: https://git.automotivelinux.org/AGL/meta-agl/tree/meta-netboot/README --- Stephane Desneux - CTO stephane.desneux at iot.bzh - +33.257.620.237 - http://iot.bzh On 06/02/2018 16:42, Dominig ar Foll (Intel Open Source) wrote: > Hello, > > I have found an init script that should do the magic but is does NOT. > Could someone pass me a working set of configuration files: > ?- ndb server > ?- linux command line > > Thanks. > Dominig > > On 06/02/2018 12:14, Dominig ar Foll (Intel Open Source) wrote: >> Hello, >> >> I am reactivating the netboot for Intel. pxe and grub2 collaborate >> well enough to get my kernel and initrd loaded and started. >> I can see that the initnetbootramfs provide the ndb client, but I >> would be interesting by an example of a working config. >> I do not understand what starts the ndb client. The only systemd >> target in /etc is a broken link. >> >> Hints are welcome. >> -- >> Dominig ar Foll >> Senior Software Architect >> Intel Open Source Technology Centre > > -- > Dominig ar Foll > Senior Software Architect > Intel Open Source Technology Centre > > > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > From jsmoeller at linuxfoundation.org Wed Feb 7 15:07:57 2018 From: jsmoeller at linuxfoundation.org (Jan-Simon =?ISO-8859-1?Q?M=F6ller?=) Date: Wed, 07 Feb 2018 16:07:57 +0100 Subject: [agl-discussions] [RFC] Development / Gerrit Workflow tuning Message-ID: <2468018.AWp1xHMOA4@elrond> Hi all ! As a follow-up of today's SAT call we'd like to gather your feedback about the current gerrit workflow and how we can improve it. Please reply with your thoughts: - what is working good and should be kept as-is ? - what is slowing us down ? - what else would you change ? For the next development cycle, we'd like to gather your feedback on the proposed adaptations for the gerrit process: - We want to increase the number of maintainers with merge access to avoid bottlenecks and speed-up the flow of code. - Each profile (IVI, telematics, core) would have a set of maintainers (>=3) - src / staging would have a set of maintainers (>=5) - Maintainers would be nominated by the community and approved by SAT - Maintainers get +2 and merge rights in gerrit - gerrit will be adapted to: -- ignore the vote of the submitter/owner of the patch (no vote on own patch) -- votes become additive (e.g. +2 & +2 = +4) --- e.g. a +4 is required for merge --- up for discussion --- if +2 [=1*+2 merger review or as option 2*+1 normal reviews] --- or +4 [= 2*+2 merger review or as option 4*+1 normal reviews] -- all src / staging repos need to go through gerrit reviews going forward (no more direct push) Please tell us your thoughts about the above questions and the proposal. Thanks. Best regards, Jan-Simon M?ller AGL Release Manager From jsmoeller at linuxfoundation.org Tue Feb 6 20:30:14 2018 From: jsmoeller at linuxfoundation.org (Jan-Simon =?ISO-8859-1?Q?M=F6ller?=) Date: Tue, 06 Feb 2018 21:30:14 +0100 Subject: [agl-discussions] AGL netboot NDB client configuration in initrd In-Reply-To: <47436827.FDvlNaYZ9c@elrond> References: <33b876d0-b067-8a28-1bab-fc4071a1e8da@fridu.net> <1d8097f9-c48d-abb4-0148-f129c1a3fb9a@fridu.net> <47436827.FDvlNaYZ9c@elrond> Message-ID: <2838214.qDguDmx01M@elrond> Also see: https://git.automotivelinux.org/AGL/meta-agl/tree/meta-netboot/README Best, JS Am Dienstag, 6. Februar 2018, 21:27:08 CET schrieb Jan-Simon M?ller: > Hi Dominig, > > Here are the answers inline: > > > Am Dienstag, 6. Februar 2018, 16:42:57 CET schrieb Dominig ar Foll (Intel > Open > Source): > > Hello, > > > > I have found an init script that should do the magic but is does NOT. > > > > Could someone pass me a working set of configuration files: > > - ndb server > > xnbd-server: > > xnbd-server --logpath /tmp/xnbd.log --daemon \ > --target --lport 12345 /path/to/filesystem/image.ext4 > > e.g.: > xnbd-server --logpath /tmp/xnbd.log.55931 --daemon --target --lport 55931 \ > /var/lib/lava/dispatcher/tmp/5256/agl-image-ivi-crosssdk-m3ulcb.ext4 > > > linux cmdline: > > add: nbd.server= nbd.port= > > e.g.: > setenv nbdkbootargs ' ip=dhcp nbd.server=192.168.111.1 nbd.port=55931 root=/ > dev/ram0 ramdisk_size=16384 rootdelay=7 rw ip=dhcp' > > HTH, > Jan-Simon > > > - linux command line > > > > Thanks. > > Dominig > > > > On 06/02/2018 12:14, Dominig ar Foll (Intel Open Source) wrote: > > Hello, > > > > I am reactivating the netboot for Intel. pxe and grub2 collaborate well > > enough to get my kernel and initrd loaded and started. I can see that the > > initnetbootramfs provide the ndb client, but I would be interesting by an > > example of a working config. I do not understand what starts the ndb > > client. The only systemd target in /etc is a broken link. > > > > Hints are welcome. > > Dominig ar Foll > > Senior Software Architect > > Intel Open Source Technology Centre > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From Ahmad.BaniJamali at oulu.fi Wed Feb 7 15:23:09 2018 From: Ahmad.BaniJamali at oulu.fi (Ahmad Bani Jamali) Date: Wed, 7 Feb 2018 15:23:09 +0000 Subject: [agl-discussions] Invitation for an online Survey_Software Architecture for automotive IoT Cloud Platform Message-ID: Dear AGL partners, We at the University of Oulu, Finland empirically investigate "software architectures of automotive IoT cloud platforms" including design patterns (styles), quality attributes, evaluation methods, and tools. For this research, we depend on your contribution! We would very much appreciate if you fill out our survey and also forward it to other people with relevant expertise. Link to questionnaire: https://link.webropolsurveys.com/S/EDEA9BBBACF9E0FB Thank you very much for your kind support! Ahmad Banijamali & Pasi Kuvaja University of Oulu M3S Research Unit http://www.oulu.fi/m3s/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From tmatsuzawa at xevo.com Thu Feb 8 03:37:09 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Thu, 8 Feb 2018 03:37:09 +0000 Subject: [agl-discussions] haptic touch panel. In-Reply-To: References: Message-ID: By the way, AGL UI currently can give sound feedback (beep) when buttons, etc. are pressed? That may be the places where we may also want to give vibration, or maybe flash (for hearing-impaired drivers) feedbacks. ________________________________________ From: Takashi Matsuzawa Sent: Wednesday, February 7, 2018 4:21 PM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: haptic touch panel. I can see an example deisgn of haptic feedback touch panel: http://www.ti.com/lit/ug/tidu968/tidu968.pdf It uses DRV2667 chip to drive piezo actuators which are attached to a WVGA touch panel. On the document how-to DIY information is available, but it is not available as kit to purchse. This is giving feedback by actuator vibration, actuators are controlled by I2C signals from the host. I can see hobbiest I2C breakout board for DRV2667 is available (they sell this wit piezo actuators as set), so it may not be too difficult to make up something to give touch vibration on panel. (Since AGL uses Full HD palnel, you may need multiples of actuators?) https://hackaday.io/project/3086-piezo-haptic-flex-module I think this might be very primitive demo. (Not really sure - since I have not tried it yet. Perhaps choice of waveform and number of actuators may give you good result.) Alternative (not necessarily the choice is binary) option might be that going with mor professional and high-quality devices, maybe collaborating with special device manufactureres. There may be more complex or advanced haptic solution available. e.g. simulating the surface by ultrasonic wave or static electricity, so that you can "feel" buttons on the panel. But they may need very special hardware or panels, which probably be difficult to get or hard to control. But it may mean the demo systm becomes very expensive, and not all of the members can easily try. From jose.bollo at iot.bzh Thu Feb 8 09:28:22 2018 From: jose.bollo at iot.bzh (=?UTF-8?B?Sm9zw6k=?= Bollo) Date: Thu, 8 Feb 2018 10:28:22 +0100 Subject: [agl-discussions] [RFC] Development / Gerrit Workflow tuning In-Reply-To: <2468018.AWp1xHMOA4@elrond> References: <2468018.AWp1xHMOA4@elrond> Message-ID: <20180208102822.0c09bfea@d-jobol.iot.bzh> On Wed, 07 Feb 2018 16:07:57 +0100 Jan-Simon M?ller wrote: > Hi all ! > > As a follow-up of today's SAT call we'd like to gather your feedback > about the current gerrit workflow and how we can improve it. > > Please reply with your thoughts: > - what is working good and should be kept as-is ? The review process is cool. > - what is slowing us down ? CSS of gerrit not compliant with firefox (or conversely) I have to admit that sometime I am too lazy to review anything. Probably that enforcing me could help. > - what else would you change ? The CSS > For the next development cycle, we'd like to gather your feedback on > the proposed adaptations for the gerrit process: > > - We want to increase the number of maintainers with merge access to > avoid bottlenecks and speed-up the flow of code. Agreed, JSM is not enough. > - Each profile (IVI, telematics, core) would have a set of > maintainers (>=3) > - src / staging would have a set of maintainers (>=5) > - Maintainers would be nominated by the community and approved by SAT > - Maintainers get +2 and merge rights in gerrit > - gerrit will be adapted to: > -- ignore the vote of the submitter/owner of the patch (no vote on > own patch) > -- votes become additive (e.g. +2 & +2 = +4) > --- e.g. a +4 is required for merge > --- up for discussion > --- if +2 [=1*+2 merger review or as option 2*+1 normal > reviews] --- or +4 [= 2*+2 merger review or as option 4*+1 normal > reviews] Hum I'm skeptical about adding. Actual flow pleases me. > -- all src / staging repos need to go through gerrit reviews > going forward (no more direct push) I'm not in favor of that. This will not speed development as it increase the count of reviews. But I can adapt me... Best regards Jos? Bollo > Please tell us your thoughts about the above questions and the > proposal. > > > Thanks. > > Best regards, > > Jan-Simon M?ller > AGL Release Manager > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From tmatsuzawa at xevo.com Thu Feb 8 09:49:10 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Thu, 8 Feb 2018 09:49:10 +0000 Subject: [agl-discussions] Adding Up Boards (core and squared) support in Intel pages In-Reply-To: References: , Message-ID: Hello. Not a big issue, but I noticed scripts_mkefi-agl.sh now depends on "-P" (partscan) feature of losetup. I need to upgrade my host to ubuntu 16 for this. ________________________________________ From: Dominig ar Foll (Intel Open Source) Sent: Wednesday, January 31, 2018 8:25 PM To: Takashi Matsuzawa; Jan-Simon Moeller Cc: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] Adding Up Boards (core and squared) support in Intel pages Le 31/01/2018 ? 04:08, Takashi Matsuzawa a ?crit : > Hello. > I find it interesting that "Squared" board has header+FPGA for I/O customization. Yes, the FPGA changes with the model. I do not have the programming process, but I have the contact in Aaon (the manufactuer) if there is an interest. > Q1: So, both of the UP boards are supported by "intel-corei7-64" targets. Yes. As noticed, depending of the Com card that you add in the slot, you will have to select the right firmware in your build/conf/site.conf file, so your image embedded the firmware required by what ever COM car you will have selected. The same may apply to the PCI slot (driver and Firmware if required). > Q2: Do you know I can get schematics for UP boards - I only can see datasheets. > I just want to look into how their USB-OTG port pins are connected to the SoC. The Up boards are not Open Hardware by opposition to the Minnowboard. Neither the schematic, nor the BIOS code are available. Aaon sell boards which are compliant with Industrial requirement, but keep that know-how to themselves. They are open to commercial discussion would you require changes. On the opposite side, their bus interfaces (low and high speed) are open and documented. Dominig > > ________________________________________ > From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Jan-Simon Moeller > Sent: Wednesday, January 31, 2018 12:43:49 AM > To: Dominig ar Foll (Intel Open Source) > Cc: automotive-discussions at lists.linuxfoundation.org > Subject: Re: [agl-discussions] Adding Up Boards (core and squared) support in Intel pages > > Good. looking forward to net-booting the board. > js > > Am 30.01.2018 4:01 nachm. schrieb "Dominig ar Foll (Intel Open Source)" >: > Hello, > > for your info I have added the support of Up board (Squared and Core) to the Getting-Started/Intel pages. > It should become visible on AGL web site after 24 hours. > > If you are in a rush, you can check the github pages directly. > https://github.com/automotive-grade-linux/docs-agl > > You will also notice that the Up Boards are booting any valid AGL Intel images from a USB stick out of the box. > The major change is that the serial port connected on the Arduino connector is ttyS4 on my board but should be ttyS1 if documentation was correct (might differ on different HW release). > - http://www.up-board.org/wp-content/uploads/2017/11/UP-Square-DatasheetV0.5.pdf > > I have also describe the process to install AGL directly on the eMMC. > You may also notice that the Network boot seems to be more reliable/forgiving than with the Minnowboard. > > For more info on the Up boards please see: > https://www.up-community.org/ > > Enjoy. > > -- > Dominig ar Foll > Senior Software Architect > Intel Open Source Technology Centre > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre From tmatsuzawa at xevo.com Thu Feb 8 11:10:35 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Thu, 8 Feb 2018 11:10:35 +0000 Subject: [agl-discussions] Adding Up Boards (core and squared) support in Intel pages In-Reply-To: References: , , Message-ID: (Update) Hello. I am now trying to boot My UP2 board. The board has blue power LED near DC jack, but it does not light correctly. (i.e. it does not power-on) It lights only sometimes, when I re-plug the DC jack, but usually, just plug it in, nothing happens. LED stays blank. (I noticed there are 4 colorful LEDs also, but not sure about their purpose. They all are also lit sometimes, if I re-plug the DC jack.) Also it is lit properly if I connect FTDI cable to RPi header pins (so that 5V DC is fed from the header pins). I noticed following on their document: >UP Board and UP Core:DC power supply rated 5V/4A >UP Squared:DC power supply rated 5V/6A I am trying with 5V/4A or 5V/5A power supplies. Do I need precisely 5V/6A (6A or above) power supply to properly power it on? When properly powered on, what I should see on my HDMI display? Will I see BIOS setup screen? Or, it is just stay black until the Linux image (from my USB stick) properly boot up? ________________________________________ From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Takashi Matsuzawa Sent: Thursday, February 8, 2018 6:49 PM To: Dominig ar Foll (Intel Open Source); Jan-Simon Moeller Cc: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] Adding Up Boards (core and squared) support in Intel pages Hello. Not a big issue, but I noticed scripts_mkefi-agl.sh now depends on "-P" (partscan) feature of losetup. I need to upgrade my host to ubuntu 16 for this. ________________________________________ From: Dominig ar Foll (Intel Open Source) Sent: Wednesday, January 31, 2018 8:25 PM To: Takashi Matsuzawa; Jan-Simon Moeller Cc: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] Adding Up Boards (core and squared) support in Intel pages Le 31/01/2018 ? 04:08, Takashi Matsuzawa a ?crit : > Hello. > I find it interesting that "Squared" board has header+FPGA for I/O customization. Yes, the FPGA changes with the model. I do not have the programming process, but I have the contact in Aaon (the manufactuer) if there is an interest. > Q1: So, both of the UP boards are supported by "intel-corei7-64" targets. Yes. As noticed, depending of the Com card that you add in the slot, you will have to select the right firmware in your build/conf/site.conf file, so your image embedded the firmware required by what ever COM car you will have selected. The same may apply to the PCI slot (driver and Firmware if required). > Q2: Do you know I can get schematics for UP boards - I only can see datasheets. > I just want to look into how their USB-OTG port pins are connected to the SoC. The Up boards are not Open Hardware by opposition to the Minnowboard. Neither the schematic, nor the BIOS code are available. Aaon sell boards which are compliant with Industrial requirement, but keep that know-how to themselves. They are open to commercial discussion would you require changes. On the opposite side, their bus interfaces (low and high speed) are open and documented. Dominig > > ________________________________________ > From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Jan-Simon Moeller > Sent: Wednesday, January 31, 2018 12:43:49 AM > To: Dominig ar Foll (Intel Open Source) > Cc: automotive-discussions at lists.linuxfoundation.org > Subject: Re: [agl-discussions] Adding Up Boards (core and squared) support in Intel pages > > Good. looking forward to net-booting the board. > js > > Am 30.01.2018 4:01 nachm. schrieb "Dominig ar Foll (Intel Open Source)" >: > Hello, > > for your info I have added the support of Up board (Squared and Core) to the Getting-Started/Intel pages. > It should become visible on AGL web site after 24 hours. > > If you are in a rush, you can check the github pages directly. > https://github.com/automotive-grade-linux/docs-agl > > You will also notice that the Up Boards are booting any valid AGL Intel images from a USB stick out of the box. > The major change is that the serial port connected on the Arduino connector is ttyS4 on my board but should be ttyS1 if documentation was correct (might differ on different HW release). > - http://www.up-board.org/wp-content/uploads/2017/11/UP-Square-DatasheetV0.5.pdf > > I have also describe the process to install AGL directly on the eMMC. > You may also notice that the Network boot seems to be more reliable/forgiving than with the Minnowboard. > > For more info on the Up boards please see: > https://www.up-community.org/ > > Enjoy. > > -- > Dominig ar Foll > Senior Software Architect > Intel Open Source Technology Centre > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From dominig.arfoll at fridu.net Thu Feb 8 11:41:54 2018 From: dominig.arfoll at fridu.net (Dominig ar Foll (Intel Open Source)) Date: Thu, 8 Feb 2018 12:41:54 +0100 Subject: [agl-discussions] data persistence is broken in master Message-ID: An HTML attachment was scrubbed... URL: From tmatsuzawa at xevo.com Thu Feb 8 12:03:48 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Thu, 8 Feb 2018 12:03:48 +0000 Subject: [agl-discussions] Adding Up Boards (core and squared) support in Intel pages In-Reply-To: References: , , , Message-ID: Humm, they are saying there is a problem with heatsink/screws. https://forum.up-community.org/discussion/2251/up2-not-powering-on ________________________________________ From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Takashi Matsuzawa Sent: Thursday, February 8, 2018 8:10 PM To: Dominig ar Foll (Intel Open Source); Jan-Simon Moeller Cc: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] Adding Up Boards (core and squared) support in Intel pages (Update) Hello. I am now trying to boot My UP2 board. The board has blue power LED near DC jack, but it does not light correctly. (i.e. it does not power-on) It lights only sometimes, when I re-plug the DC jack, but usually, just plug it in, nothing happens. LED stays blank. (I noticed there are 4 colorful LEDs also, but not sure about their purpose. They all are also lit sometimes, if I re-plug the DC jack.) Also it is lit properly if I connect FTDI cable to RPi header pins (so that 5V DC is fed from the header pins). I noticed following on their document: >UP Board and UP Core:DC power supply rated 5V/4A >UP Squared:DC power supply rated 5V/6A I am trying with 5V/4A or 5V/5A power supplies. Do I need precisely 5V/6A (6A or above) power supply to properly power it on? When properly powered on, what I should see on my HDMI display? Will I see BIOS setup screen? Or, it is just stay black until the Linux image (from my USB stick) properly boot up? ________________________________________ From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Takashi Matsuzawa Sent: Thursday, February 8, 2018 6:49 PM To: Dominig ar Foll (Intel Open Source); Jan-Simon Moeller Cc: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] Adding Up Boards (core and squared) support in Intel pages Hello. Not a big issue, but I noticed scripts_mkefi-agl.sh now depends on "-P" (partscan) feature of losetup. I need to upgrade my host to ubuntu 16 for this. ________________________________________ From: Dominig ar Foll (Intel Open Source) Sent: Wednesday, January 31, 2018 8:25 PM To: Takashi Matsuzawa; Jan-Simon Moeller Cc: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] Adding Up Boards (core and squared) support in Intel pages Le 31/01/2018 ? 04:08, Takashi Matsuzawa a ?crit : > Hello. > I find it interesting that "Squared" board has header+FPGA for I/O customization. Yes, the FPGA changes with the model. I do not have the programming process, but I have the contact in Aaon (the manufactuer) if there is an interest. > Q1: So, both of the UP boards are supported by "intel-corei7-64" targets. Yes. As noticed, depending of the Com card that you add in the slot, you will have to select the right firmware in your build/conf/site.conf file, so your image embedded the firmware required by what ever COM car you will have selected. The same may apply to the PCI slot (driver and Firmware if required). > Q2: Do you know I can get schematics for UP boards - I only can see datasheets. > I just want to look into how their USB-OTG port pins are connected to the SoC. The Up boards are not Open Hardware by opposition to the Minnowboard. Neither the schematic, nor the BIOS code are available. Aaon sell boards which are compliant with Industrial requirement, but keep that know-how to themselves. They are open to commercial discussion would you require changes. On the opposite side, their bus interfaces (low and high speed) are open and documented. Dominig > > ________________________________________ > From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Jan-Simon Moeller > Sent: Wednesday, January 31, 2018 12:43:49 AM > To: Dominig ar Foll (Intel Open Source) > Cc: automotive-discussions at lists.linuxfoundation.org > Subject: Re: [agl-discussions] Adding Up Boards (core and squared) support in Intel pages > > Good. looking forward to net-booting the board. > js > > Am 30.01.2018 4:01 nachm. schrieb "Dominig ar Foll (Intel Open Source)" >: > Hello, > > for your info I have added the support of Up board (Squared and Core) to the Getting-Started/Intel pages. > It should become visible on AGL web site after 24 hours. > > If you are in a rush, you can check the github pages directly. > https://github.com/automotive-grade-linux/docs-agl > > You will also notice that the Up Boards are booting any valid AGL Intel images from a USB stick out of the box. > The major change is that the serial port connected on the Arduino connector is ttyS4 on my board but should be ttyS1 if documentation was correct (might differ on different HW release). > - http://www.up-board.org/wp-content/uploads/2017/11/UP-Square-DatasheetV0.5.pdf > > I have also describe the process to install AGL directly on the eMMC. > You may also notice that the Network boot seems to be more reliable/forgiving than with the Minnowboard. > > For more info on the Up boards please see: > https://www.up-community.org/ > > Enjoy. > > -- > Dominig ar Foll > Senior Software Architect > Intel Open Source Technology Centre > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From jsmoeller at linuxfoundation.org Thu Feb 8 12:08:15 2018 From: jsmoeller at linuxfoundation.org (Jan-Simon =?ISO-8859-1?Q?M=F6ller?=) Date: Thu, 08 Feb 2018 13:08:15 +0100 Subject: [agl-discussions] data persistence is broken in master In-Reply-To: References: Message-ID: <5932109.AphDi1DOOH@elrond> Am Donnerstag, 8. Februar 2018, 12:41:54 CET schrieb Dominig ar Foll (Intel Open Source): > Master is broken. > How is it possible to get a patch accepted that break master (missing file). The fix is in flight already. https://gerrit.automotivelinux.org/gerrit/#/c/13369/ Master uses ${AUTOREV} thus the recipe needs to catch up. Best, JS > ----------- log --------- > > DEBUG: Executing shell function do_configure > CMake Error: The source directory > "/home/dominig/AGL-master/build/tmp/work/corei7-64-agl-linux/agl-service-da > ta-persistence/1.0+gitAUTOINC+91e32ea5d4-r0/git/ll-database-binding" does > not exist. Specify --help for usage, or press the help button on the CMake > GUI. WARNING: > /home/dominig/AGL-master/build/tmp/work/corei7-64-agl-linux/agl-service-dat > a-persistence/1.0+gitAUTOINC+91e32ea5d4-r0/temp/run.do_configure.17275:1 > exit 1 from 'cmake $oecmake_sitefile > /home/dominig/AGL-master/build/tmp/work/corei7-64-agl-linux/agl-service-dat > a-persistence/1.0+gitAUTOINC+91e32ea5d4-r0/git/ll-database-binding > -DCMAKE_INSTALL_PREFIX:PATH=/usr -DCMAKE_INSTALL_BINDIR:PATH=bin > -DCMAKE_INSTALL_SBINDIR:PATH=sbin -DCMAKE_INSTALL_LIBEXECDIR:PATH=libexec > -DCMAKE_INSTALL_SYSCONFDIR:PATH=/etc > -DCMAKE_INSTALL_SHAREDSTATEDIR:PATH=../com > -DCMAKE_INSTALL_LOCALSTATEDIR:PATH=/var -DCMAKE_INSTALL_LIBDIR:PATH=lib > -DCMAKE_INSTALL_INCLUDEDIR:PATH=include > -DCMAKE_INSTALL_DATAROOTDIR:PATH=share -DCMAKE_INSTALL_SO_NO_EXE=0 > -DCMAKE_TOOLCHAIN_FILE=/home/dominig/AGL-master/build/tmp/work/corei7-64-ag > l-linux/agl-service-data-persistence/1.0+gitAUTOINC+91e32ea5d4-r0/toolchain. > cmake -DCMAKE_VERBOSE_MAKEFILE=1 -DCMAKE_NO_SYSTEM_FROM_IMPORTED=1 > ${PACKAGECONFIG_CONFARGS} -Wno-dev' ERROR: Function failed: do_configure > (log file is located at > /home/dominig/AGL-master/build/tmp/work/corei7-64-agl-linux/agl-service-dat > a-persistence/1.0+gitAUTOINC+91e32ea5d4-r0/temp/log.do_configure.17275) > Dominig ar Foll > Senior Software Architect > Intel Open Source Technology Centre From jose.bollo at iot.bzh Thu Feb 8 12:13:46 2018 From: jose.bollo at iot.bzh (=?UTF-8?B?Sm9zw6k=?= Bollo) Date: Thu, 8 Feb 2018 13:13:46 +0100 Subject: [agl-discussions] data persistence is broken in master In-Reply-To: <5932109.AphDi1DOOH@elrond> References: <5932109.AphDi1DOOH@elrond> Message-ID: <20180208131346.27b11ba4@d-jobol.iot.bzh> On Thu, 08 Feb 2018 13:08:15 +0100 Jan-Simon M?ller wrote: > Am Donnerstag, 8. Februar 2018, 12:41:54 CET schrieb Dominig ar Foll > (Intel Open Source): > > Master is broken. > > How is it possible to get a patch accepted that break master > > (missing file). > > The fix is in flight already. > https://gerrit.automotivelinux.org/gerrit/#/c/13369/ > Master uses ${AUTOREV} thus the recipe needs to catch up. AUTOREV is not good, that is one more proof Regards Jose > Best, > JS > > > > ----------- log --------- > > > > DEBUG: Executing shell function do_configure > > CMake Error: The source directory > > "/home/dominig/AGL-master/build/tmp/work/corei7-64-agl-linux/agl-service-da > > ta-persistence/1.0+gitAUTOINC+91e32ea5d4-r0/git/ll-database-binding" > > does not exist. Specify --help for usage, or press the help button > > on the CMake GUI. WARNING: > > /home/dominig/AGL-master/build/tmp/work/corei7-64-agl-linux/agl-service-dat > > a-persistence/1.0+gitAUTOINC+91e32ea5d4-r0/temp/run.do_configure.17275:1 > > exit 1 from 'cmake $oecmake_sitefile > > /home/dominig/AGL-master/build/tmp/work/corei7-64-agl-linux/agl-service-dat > > a-persistence/1.0+gitAUTOINC+91e32ea5d4-r0/git/ll-database-binding > > -DCMAKE_INSTALL_PREFIX:PATH=/usr -DCMAKE_INSTALL_BINDIR:PATH=bin > > -DCMAKE_INSTALL_SBINDIR:PATH=sbin > > -DCMAKE_INSTALL_LIBEXECDIR:PATH=libexec > > -DCMAKE_INSTALL_SYSCONFDIR:PATH=/etc > > -DCMAKE_INSTALL_SHAREDSTATEDIR:PATH=../com > > -DCMAKE_INSTALL_LOCALSTATEDIR:PATH=/var > > -DCMAKE_INSTALL_LIBDIR:PATH=lib > > -DCMAKE_INSTALL_INCLUDEDIR:PATH=include > > -DCMAKE_INSTALL_DATAROOTDIR:PATH=share -DCMAKE_INSTALL_SO_NO_EXE=0 > > -DCMAKE_TOOLCHAIN_FILE=/home/dominig/AGL-master/build/tmp/work/corei7-64-ag > > l-linux/agl-service-data-persistence/1.0+gitAUTOINC+91e32ea5d4-r0/toolchain. > > cmake -DCMAKE_VERBOSE_MAKEFILE=1 -DCMAKE_NO_SYSTEM_FROM_IMPORTED=1 > > ${PACKAGECONFIG_CONFARGS} -Wno-dev' ERROR: Function failed: > > do_configure (log file is located > > at /home/dominig/AGL-master/build/tmp/work/corei7-64-agl-linux/agl-service-dat > > a-persistence/1.0+gitAUTOINC+91e32ea5d4-r0/temp/log.do_configure.17275) > > Dominig ar Foll Senior Software Architect Intel Open Source > > Technology Centre > > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From tmatsuzawa at xevo.com Thu Feb 8 12:50:09 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Thu, 8 Feb 2018 12:50:09 +0000 Subject: [agl-discussions] Adding Up Boards (core and squared) support in Intel pages In-Reply-To: References: , , , , Message-ID: As told on the UP community thread, the power is properly on if I loosen one of the 4 screws that attach large heatsink to the board. (Looks like it is related to the amount of pressure on CPU by heatsink) ________________________________________ From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Takashi Matsuzawa Sent: Thursday, February 8, 2018 9:03 PM To: Dominig ar Foll (Intel Open Source); Jan-Simon Moeller Cc: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] Adding Up Boards (core and squared) support in Intel pages Humm, they are saying there is a problem with heatsink/screws. https://forum.up-community.org/discussion/2251/up2-not-powering-on ________________________________________ From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Takashi Matsuzawa Sent: Thursday, February 8, 2018 8:10 PM To: Dominig ar Foll (Intel Open Source); Jan-Simon Moeller Cc: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] Adding Up Boards (core and squared) support in Intel pages (Update) Hello. I am now trying to boot My UP2 board. The board has blue power LED near DC jack, but it does not light correctly. (i.e. it does not power-on) It lights only sometimes, when I re-plug the DC jack, but usually, just plug it in, nothing happens. LED stays blank. (I noticed there are 4 colorful LEDs also, but not sure about their purpose. They all are also lit sometimes, if I re-plug the DC jack.) Also it is lit properly if I connect FTDI cable to RPi header pins (so that 5V DC is fed from the header pins). I noticed following on their document: >UP Board and UP Core:DC power supply rated 5V/4A >UP Squared:DC power supply rated 5V/6A I am trying with 5V/4A or 5V/5A power supplies. Do I need precisely 5V/6A (6A or above) power supply to properly power it on? When properly powered on, what I should see on my HDMI display? Will I see BIOS setup screen? Or, it is just stay black until the Linux image (from my USB stick) properly boot up? ________________________________________ From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Takashi Matsuzawa Sent: Thursday, February 8, 2018 6:49 PM To: Dominig ar Foll (Intel Open Source); Jan-Simon Moeller Cc: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] Adding Up Boards (core and squared) support in Intel pages Hello. Not a big issue, but I noticed scripts_mkefi-agl.sh now depends on "-P" (partscan) feature of losetup. I need to upgrade my host to ubuntu 16 for this. ________________________________________ From: Dominig ar Foll (Intel Open Source) Sent: Wednesday, January 31, 2018 8:25 PM To: Takashi Matsuzawa; Jan-Simon Moeller Cc: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] Adding Up Boards (core and squared) support in Intel pages Le 31/01/2018 ? 04:08, Takashi Matsuzawa a ?crit : > Hello. > I find it interesting that "Squared" board has header+FPGA for I/O customization. Yes, the FPGA changes with the model. I do not have the programming process, but I have the contact in Aaon (the manufactuer) if there is an interest. > Q1: So, both of the UP boards are supported by "intel-corei7-64" targets. Yes. As noticed, depending of the Com card that you add in the slot, you will have to select the right firmware in your build/conf/site.conf file, so your image embedded the firmware required by what ever COM car you will have selected. The same may apply to the PCI slot (driver and Firmware if required). > Q2: Do you know I can get schematics for UP boards - I only can see datasheets. > I just want to look into how their USB-OTG port pins are connected to the SoC. The Up boards are not Open Hardware by opposition to the Minnowboard. Neither the schematic, nor the BIOS code are available. Aaon sell boards which are compliant with Industrial requirement, but keep that know-how to themselves. They are open to commercial discussion would you require changes. On the opposite side, their bus interfaces (low and high speed) are open and documented. Dominig > > ________________________________________ > From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Jan-Simon Moeller > Sent: Wednesday, January 31, 2018 12:43:49 AM > To: Dominig ar Foll (Intel Open Source) > Cc: automotive-discussions at lists.linuxfoundation.org > Subject: Re: [agl-discussions] Adding Up Boards (core and squared) support in Intel pages > > Good. looking forward to net-booting the board. > js > > Am 30.01.2018 4:01 nachm. schrieb "Dominig ar Foll (Intel Open Source)" >: > Hello, > > for your info I have added the support of Up board (Squared and Core) to the Getting-Started/Intel pages. > It should become visible on AGL web site after 24 hours. > > If you are in a rush, you can check the github pages directly. > https://github.com/automotive-grade-linux/docs-agl > > You will also notice that the Up Boards are booting any valid AGL Intel images from a USB stick out of the box. > The major change is that the serial port connected on the Arduino connector is ttyS4 on my board but should be ttyS1 if documentation was correct (might differ on different HW release). > - http://www.up-board.org/wp-content/uploads/2017/11/UP-Square-DatasheetV0.5.pdf > > I have also describe the process to install AGL directly on the eMMC. > You may also notice that the Network boot seems to be more reliable/forgiving than with the Minnowboard. > > For more info on the Up boards please see: > https://www.up-community.org/ > > Enjoy. > > -- > Dominig ar Foll > Senior Software Architect > Intel Open Source Technology Centre > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From leon.anavi at konsulko.com Thu Feb 8 14:33:06 2018 From: leon.anavi at konsulko.com (Leon Anavi) Date: Thu, 8 Feb 2018 16:33:06 +0200 Subject: [agl-discussions] FOSDEM 2018 Feedback Message-ID: <0a0d5c2e-5fbb-c276-4753-b11f60f71f6b@konsulko.com> Hi, It was a great pleasure for me to be a volunteer at AGL stand at FOSDEM for a second year in a row. Walt, thank you for arranging the AGL stand. Jan-Simon, Sebastien, thank you for booking the restaurant for the automotive community dinner on Saturday. Most of the time there was a huge queue on the AGL stand and some of my friends even complained that the didn't get the change to have a closer look at our stuff. There were 3 AGL demos: * 2018 CES Demonstrator * Automotive user interface based on Chromium by Igalia * Software updates with meta-updater and OSTree by ATS Advanced Telematic Systems (a Here Company) and Konsulko Group using Funky Flounder (this was my part of the demos :) ) I have published more details at the AGL wiki: https://wiki.automotivelinux.org/agl-distro/fosdem-2018 https://wiki.automotivelinux.org/agl-distro/libostree-demo I was at AGL stand on Saturday late afternoon and Sunday afternoon. In my opinion, it was very convenient that we were next to OpenEmbedded stand. Based on my experience, some visitors had been already familiar with AGL based on the demos from FOSDEM 2017, others were completely new to the project and of course there were a lot of visitors from the automotive industry who knew AGLL well. Again, the most frequently asked question by open source enthusiasts was "how can I get AGL in my car?" It was the same at FOSDEM 2017. Thinking aloud, may be it is worth putting efforts in the community supported boards such as Raspberry Pi 3 to have something useful for the cars of the most technically advanced enthusiasts. The automotive community dinner at Saturday night was really nice (despite the hilariously absurd issues of the restaurant to provide the bill :) ). It was great to see at one place contributors from Automotive Grade Linux, GENIVI Dev Platform and Tizen. I hope we will do the AGL stand again at FOSDEM 2019 :) Thanks, Leon -- Leon Anavi Software Engineer konsulko.com From wminer at linuxfoundation.org Thu Feb 8 15:26:33 2018 From: wminer at linuxfoundation.org (Walt Miner) Date: Thu, 8 Feb 2018 09:26:33 -0600 Subject: [agl-discussions] FOSDEM 2018 Feedback In-Reply-To: <0a0d5c2e-5fbb-c276-4753-b11f60f71f6b@konsulko.com> References: <0a0d5c2e-5fbb-c276-4753-b11f60f71f6b@konsulko.com> Message-ID: Hello Leon, Thanks for helping out at the demo table and thank you to the IoT.bzh team and Maxim from Igalia as well for helping out. The most common question definitely was how can I get this in my car. I saw your talk on Saturday and it was very good. I did not get a chance to see your Sunday session, but I am sure it was excellent. Let me be the first to say that we should definitely go to the same restaurant next year or Le Bugatti, where nine of us went on Friday night, since bill calculation hilarity will definitely ensue at either place. Regards, Walt On Thu, Feb 8, 2018 at 8:33 AM, Leon Anavi wrote: > Hi, > > It was a great pleasure for me to be a volunteer at AGL stand at FOSDEM > for a second year in a row. Walt, thank you for arranging the AGL stand. > Jan-Simon, Sebastien, thank you for booking the restaurant for the > automotive community dinner on Saturday. > > Most of the time there was a huge queue on the AGL stand and some of my > friends even complained that the didn't get the change to have a closer > look at our stuff. There were 3 AGL demos: > * 2018 CES Demonstrator > * Automotive user interface based on Chromium by Igalia > * Software updates with meta-updater and OSTree by ATS Advanced > Telematic Systems (a Here Company) and Konsulko Group using Funky > Flounder (this was my part of the demos :) ) > > I have published more details at the AGL wiki: > https://wiki.automotivelinux.org/agl-distro/fosdem-2018 > https://wiki.automotivelinux.org/agl-distro/libostree-demo > > I was at AGL stand on Saturday late afternoon and Sunday afternoon. In > my opinion, it was very convenient that we were next to OpenEmbedded > stand. Based on my experience, some visitors had been already familiar > with AGL based on the demos from FOSDEM 2017, others were completely new > to the project and of course there were a lot of visitors from the > automotive industry who knew AGLL well. Again, the most frequently asked > question by open source enthusiasts was "how can I get AGL in my car?" > It was the same at FOSDEM 2017. Thinking aloud, may be it is worth > putting efforts in the community supported boards such as Raspberry Pi 3 > to have something useful for the cars of the most technically advanced > enthusiasts. > > The automotive community dinner at Saturday night was really nice > (despite the hilariously absurd issues of the restaurant to provide the > bill :) ). It was great to see at one place contributors from Automotive > Grade Linux, GENIVI Dev Platform and Tizen. > > I hope we will do the AGL stand again at FOSDEM 2019 :) > > Thanks, > Leon > > -- > Leon Anavi > Software Engineer > konsulko.com > > > -- Walt Miner Engineering Project Manager The Linux Foundation mobile: +1.847.502.7087 Visit us at: automotive.linuxfoundation.org www.linuxfoundation.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From tmatsuzawa at xevo.com Thu Feb 8 16:28:59 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Thu, 8 Feb 2018 16:28:59 +0000 Subject: [agl-discussions] FOSDEM 2018 Feedback In-Reply-To: References: <0a0d5c2e-5fbb-c276-4753-b11f60f71f6b@konsulko.com>, Message-ID: >Thinking aloud, may be it is worth putting efforts in the community supported boards such as Raspberry Pi 3 to have something useful for the cars of the most technically advanced enthusiasts. May not be totally AGL BSP issue, and this may not be a premium / OEM soliution, what I immediately think is: - HDMI/touch screen (can I mount that HDML panel to my car and/or can I use my iPad as display for my AGL/RPi?) - map/navigation (a map for my local region) - GPS dongle? - Audio (can it be connected to my car's audio??) - Power (anhy RPI car DC connection kit?) Maybe having "reference kit" for this may help people setup things easier on their cars. ________________________________________ From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Walt Miner Sent: Friday, February 9, 2018 12:26:33 AM To: Leon Anavi Cc: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] FOSDEM 2018 Feedback Hello Leon, Thanks for helping out at the demo table and thank you to the IoT.bzh team and Maxim from Igalia as well for helping out. The most common question definitely was how can I get this in my car. I saw your talk on Saturday and it was very good. I did not get a chance to see your Sunday session, but I am sure it was excellent. Let me be the first to say that we should definitely go to the same restaurant next year or Le Bugatti, where nine of us went on Friday night, since bill calculation hilarity will definitely ensue at either place. Regards, Walt On Thu, Feb 8, 2018 at 8:33 AM, Leon Anavi > wrote: Hi, It was a great pleasure for me to be a volunteer at AGL stand at FOSDEM for a second year in a row. Walt, thank you for arranging the AGL stand. Jan-Simon, Sebastien, thank you for booking the restaurant for the automotive community dinner on Saturday. Most of the time there was a huge queue on the AGL stand and some of my friends even complained that the didn't get the change to have a closer look at our stuff. There were 3 AGL demos: * 2018 CES Demonstrator * Automotive user interface based on Chromium by Igalia * Software updates with meta-updater and OSTree by ATS Advanced Telematic Systems (a Here Company) and Konsulko Group using Funky Flounder (this was my part of the demos :) ) I have published more details at the AGL wiki: https://wiki.automotivelinux.org/agl-distro/fosdem-2018 https://wiki.automotivelinux.org/agl-distro/libostree-demo I was at AGL stand on Saturday late afternoon and Sunday afternoon. In my opinion, it was very convenient that we were next to OpenEmbedded stand. Based on my experience, some visitors had been already familiar with AGL based on the demos from FOSDEM 2017, others were completely new to the project and of course there were a lot of visitors from the automotive industry who knew AGLL well. Again, the most frequently asked question by open source enthusiasts was "how can I get AGL in my car?" It was the same at FOSDEM 2017. Thinking aloud, may be it is worth putting efforts in the community supported boards such as Raspberry Pi 3 to have something useful for the cars of the most technically advanced enthusiasts. The automotive community dinner at Saturday night was really nice (despite the hilariously absurd issues of the restaurant to provide the bill :) ). It was great to see at one place contributors from Automotive Grade Linux, GENIVI Dev Platform and Tizen. I hope we will do the AGL stand again at FOSDEM 2019 :) Thanks, Leon -- Leon Anavi Software Engineer konsulko.com -- Walt Miner [https://docs.google.com/uc?export=download&id=0ByWQ8KVvCEUreGlqdXdwMTE5SXM&revid=0ByWQ8KVvCEUrSXIzMmFsMkxxR3ZybnR5dE9tU3dRc3d6cFFZPQ] Engineering Project Manager The Linux Foundation mobile: +1.847.502.7087 Visit us at: automotive.linuxfoundation.org www.linuxfoundation.org From mkelly at xevo.com Thu Feb 8 21:19:37 2018 From: mkelly at xevo.com (Martin Kelly) Date: Thu, 8 Feb 2018 13:19:37 -0800 Subject: [agl-discussions] data persistence is broken in master In-Reply-To: <20180208131346.27b11ba4@d-jobol.iot.bzh> References: <5932109.AphDi1DOOH@elrond> <20180208131346.27b11ba4@d-jobol.iot.bzh> Message-ID: <3f13fe89-42e2-bcb9-12fd-ad9279d78cd8@xevo.com> On 02/08/2018 04:13 AM, Jos? Bollo wrote: > On Thu, 08 Feb 2018 13:08:15 +0100 > Jan-Simon M?ller wrote: > >> Am Donnerstag, 8. Februar 2018, 12:41:54 CET schrieb Dominig ar Foll >> (Intel Open Source): >>> Master is broken. >>> How is it possible to get a patch accepted that break master >>> (missing file). >> >> The fix is in flight already. >> https://gerrit.automotivelinux.org/gerrit/#/c/13369/ >> Master uses ${AUTOREV} thus the recipe needs to catch up. > > AUTOREV is not good, that is one more proof > +1! From mkelly at xevo.com Thu Feb 8 21:33:19 2018 From: mkelly at xevo.com (Martin Kelly) Date: Thu, 8 Feb 2018 13:33:19 -0800 Subject: [agl-discussions] GPLv2 handling Message-ID: <553cc97c-3e65-4bf5-af0a-7d633cea6d90@xevo.com> Hi, I noticed we recently started pulling in the meta-gplv2 layer for agl-demo and defaulting to its recipes in the AGL distro settings. Although I can see the reasoning for this, it also breaks a number of recipes because what's in meta-gplv2 is very old (e.g. readline 5 vs readline 7). I noticed this breakage when trying to build networkmanager (which needs at least readline 6), but I'm sure there are many other breakages because of such old recipes. I'm wondering if anyone has objections to making this all controlled at the top-level, while preserving the current GPLv2 default. My first thoughts on how to do this are: - An AGL feature called "agl-demo-gplv3" that would add in agl-demo but not meta-gplv2. - A DISTRO_FEATURE "gplv3", unset by default. If it is not set, then we make the PREFERRED_VERSION for various libraries default to gplv2 versions in our distro settings. There also may be better ways to achieve the same purpose that I have not thought of. Please let me know your thoughts, Martin From jsmoeller at linuxfoundation.org Thu Feb 8 22:39:20 2018 From: jsmoeller at linuxfoundation.org (Jan-Simon =?ISO-8859-1?Q?M=F6ller?=) Date: Thu, 08 Feb 2018 23:39:20 +0100 Subject: [agl-discussions] GPLv2 handling In-Reply-To: <553cc97c-3e65-4bf5-af0a-7d633cea6d90@xevo.com> References: <553cc97c-3e65-4bf5-af0a-7d633cea6d90@xevo.com> Message-ID: <1893515.ueZbnqy5sa@elrond> Am Donnerstag, 8. Februar 2018, 22:33:19 CET schrieb Martin Kelly: > Hi, > > I noticed we recently started pulling in the meta-gplv2 layer for > agl-demo and defaulting to its recipes in the AGL distro settings. > Although I can see the reasoning for this, it also breaks a number of > recipes because what's in meta-gplv2 is very old (e.g. readline 5 vs > readline 7). I noticed this breakage when trying to build networkmanager > (which needs at least readline 6), but I'm sure there are many other > breakages because of such old recipes. > > I'm wondering if anyone has objections to making this all controlled at > the top-level, while preserving the current GPLv2 default. > > My first thoughts on how to do this are: > > - An AGL feature called "agl-demo-gplv3" that would add in agl-demo but > not meta-gplv2. > - A DISTRO_FEATURE "gplv3", unset by default. If it is not set, then we > make the PREFERRED_VERSION for various libraries default to gplv2 > versions in our distro settings. Yes, right now its global. In general ack, that a switch would be good. We might have to be a little more specific (e.g. no gplv3 on _class-target but allow on _class-nativesdk or _class-native ). @Matt: thoughts ? suggestions ? Best, Jan-Simon From tmatsuzawa at xevo.com Fri Feb 9 03:44:40 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Fri, 9 Feb 2018 03:44:40 +0000 Subject: [agl-discussions] UP2 board In-Reply-To: References: , , , , , Message-ID: Hello. I tried with thinner sillicon sheet, but looks like careful adjustment is needed when I attach heat-sink to the board. This really should be addressed by AAEON. Anyhow, I could boot AGL snapshot image on it, but I am seeing WM is not being loaded correctly. I can see OS is booting and can look into the log, the boot log displayed on display, and I can see weston process is running, but the display remains black afterwards. Is should be snapshot build issue, or maybe related to the board? (I used the board as it arried - not updated BIOS, no change in the BIOS setup, etc.) ==== Feb 09 10:32:09 intel-corei7-64 afbd-windowmanager-service-2017 at 0.1[546]: NOTICE: API monitor started [/usr/src/debug/af-binder/master+gitAUTOINC+9c1c9a1ba4-r0/git/src/afb-apiset.c:353,start_api] Feb 09 10:32:09 intel-corei7-64 afbd-windowmanager-service-2017 at 0.1[546]: INFO: API windowmanager starting... [/usr/src/debug/af-binder/master+gitAUTOINC+9c1c9a1ba4-r0/git/src/afb-apiset.c:338,start_api] Feb 09 10:32:09 intel-corei7-64 afbd-windowmanager-service-2017 at 0.1[546]: [174332.798] [wm ERROR] [app.cpp, init_layers(), Line:183] >>> ivi_controller global not available Feb 09 10:32:09 intel-corei7-64 afbd-windowmanager-service-2017 at 0.1[546]: [174332.828] [wm ERROR] [main.cpp, _binding_init(), Line:126] >>> Could not connect to compositor Feb 09 10:32:09 intel-corei7-64 afbd-windowmanager-service-2017 at 0.1[546]: ERROR: Initialisation of service API windowmanager failed (-1): Success [/usr/src/debug/af-binder/master+gitAUTOINC+9c1c9a1ba4-r0/git/src/afb-export.c:1375,afb_export_start] Feb 09 10:32:09 intel-corei7-64 afbd-windowmanager-service-2017 at 0.1[546]: ERROR: The api windowmanager failed to start (-1) ==== [...] From tanikawa.tadao at jp.panasonic.com Fri Feb 9 08:03:04 2018 From: tanikawa.tadao at jp.panasonic.com (tanikawa.tadao at jp.panasonic.com) Date: Fri, 9 Feb 2018 08:03:04 +0000 Subject: [agl-discussions] UP2 board In-Reply-To: References: , , , , , Message-ID: <05a75ac700764088a855698f24b47166@JPA000SECMN07.palet.jp.panasonic.com> > Anyhow, I could boot AGL snapshot image on it On master branch, you have to wait 1 patch will be merged for window manager. https://gerrit.automotivelinux.org/gerrit/#/c/13315/2 Regards, Tadao > -----Original Message----- > From: automotive-discussions-bounces at lists.linuxfoundation.org > [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On Behalf Of Takashi Matsuzawa > Sent: Friday, February 09, 2018 12:45 PM > To: Dominig ar Foll (Intel Open Source) > Cc: automotive-discussions at lists.linuxfoundation.org > Subject: Re: [agl-discussions] UP2 board > > Hello. > > I tried with thinner sillicon sheet, but looks like careful adjustment is needed when I attach heat-sink to the board. > This really should be addressed by AAEON. > > Anyhow, I could boot AGL snapshot image on it, but I am seeing WM is not being loaded correctly. > I can see OS is booting and can look into the log, the boot log displayed on display, and I can see weston process > is running, but the display remains black afterwards. > > Is should be snapshot build issue, or maybe related to the board? > (I used the board as it arried - not updated BIOS, no change in the BIOS setup, etc.) > > ==== > Feb 09 10:32:09 intel-corei7-64 afbd-windowmanager-service-2017 at 0.1[546]: NOTICE: API monitor started > [/usr/src/debug/af-binder/master+gitAUTOINC+9c1c9a1ba4-r0/git/src/afb-apiset.c:353,start_api] > Feb 09 10:32:09 intel-corei7-64 afbd-windowmanager-service-2017 at 0.1[546]: INFO: API windowmanager starting... > [/usr/src/debug/af-binder/master+gitAUTOINC+9c1c9a1ba4-r0/git/src/afb-apiset.c:338,start_api] > Feb 09 10:32:09 intel-corei7-64 afbd-windowmanager-service-2017 at 0.1[546]: [174332.798] [wm ERROR] [app.cpp, > init_layers(), Line:183] >>> ivi_controller global not available > Feb 09 10:32:09 intel-corei7-64 afbd-windowmanager-service-2017 at 0.1[546]: [174332.828] [wm ERROR] [main.cpp, > _binding_init(), Line:126] >>> Could not connect to compositor > Feb 09 10:32:09 intel-corei7-64 afbd-windowmanager-service-2017 at 0.1[546]: ERROR: Initialisation of service API > windowmanager failed (-1): Success > [/usr/src/debug/af-binder/master+gitAUTOINC+9c1c9a1ba4-r0/git/src/afb-export.c:1375,afb_export_start] > Feb 09 10:32:09 intel-corei7-64 afbd-windowmanager-service-2017 at 0.1[546]: ERROR: The api windowmanager failed to > start (-1) > ==== > > [...] > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From msisov at igalia.com Fri Feb 9 13:42:56 2018 From: msisov at igalia.com (Maksim Sisov) Date: Fri, 09 Feb 2018 15:42:56 +0200 Subject: [agl-discussions] FOSDEM 2018 Feedback In-Reply-To: References: <0a0d5c2e-5fbb-c276-4753-b11f60f71f6b@konsulko.com> Message-ID: <16f501a4fea92f6c765b0c4f11513c12@igalia.com> Hi! Thank you! It was a pleasure to meet and talk to you at FOSDEM! Regards, Maksim On 08.02.2018 17:26, Walt Miner wrote: > Hello Leon, > Thanks for helping out at the demo table and thank you to the IoT.bzh > team and Maxim from Igalia as well for helping out. The most common > question definitely was how can I get this in my car. I saw your > talk on Saturday and it was very good. I did not get a chance to see > your Sunday session, but I am sure it was excellent. > > Let me be the first to say that we should definitely go to the same > restaurant next year or Le Bugatti, where nine of us went on Friday > night, since bill calculation hilarity will definitely ensue at either > place. > > Regards, > Walt > > On Thu, Feb 8, 2018 at 8:33 AM, Leon Anavi > wrote: > >> Hi, >> >> It was a great pleasure for me to be a volunteer at AGL stand at >> FOSDEM >> for a second year in a row. Walt, thank you for arranging the AGL >> stand. >> Jan-Simon, Sebastien, thank you for booking the restaurant for the >> automotive community dinner on Saturday. >> >> Most of the time there was a huge queue on the AGL stand and some of >> my >> friends even complained that the didn't get the change to have a >> closer >> look at our stuff. There were 3 AGL demos: >> * 2018 CES Demonstrator >> * Automotive user interface based on Chromium by Igalia >> * Software updates with meta-updater and OSTree by ATS Advanced >> Telematic Systems (a Here Company) and Konsulko Group using Funky >> Flounder (this was my part of the demos :) ) >> >> I have published more details at the AGL wiki: >> https://wiki.automotivelinux.org/agl-distro/fosdem-2018 [1] >> https://wiki.automotivelinux.org/agl-distro/libostree-demo [2] >> >> I was at AGL stand on Saturday late afternoon and Sunday afternoon. >> In >> my opinion, it was very convenient that we were next to OpenEmbedded >> stand. Based on my experience, some visitors had been already >> familiar >> with AGL based on the demos from FOSDEM 2017, others were completely >> new >> to the project and of course there were a lot of visitors from the >> automotive industry who knew AGLL well. Again, the most frequently >> asked >> question by open source enthusiasts was "how can I get AGL in my >> car?" >> It was the same at FOSDEM 2017. Thinking aloud, may be it is worth >> putting efforts in the community supported boards such as Raspberry >> Pi 3 >> to have something useful for the cars of the most technically >> advanced >> enthusiasts. >> >> The automotive community dinner at Saturday night was really nice >> (despite the hilariously absurd issues of the restaurant to provide >> the >> bill :) ). It was great to see at one place contributors from >> Automotive >> Grade Linux, GENIVI Dev Platform and Tizen. >> >> I hope we will do the AGL stand again at FOSDEM 2019 :) >> >> Thanks, >> Leon >> >> -- >> Leon Anavi >> Software Engineer >> konsulko.com [3] > > -- > > Walt Miner > > [4] > > Engineering Project Manager > The Linux Foundation > > mobile: +1.847.502.7087 > > Visit us at: > automotive.linuxfoundation.org [5] > > www.linuxfoundation.org [6] > > > > Links: > ------ > [1] https://wiki.automotivelinux.org/agl-distro/fosdem-2018 > [2] https://wiki.automotivelinux.org/agl-distro/libostree-demo > [3] http://konsulko.com > [4] https://twitter.com/VStarWalt > [5] http://automotive.linuxfoundation.org > [6] http://www.linuxfoundation.org > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From wminer at linuxfoundation.org Fri Feb 9 13:54:09 2018 From: wminer at linuxfoundation.org (wminer at linuxfoundation.org) Date: Fri, 09 Feb 2018 13:54:09 +0000 Subject: [agl-discussions] Updated invitation: EG Virtualization @ Tue Feb 13, 2018 9am - 10am (CST) (automotive-discussions@lists.linuxfoundation.org) Message-ID: <001a114b387cd63f730564c7dcdc@google.com> This event has been changed. Title: EG Virtualization 1. Please join my meeting. https://global.gotomeeting.com/join/728365005 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. Australia: +61 2 9091 7603 Austria: +43 1 2530 22500 Belgium: +32 (0) 27 00 6375 Canada (toll-free): 1 888 299 1889 Canada: +1 (647) 497-9373 Denmark: +45 32 72 03 69 Finland: +358 (0) 923 17 0555 France: +33 (0) 170 950 585 Germany: +49 (0) 692 5736 7208 India (toll-free): 000 800 852 1424 Ireland: +353 (0) 15 255 598 Italy: +39 0 699 26 68 65 Japan (toll-free): 0 120 352 900 Korea, Republic of (toll-free): 0806180880 Netherlands: +31 (0) 707 709 520 New Zealand: +64 9 887 3469 Norway: +47 23 96 01 18 Spain: +34 932 75 1230 Sweden: +46 (0) 853 527 817 Switzerland: +41 (0) 225 4599 60 United Kingdom: +44 (0) 20 3713 5010 United States (toll-free): 1 866 899 4679 United States: +1 (571) 317-3117 Access Code: 728-365-005 Audio PIN: Shown after joining the meeting Meeting ID: 728-365-005 When: Tue Feb 13, 2018 9am ? 10am Central Time (changed) Where: https://www.gotomeeting.com/join/728365005 Calendar: automotive-discussions at lists.linuxfoundation.org Who: * Walt Miner - creator * automotive-discussions at lists.linuxfoundation.org * dcauchy at linuxfoundation.org * Noriaki Fukuyasu * Jan-Simon Moeller * Michele Paolino Event details: https://www.google.com/calendar/event?action=VIEW&eid=MDJiaDM1Yzd0b282NjVzZnRxdWF2bWM3bGggYXV0b21vdGl2ZS1kaXNjdXNzaW9uc0BsaXN0cy5saW51eGZvdW5kYXRpb24ub3Jn&tok=NzIjbGludXhmb3VuZGF0aW9uLm9yZ19pMHJzOGFta20wZmxkZTdrcTV1NGI5dGVmNEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tY2JkMzVmYWM4YzJmMWQyYjBiMTQ1MDc0NTNiODdkZDRkOWU4NDcwZA&ctz=America/Chicago&hl=en Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account automotive-discussions at lists.linuxfoundation.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3751 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3826 bytes Desc: not available URL: From msisov at igalia.com Fri Feb 9 15:12:26 2018 From: msisov at igalia.com (Maksim Sisov) Date: Fri, 09 Feb 2018 17:12:26 +0200 Subject: [agl-discussions] Kernel Panic. In-Reply-To: <16f501a4fea92f6c765b0c4f11513c12@igalia.com> References: <0a0d5c2e-5fbb-c276-4753-b11f60f71f6b@konsulko.com> <16f501a4fea92f6c765b0c4f11513c12@igalia.com> Message-ID: <357b346f1a8aefbe245d05e31130265e@igalia.com> Hi! I'm trying to boot an AGL image compiled from EEL 5.0 for Renesas m3 board. But for some reason I got kernel panic when I booted my board. The error is the following: [ 2.582930] VFS: Cannot open root device "mmcblk1p1" or unknown-block(179,1): error -6 [ 2.590933] Please append a correct "root=" boot option; here are the available partitions: [ 2.599350] b300 7634944 mmcblk1 [ 2.603217] driver: mmcblk [ 2.606037] b360 4096 mmcblk1rpmb [ 2.610245] (driver?) [ 2.612627] b340 8192 mmcblk1boot1 [ 2.616918] (driver?) [ 2.619291] b320 8192 mmcblk1boot0 [ 2.623591] (driver?) [ 2.625977] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,1) [ 2.634459] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.9.0-yocto-standard #1 [ 2.641628] Hardware name: Renesas M3ULCB board based on r8a7796 (DT) [ 2.648098] Call trace: [ 2.650563] [] dump_backtrace+0x0/0x1a0 [ 2.655988] [] show_stack+0x14/0x20 [ 2.661065] [] dump_stack+0x94/0xb8 [ 2.666142] [] panic+0x110/0x278 [ 2.670959] [] mount_block_root+0x184/0x25c [ 2.677963] [] mount_root+0x11c/0x134 [ 2.684417] [] prepare_namespace+0x13c/0x184 [ 2.691476] [] kernel_init_freeable+0x224/0x248 [ 2.698797] [] kernel_init+0x10/0x100 [ 2.705241] [] ret_from_fork+0x10/0x50 [ 2.711762] SMP: stopping secondary CPUs [ 2.716897] Kernel Offset: disabled [ 2.721585] Memory Limit: none [ 2.725836] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,1) I've checked the env, and they looked ok for me. Am I missing something? => printenv baudrate=115200 bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait ro rootfstype=ext4 bootcmd=run load_ker; run load_dtb; booti 0x48080000 - 0x48000000 bootdelay=3 fdt_high=0xffffffffffffffff initrd_high=0xffffffffffffffff load_dtb=ext4load mmc 0:1 0x48000000 /boot/Image-r8a7796-m3ulcb.dtb load_ker=ext4load mmc 0:1 0x48080000 /boot/Image stderr=serial stdin=serial stdout=serial ver=U-Boot 2015.04 (Mar 21 2017 - 18:12:04) Environment size: 459/131068 bytes Best regards, Maksim From loic.collignon at iot.bzh Fri Feb 9 15:14:40 2018 From: loic.collignon at iot.bzh (=?UTF-8?B?TG/Dr2MgQ29sbGlnbm9uIFsgSW9ULmJ6aCBd?=) Date: Fri, 9 Feb 2018 16:14:40 +0100 Subject: [agl-discussions] Kernel Panic. In-Reply-To: <357b346f1a8aefbe245d05e31130265e@igalia.com> References: <0a0d5c2e-5fbb-c276-4753-b11f60f71f6b@konsulko.com> <16f501a4fea92f6c765b0c4f11513c12@igalia.com> <357b346f1a8aefbe245d05e31130265e@igalia.com> Message-ID: Hi! mmcblk1p1 is for situation where you have the kingfisher extension board. Try to change it to mmcblk0p1, when you use only the M3. Regards, Lo?c Collignon [IoT.bzh] 2018-02-09 16:12 GMT+01:00 Maksim Sisov : > Hi! > > I'm trying to boot an AGL image compiled from EEL 5.0 for Renesas m3 > board. But for some reason I got kernel panic when I booted my board. > > The error is the following: > > [ 2.582930] VFS: Cannot open root device "mmcblk1p1" or > unknown-block(179,1): error -6 > [ 2.590933] Please append a correct "root=" boot option; here are the > available partitions: > [ 2.599350] b300 7634944 mmcblk1 [ 2.603217] driver: > mmcblk > [ 2.606037] b360 4096 mmcblk1rpmb [ 2.610245] > (driver?) > [ 2.612627] b340 8192 mmcblk1boot1 [ 2.616918] > (driver?) > [ 2.619291] b320 8192 mmcblk1boot0 [ 2.623591] > (driver?) > [ 2.625977] Kernel panic - not syncing: VFS: Unable to mount root fs > on unknown-block(179,1) > [ 2.634459] CPU: 1 PID: 1 Comm: swapper/0 Not tainted > 4.9.0-yocto-standard #1 > [ 2.641628] Hardware name: Renesas M3ULCB board based on r8a7796 (DT) > [ 2.648098] Call trace: > [ 2.650563] [] dump_backtrace+0x0/0x1a0 > [ 2.655988] [] show_stack+0x14/0x20 > [ 2.661065] [] dump_stack+0x94/0xb8 > [ 2.666142] [] panic+0x110/0x278 > [ 2.670959] [] mount_block_root+0x184/0x25c > [ 2.677963] [] mount_root+0x11c/0x134 > [ 2.684417] [] prepare_namespace+0x13c/0x184 > [ 2.691476] [] kernel_init_freeable+0x224/0x248 > [ 2.698797] [] kernel_init+0x10/0x100 > [ 2.705241] [] ret_from_fork+0x10/0x50 > [ 2.711762] SMP: stopping secondary CPUs > [ 2.716897] Kernel Offset: disabled > [ 2.721585] Memory Limit: none > [ 2.725836] ---[ end Kernel panic - not syncing: VFS: Unable to mount > root fs on unknown-block(179,1) > > I've checked the env, and they looked ok for me. Am I missing something? > > > => printenv > baudrate=115200 > bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait ro > rootfstype=ext4 > bootcmd=run load_ker; run load_dtb; booti 0x48080000 - 0x48000000 > bootdelay=3 > fdt_high=0xffffffffffffffff > initrd_high=0xffffffffffffffff > load_dtb=ext4load mmc 0:1 0x48000000 /boot/Image-r8a7796-m3ulcb.dtb > load_ker=ext4load mmc 0:1 0x48080000 /boot/Image > stderr=serial > stdin=serial > stdout=serial > ver=U-Boot 2015.04 (Mar 21 2017 - 18:12:04) > > Environment size: 459/131068 bytes > > Best regards, > Maksim > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephen.lawrence at renesas.com Fri Feb 9 15:46:51 2018 From: stephen.lawrence at renesas.com (Stephen Lawrence) Date: Fri, 9 Feb 2018 15:46:51 +0000 Subject: [agl-discussions] Kernel Panic. In-Reply-To: <357b346f1a8aefbe245d05e31130265e@igalia.com> References: <0a0d5c2e-5fbb-c276-4753-b11f60f71f6b@konsulko.com> <16f501a4fea92f6c765b0c4f11513c12@igalia.com> <357b346f1a8aefbe245d05e31130265e@igalia.com> Message-ID: Hi > -----Original Message----- > From: automotive-discussions-bounces at lists.linuxfoundation.org > [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On > Behalf Of Maksim Sisov > Sent: 09 February 2018 15:12 > To: automotive-discussions at lists.linuxfoundation.org > Subject: [agl-discussions] Kernel Panic. > > Hi! > > I'm trying to boot an AGL image compiled from EEL 5.0 for Renesas m3 > board. But for some reason I got kernel panic when I booted my board. > [snip] > bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait ro I'm not familiar with the AGL image setup but should it be rw, not ro? Regards Steve From msisov at igalia.com Fri Feb 9 16:48:45 2018 From: msisov at igalia.com (Maksim Sisov) Date: Fri, 09 Feb 2018 18:48:45 +0200 Subject: [agl-discussions] Kernel Panic. In-Reply-To: References: <0a0d5c2e-5fbb-c276-4753-b11f60f71f6b@konsulko.com> <16f501a4fea92f6c765b0c4f11513c12@igalia.com> <357b346f1a8aefbe245d05e31130265e@igalia.com> Message-ID: <8fa1c61b15b81a8a154db83b537d0f98@igalia.com> Hi! On 09.02.2018 17:14, Lo?c Collignon [ IoT.bzh ] wrote: > Hi! > mmcblk1p1 is for situation where you have the kingfisher extension > board. > > Try to change it to mmcblk0p1, when you use only the M3. Thanks! It helped! Regards, Maksim > > Regards, > Lo?c Collignon [IoT.bzh] > 2018-02-09 16:12 GMT+01:00 Maksim Sisov : > >> Hi! >> >> I'm trying to boot an AGL image compiled from EEL 5.0 for Renesas m3 >> board. But for some reason I got kernel panic when I booted my >> board. >> >> The error is the following: >> >> [ 2.582930] VFS: Cannot open root device "mmcblk1p1" or >> unknown-block(179,1): error -6 >> [ 2.590933] Please append a correct "root=" boot option; here are >> the >> available partitions: >> [ 2.599350] b300 7634944 mmcblk1 [ 2.603217] driver: >> mmcblk >> [ 2.606037] b360 4096 mmcblk1rpmb [ 2.610245] >> (driver?) >> [ 2.612627] b340 8192 mmcblk1boot1 [ 2.616918] >> (driver?) >> [ 2.619291] b320 8192 mmcblk1boot0 [ 2.623591] >> (driver?) >> [ 2.625977] Kernel panic - not syncing: VFS: Unable to mount root >> fs >> on unknown-block(179,1) >> [ 2.634459] CPU: 1 PID: 1 Comm: swapper/0 Not tainted >> 4.9.0-yocto-standard #1 >> [ 2.641628] Hardware name: Renesas M3ULCB board based on r8a7796 >> (DT) >> [ 2.648098] Call trace: >> [ 2.650563] [] dump_backtrace+0x0/0x1a0 >> [ 2.655988] [] show_stack+0x14/0x20 >> [ 2.661065] [] dump_stack+0x94/0xb8 >> [ 2.666142] [] panic+0x110/0x278 >> [ 2.670959] [] mount_block_root+0x184/0x25c >> [ 2.677963] [] mount_root+0x11c/0x134 >> [ 2.684417] [] prepare_namespace+0x13c/0x184 >> [ 2.691476] [] kernel_init_freeable+0x224/0x248 >> [ 2.698797] [] kernel_init+0x10/0x100 >> [ 2.705241] [] ret_from_fork+0x10/0x50 >> [ 2.711762] SMP: stopping secondary CPUs >> [ 2.716897] Kernel Offset: disabled >> [ 2.721585] Memory Limit: none >> [ 2.725836] ---[ end Kernel panic - not syncing: VFS: Unable to >> mount >> root fs on unknown-block(179,1) >> >> I've checked the env, and they looked ok for me. Am I missing >> something? >> >> => printenv >> baudrate=115200 >> bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait ro >> rootfstype=ext4 >> bootcmd=run load_ker; run load_dtb; booti 0x48080000 - 0x48000000 >> bootdelay=3 >> fdt_high=0xffffffffffffffff >> initrd_high=0xffffffffffffffff >> load_dtb=ext4load mmc 0:1 0x48000000 /boot/Image-r8a7796-m3ulcb.dtb >> load_ker=ext4load mmc 0:1 0x48080000 /boot/Image >> stderr=serial >> stdin=serial >> stdout=serial >> ver=U-Boot 2015.04 (Mar 21 2017 - 18:12:04) >> >> Environment size: 459/131068 bytes >> >> Best regards, >> Maksim >> _______________________________________________ >> automotive-discussions mailing list >> automotive-discussions at lists.linuxfoundation.org >> > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions >> [1] > > > > Links: > ------ > [1] https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From vishnu.tvrprasad at gmail.com Fri Feb 9 17:50:58 2018 From: vishnu.tvrprasad at gmail.com (vishnu Tadepalli) Date: Fri, 9 Feb 2018 12:50:58 -0500 Subject: [agl-discussions] Kernel Panic Message-ID: Looks like the partitions are not created on eMMC. On Fri, Feb 9, 2018 at 11:48 AM, < automotive-discussions-request at lists.linuxfoundation.org> wrote: > Send automotive-discussions mailing list submissions to > automotive-discussions at lists.linuxfoundation.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.linuxfoundation.org/mailman/listinfo/ > automotive-discussions > > or, via email, send a message with subject or body 'help' to > automotive-discussions-request at lists.linuxfoundation.org > > You can reach the person managing the list at > automotive-discussions-owner at lists.linuxfoundation.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of automotive-discussions digest..." > > > Today's Topics: > > 1. Kernel Panic. (Maksim Sisov) > 2. Re: Kernel Panic. (Lo?c) > 3. Re: Kernel Panic. (Stephen Lawrence) > 4. Re: Kernel Panic. (Maksim Sisov) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 09 Feb 2018 17:12:26 +0200 > From: Maksim Sisov > To: automotive-discussions at lists.linuxfoundation.org > Subject: [agl-discussions] Kernel Panic. > Message-ID: <357b346f1a8aefbe245d05e31130265e at igalia.com> > Content-Type: text/plain; charset=US-ASCII > > Hi! > > I'm trying to boot an AGL image compiled from EEL 5.0 for Renesas m3 > board. But for some reason I got kernel panic when I booted my board. > > The error is the following: > > [ 2.582930] VFS: Cannot open root device "mmcblk1p1" or > unknown-block(179,1): error -6 > [ 2.590933] Please append a correct "root=" boot option; here are the > available partitions: > [ 2.599350] b300 7634944 mmcblk1 [ 2.603217] driver: > mmcblk > [ 2.606037] b360 4096 mmcblk1rpmb [ 2.610245] > (driver?) > [ 2.612627] b340 8192 mmcblk1boot1 [ 2.616918] > (driver?) > [ 2.619291] b320 8192 mmcblk1boot0 [ 2.623591] > (driver?) > [ 2.625977] Kernel panic - not syncing: VFS: Unable to mount root fs > on unknown-block(179,1) > [ 2.634459] CPU: 1 PID: 1 Comm: swapper/0 Not tainted > 4.9.0-yocto-standard #1 > [ 2.641628] Hardware name: Renesas M3ULCB board based on r8a7796 (DT) > [ 2.648098] Call trace: > [ 2.650563] [] dump_backtrace+0x0/0x1a0 > [ 2.655988] [] show_stack+0x14/0x20 > [ 2.661065] [] dump_stack+0x94/0xb8 > [ 2.666142] [] panic+0x110/0x278 > [ 2.670959] [] mount_block_root+0x184/0x25c > [ 2.677963] [] mount_root+0x11c/0x134 > [ 2.684417] [] prepare_namespace+0x13c/0x184 > [ 2.691476] [] kernel_init_freeable+0x224/0x248 > [ 2.698797] [] kernel_init+0x10/0x100 > [ 2.705241] [] ret_from_fork+0x10/0x50 > [ 2.711762] SMP: stopping secondary CPUs > [ 2.716897] Kernel Offset: disabled > [ 2.721585] Memory Limit: none > [ 2.725836] ---[ end Kernel panic - not syncing: VFS: Unable to mount > root fs on unknown-block(179,1) > > I've checked the env, and they looked ok for me. Am I missing something? > > > => printenv > baudrate=115200 > bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait ro > rootfstype=ext4 > bootcmd=run load_ker; run load_dtb; booti 0x48080000 - 0x48000000 > bootdelay=3 > fdt_high=0xffffffffffffffff > initrd_high=0xffffffffffffffff > load_dtb=ext4load mmc 0:1 0x48000000 /boot/Image-r8a7796-m3ulcb.dtb > load_ker=ext4load mmc 0:1 0x48080000 /boot/Image > stderr=serial > stdin=serial > stdout=serial > ver=U-Boot 2015.04 (Mar 21 2017 - 18:12:04) > > Environment size: 459/131068 bytes > > Best regards, > Maksim > > > ------------------------------ > > Message: 2 > Date: Fri, 9 Feb 2018 16:14:40 +0100 > From: Lo?c Collignon [ IoT.bzh ] > To: Maksim Sisov > Cc: automotive-discussions at lists.linuxfoundation.org > Subject: Re: [agl-discussions] Kernel Panic. > Message-ID: > pyCC_w at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi! > mmcblk1p1 is for situation where you have the kingfisher extension board. > Try to change it to mmcblk0p1, when you use only the M3. > > Regards, > Lo?c Collignon [IoT.bzh] > > 2018-02-09 16:12 GMT+01:00 Maksim Sisov : > > > Hi! > > > > I'm trying to boot an AGL image compiled from EEL 5.0 for Renesas m3 > > board. But for some reason I got kernel panic when I booted my board. > > > > The error is the following: > > > > [ 2.582930] VFS: Cannot open root device "mmcblk1p1" or > > unknown-block(179,1): error -6 > > [ 2.590933] Please append a correct "root=" boot option; here are the > > available partitions: > > [ 2.599350] b300 7634944 mmcblk1 [ 2.603217] driver: > > mmcblk > > [ 2.606037] b360 4096 mmcblk1rpmb [ 2.610245] > > (driver?) > > [ 2.612627] b340 8192 mmcblk1boot1 [ 2.616918] > > (driver?) > > [ 2.619291] b320 8192 mmcblk1boot0 [ 2.623591] > > (driver?) > > [ 2.625977] Kernel panic - not syncing: VFS: Unable to mount root fs > > on unknown-block(179,1) > > [ 2.634459] CPU: 1 PID: 1 Comm: swapper/0 Not tainted > > 4.9.0-yocto-standard #1 > > [ 2.641628] Hardware name: Renesas M3ULCB board based on r8a7796 (DT) > > [ 2.648098] Call trace: > > [ 2.650563] [] dump_backtrace+0x0/0x1a0 > > [ 2.655988] [] show_stack+0x14/0x20 > > [ 2.661065] [] dump_stack+0x94/0xb8 > > [ 2.666142] [] panic+0x110/0x278 > > [ 2.670959] [] mount_block_root+0x184/0x25c > > [ 2.677963] [] mount_root+0x11c/0x134 > > [ 2.684417] [] prepare_namespace+0x13c/0x184 > > [ 2.691476] [] kernel_init_freeable+0x224/0x248 > > [ 2.698797] [] kernel_init+0x10/0x100 > > [ 2.705241] [] ret_from_fork+0x10/0x50 > > [ 2.711762] SMP: stopping secondary CPUs > > [ 2.716897] Kernel Offset: disabled > > [ 2.721585] Memory Limit: none > > [ 2.725836] ---[ end Kernel panic - not syncing: VFS: Unable to mount > > root fs on unknown-block(179,1) > > > > I've checked the env, and they looked ok for me. Am I missing something? > > > > > > => printenv > > baudrate=115200 > > bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait ro > > rootfstype=ext4 > > bootcmd=run load_ker; run load_dtb; booti 0x48080000 - 0x48000000 > > bootdelay=3 > > fdt_high=0xffffffffffffffff > > initrd_high=0xffffffffffffffff > > load_dtb=ext4load mmc 0:1 0x48000000 /boot/Image-r8a7796-m3ulcb.dtb > > load_ker=ext4load mmc 0:1 0x48080000 /boot/Image > > stderr=serial > > stdin=serial > > stdout=serial > > ver=U-Boot 2015.04 (Mar 21 2017 - 18:12:04) > > > > Environment size: 459/131068 bytes > > > > Best regards, > > Maksim > > _______________________________________________ > > automotive-discussions mailing list > > automotive-discussions at lists.linuxfoundation.org > > https://lists.linuxfoundation.org/mailman/listinfo/ > automotive-discussions > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: discussions/attachments/20180209/d462ebec/attachment-0001.html> > > ------------------------------ > > Message: 3 > Date: Fri, 9 Feb 2018 15:46:51 +0000 > From: Stephen Lawrence > To: Maksim Sisov > Cc: "automotive-discussions at lists.linuxfoundation.org" > > Subject: Re: [agl-discussions] Kernel Panic. > Message-ID: > apcprd06.prod.outlook.com> > > Content-Type: text/plain; charset="us-ascii" > > Hi > > > -----Original Message----- > > From: automotive-discussions-bounces at lists.linuxfoundation.org > > [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On > > Behalf Of Maksim Sisov > > Sent: 09 February 2018 15:12 > > To: automotive-discussions at lists.linuxfoundation.org > > Subject: [agl-discussions] Kernel Panic. > > > > Hi! > > > > I'm trying to boot an AGL image compiled from EEL 5.0 for Renesas m3 > > board. But for some reason I got kernel panic when I booted my board. > > > > [snip] > > > bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait ro > > I'm not familiar with the AGL image setup but should it be rw, not ro? > > Regards > > Steve > > > ------------------------------ > > Message: 4 > Date: Fri, 09 Feb 2018 18:48:45 +0200 > From: Maksim Sisov > To: Lo?c Collignon [ IoT.bzh ] > Cc: automotive-discussions at lists.linuxfoundation.org > Subject: Re: [agl-discussions] Kernel Panic. > Message-ID: <8fa1c61b15b81a8a154db83b537d0f98 at igalia.com> > Content-Type: text/plain; charset=UTF-8 > > Hi! > > On 09.02.2018 17:14, Lo?c Collignon [ IoT.bzh ] wrote: > > Hi! > > mmcblk1p1 is for situation where you have the kingfisher extension > > board. > > > > Try to change it to mmcblk0p1, when you use only the M3. > > Thanks! It helped! > > Regards, > Maksim > > > > Regards, > > Lo?c Collignon [IoT.bzh] > > 2018-02-09 16:12 GMT+01:00 Maksim Sisov : > > > >> Hi! > >> > >> I'm trying to boot an AGL image compiled from EEL 5.0 for Renesas m3 > >> board. But for some reason I got kernel panic when I booted my > >> board. > >> > >> The error is the following: > >> > >> [ 2.582930] VFS: Cannot open root device "mmcblk1p1" or > >> unknown-block(179,1): error -6 > >> [ 2.590933] Please append a correct "root=" boot option; here are > >> the > >> available partitions: > >> [ 2.599350] b300 7634944 mmcblk1 [ 2.603217] driver: > >> mmcblk > >> [ 2.606037] b360 4096 mmcblk1rpmb [ 2.610245] > >> (driver?) > >> [ 2.612627] b340 8192 mmcblk1boot1 [ 2.616918] > >> (driver?) > >> [ 2.619291] b320 8192 mmcblk1boot0 [ 2.623591] > >> (driver?) > >> [ 2.625977] Kernel panic - not syncing: VFS: Unable to mount root > >> fs > >> on unknown-block(179,1) > >> [ 2.634459] CPU: 1 PID: 1 Comm: swapper/0 Not tainted > >> 4.9.0-yocto-standard #1 > >> [ 2.641628] Hardware name: Renesas M3ULCB board based on r8a7796 > >> (DT) > >> [ 2.648098] Call trace: > >> [ 2.650563] [] dump_backtrace+0x0/0x1a0 > >> [ 2.655988] [] show_stack+0x14/0x20 > >> [ 2.661065] [] dump_stack+0x94/0xb8 > >> [ 2.666142] [] panic+0x110/0x278 > >> [ 2.670959] [] mount_block_root+0x184/0x25c > >> [ 2.677963] [] mount_root+0x11c/0x134 > >> [ 2.684417] [] prepare_namespace+0x13c/0x184 > >> [ 2.691476] [] kernel_init_freeable+0x224/0x248 > >> [ 2.698797] [] kernel_init+0x10/0x100 > >> [ 2.705241] [] ret_from_fork+0x10/0x50 > >> [ 2.711762] SMP: stopping secondary CPUs > >> [ 2.716897] Kernel Offset: disabled > >> [ 2.721585] Memory Limit: none > >> [ 2.725836] ---[ end Kernel panic - not syncing: VFS: Unable to > >> mount > >> root fs on unknown-block(179,1) > >> > >> I've checked the env, and they looked ok for me. Am I missing > >> something? > >> > >> => printenv > >> baudrate=115200 > >> bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait ro > >> rootfstype=ext4 > >> bootcmd=run load_ker; run load_dtb; booti 0x48080000 - 0x48000000 > >> bootdelay=3 > >> fdt_high=0xffffffffffffffff > >> initrd_high=0xffffffffffffffff > >> load_dtb=ext4load mmc 0:1 0x48000000 /boot/Image-r8a7796-m3ulcb.dtb > >> load_ker=ext4load mmc 0:1 0x48080000 /boot/Image > >> stderr=serial > >> stdin=serial > >> stdout=serial > >> ver=U-Boot 2015.04 (Mar 21 2017 - 18:12:04) > >> > >> Environment size: 459/131068 bytes > >> > >> Best regards, > >> Maksim > >> _______________________________________________ > >> automotive-discussions mailing list > >> automotive-discussions at lists.linuxfoundation.org > >> > > https://lists.linuxfoundation.org/mailman/listinfo/ > automotive-discussions > >> [1] > > > > > > > > Links: > > ------ > > [1] https://lists.linuxfoundation.org/mailman/listinfo/ > automotive-discussions > > > ------------------------------ > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > > > End of automotive-discussions Digest, Vol 61, Issue 15 > ****************************************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dominig.arfoll at fridu.net Fri Feb 9 19:10:10 2018 From: dominig.arfoll at fridu.net (Dominig ar Foll (Intel Open Source)) Date: Fri, 9 Feb 2018 20:10:10 +0100 Subject: [agl-discussions] Network boot - Intel - nbd >= V3.10 Message-ID: <585cec73-1ea1-310e-5867-76bef24271f5@fridu.net> An HTML attachment was scrubbed... URL: From jsmoeller at linuxfoundation.org Fri Feb 9 19:29:38 2018 From: jsmoeller at linuxfoundation.org (Jan-Simon =?ISO-8859-1?Q?M=F6ller?=) Date: Fri, 09 Feb 2018 20:29:38 +0100 Subject: [agl-discussions] Network boot - Intel - nbd >= V3.10 In-Reply-To: <585cec73-1ea1-310e-5867-76bef24271f5@fridu.net> References: <585cec73-1ea1-310e-5867-76bef24271f5@fridu.net> Message-ID: <4585022.XecPY7zdSi@elrond> Am Freitag, 9. Februar 2018, 20:10:10 CET schrieb Dominig ar Foll (Intel Open Source): > Good evening, > > I have been surprisingly lucky as my network boot now works on my Intel > board this Friday at only 20:00 local time. I will publish a howto after > the weekend but I would like to open a short discussion on which nbe-client > to use. > > nbd protocol as evolved quite a while ago but since the release 3.10, the > legacy mode is not supported any more. On the other side the busy box > nbd-client does not support the new protocol. The official nbd client is > supposed (but I cannot verify it) to support the old and the new protocol. > > Distro in general provides the official nbd server which is now at release > 3.10 or more. I know that alternative packages such as xnbd still support > the old protocol but - xnbd is not available by default for many distro > (including mine : OpenSUSE) - it"s just a matter of time before the old > protocol will be also dropped by alternative nbd packages - in case of an > IT enforced controled environment, using the default nbd will likely be the > only option. The LAVA automation relies on xnbd-server. xnbd-server is a standard package in debian/ubuntu and available in the default repos. That being said: if we change one side, it requires an upstream change in LAVA with the needed transition period. The good thing is that client side in the initramfs is a userspace application. So we can support both and evaluate a switch on the kernel cmdline (e.g. nbd.v3=1). TLDR: Patches welcome to the initrd mechanism to support multiple clients but make it a runtime selection. Best, Jan-Simon M?ller From matt.ranostay at konsulko.com Fri Feb 9 22:58:18 2018 From: matt.ranostay at konsulko.com (Matt Ranostay) Date: Fri, 9 Feb 2018 14:58:18 -0800 Subject: [agl-discussions] GPLv2 handling In-Reply-To: <1893515.ueZbnqy5sa@elrond> References: <553cc97c-3e65-4bf5-af0a-7d633cea6d90@xevo.com> <1893515.ueZbnqy5sa@elrond> Message-ID: On Thu, Feb 8, 2018 at 2:39 PM, Jan-Simon M?ller wrote: > Am Donnerstag, 8. Februar 2018, 22:33:19 CET schrieb Martin Kelly: >> Hi, >> >> I noticed we recently started pulling in the meta-gplv2 layer for >> agl-demo and defaulting to its recipes in the AGL distro settings. >> Although I can see the reasoning for this, it also breaks a number of >> recipes because what's in meta-gplv2 is very old (e.g. readline 5 vs >> readline 7). I noticed this breakage when trying to build networkmanager >> (which needs at least readline 6), but I'm sure there are many other >> breakages because of such old recipes. >> >> I'm wondering if anyone has objections to making this all controlled at >> the top-level, while preserving the current GPLv2 default. >> >> My first thoughts on how to do this are: >> >> - An AGL feature called "agl-demo-gplv3" that would add in agl-demo but >> not meta-gplv2. >> - A DISTRO_FEATURE "gplv3", unset by default. If it is not set, then we >> make the PREFERRED_VERSION for various libraries default to gplv2 >> versions in our distro settings. > > Yes, right now its global. In general ack, that a switch would be good. > > We might have to be a little more specific (e.g. no gplv3 on _class-target but > allow on _class-nativesdk or _class-native ). > > @Matt: thoughts ? suggestions ? > That seems like a good idea if we run into more failures. But do note that networkmanager is an on-device package and can't be using a GPLv3 version of readline.Likely if networkmanager is needed on the device you will need to add something like this bbappend for gdb -> https://gerrit.automotivelinux.org/gerrit/#/c/13313/ Without readline you lose tab-completion but it shouldn't cause too much lose of functionality. > Best, > Jan-Simon > > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From srinath.duraisamy at intel.com Sat Feb 10 02:45:23 2018 From: srinath.duraisamy at intel.com (Duraisamy, Srinath) Date: Sat, 10 Feb 2018 02:45:23 +0000 Subject: [agl-discussions] Naviagation app with maps Message-ID: Hi, I would like to demo AGL with maps working. I got to know it supports only Japan and UK maps. But how can I download the maps and see the app working ?? It would be very helpul, if you can provide the steps or document about it. Thanks Srinath -------------- next part -------------- An HTML attachment was scrubbed... URL: From dominig.arfoll at fridu.net Mon Feb 12 07:33:24 2018 From: dominig.arfoll at fridu.net (Dominig ar Foll (Intel Open Source)) Date: Mon, 12 Feb 2018 08:33:24 +0100 Subject: [agl-discussions] Network boot - Intel - nbd >= V3.10 In-Reply-To: <4585022.XecPY7zdSi@elrond> References: <585cec73-1ea1-310e-5867-76bef24271f5@fridu.net> <4585022.XecPY7zdSi@elrond> Message-ID: Le 09/02/2018 ? 20:29, Jan-Simon M?ller a ?crit?: > > The LAVA automation relies on xnbd-server. xnbd-server is a standard package > in debian/ubuntu and available in the default repos. > > That being said: if we change one side, it > requires an upstream change in LAVA with the needed transition period. > > The good thing is that client side in the initramfs is a userspace > application. So we can support both and evaluate a switch on the kernel > cmdline (e.g. nbd.v3=1). I guess that the first step would be to check that nbd client >=3.1 really supports the legacy mode as advertised. If that would be the case, it would be simplier. > TLDR: > Patches welcome to the initrd mechanism to support multiple clients but make > it a runtime selection. Yes, I would expect so, but would be simpler if possible to avoid :-) -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre From jsmoeller at linuxfoundation.org Mon Feb 12 08:50:05 2018 From: jsmoeller at linuxfoundation.org (Jan-Simon =?ISO-8859-1?Q?M=F6ller?=) Date: Mon, 12 Feb 2018 09:50:05 +0100 Subject: [agl-discussions] Network boot - Intel - nbd >= V3.10 In-Reply-To: References: <585cec73-1ea1-310e-5867-76bef24271f5@fridu.net> <4585022.XecPY7zdSi@elrond> Message-ID: <3724514.Q3sUoWeMpg@elrond> Am Montag, 12. Februar 2018, 08:33:24 CET schrieb Dominig ar Foll (Intel Open Source): > > > > The good thing is that client side in the initramfs is a userspace > > application. So we can support both and evaluate a switch on the kernel > > cmdline (e.g. nbd.v3=1). > > I guess that the first step would be to check that nbd client >=3.1 > really supports the legacy mode as advertised. > If that would be the case, it would be simplier. When meta-netboot was done, we evaluated the available implementations and chose xnbd ( https://bitbucket.org/hirofuchi/xnbd/wiki/Home ). There are many (partially in-)compatible implementations for 'nbd' (see https://bitbucket.org/hirofuchi/xnbd/wiki/Home#!links ). E.g. there seems to be now an nbdkit which sounds interesting. Or even nbd-http seems cool (reading straight from http). E.g. boot directly from our images on the DL-server. We can't ensure all servers are in every host distro out of the box. So we need to choose. > > TLDR: > > Patches welcome to the initrd mechanism to support multiple clients but > > make it a runtime selection. > > Yes, I would expect so, but would be simpler if possible to avoid :-) Yes, if there is a more compatible *client* supporting more servers, sure. Could you try xnbd-server with your client implementation and provide some feedback, please ? Best regards, Jan-Simon From dominig.arfoll at fridu.net Mon Feb 12 10:26:38 2018 From: dominig.arfoll at fridu.net (Dominig ar Foll (Intel Open Source)) Date: Mon, 12 Feb 2018 11:26:38 +0100 Subject: [agl-discussions] Naviagation app with maps In-Reply-To: References: Message-ID: An HTML attachment was scrubbed... URL: From jlu at pengutronix.de Mon Feb 12 16:40:20 2018 From: jlu at pengutronix.de (Jan =?ISO-8859-1?Q?L=FCbbe?=) Date: Mon, 12 Feb 2018 17:40:20 +0100 Subject: [agl-discussions] ivi-shell layer visibility problem Message-ID: <1518453620.6988.45.camel@pengutronix.de> Hi, I've been trying to run the 5.0.1 demo on an i.MX6 with etnaviv. After updating libdrm, gstreamer, mesa, meson and wayland to the versions in OE rocko or master, wayland-ivi-extension to 2.1 and finally agl- service-windowmanager-2017 to master it mostly works. One problem I see is that the layer visibilities don't seem to work consistently: 1. On some boots, the UI is invisible and only "LayerManagerControl set surface 1 visibility" makes it show up. 2. Even on "good" boots, if I then start an app (which works fine), I can't switch back to the home screen. Running "LayerManagerControl set layer 1001 visibility 0" makes it visible again. So it seems that the window manager (?) is not handling visibility correctly in all cases. Is that a known problem? Also, is there some documentation on how it is supposed to work? Best regards, Jan L?bbe -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | From mkelly at xevo.com Mon Feb 12 19:11:04 2018 From: mkelly at xevo.com (Martin Kelly) Date: Mon, 12 Feb 2018 11:11:04 -0800 Subject: [agl-discussions] GPLv2 handling In-Reply-To: <1893515.ueZbnqy5sa@elrond> References: <553cc97c-3e65-4bf5-af0a-7d633cea6d90@xevo.com> <1893515.ueZbnqy5sa@elrond> Message-ID: On 02/08/2018 02:39 PM, Jan-Simon M?ller wrote: > Am Donnerstag, 8. Februar 2018, 22:33:19 CET schrieb Martin Kelly: >> Hi, >> >> I noticed we recently started pulling in the meta-gplv2 layer for >> agl-demo and defaulting to its recipes in the AGL distro settings. >> Although I can see the reasoning for this, it also breaks a number of >> recipes because what's in meta-gplv2 is very old (e.g. readline 5 vs >> readline 7). I noticed this breakage when trying to build networkmanager >> (which needs at least readline 6), but I'm sure there are many other >> breakages because of such old recipes. >> >> I'm wondering if anyone has objections to making this all controlled at >> the top-level, while preserving the current GPLv2 default. >> >> My first thoughts on how to do this are: >> >> - An AGL feature called "agl-demo-gplv3" that would add in agl-demo but >> not meta-gplv2. >> - A DISTRO_FEATURE "gplv3", unset by default. If it is not set, then we >> make the PREFERRED_VERSION for various libraries default to gplv2 >> versions in our distro settings. > > Yes, right now its global. In general ack, that a switch would be good. > > We might have to be a little more specific (e.g. no gplv3 on _class-target but > allow on _class-nativesdk or _class-native ). > > @Matt: thoughts ? suggestions ? > > Best, > Jan-Simon > > Matt, thoughts? From mkelly at xevo.com Mon Feb 12 21:04:02 2018 From: mkelly at xevo.com (Martin Kelly) Date: Mon, 12 Feb 2018 13:04:02 -0800 Subject: [agl-discussions] GPLv2 handling In-Reply-To: References: <553cc97c-3e65-4bf5-af0a-7d633cea6d90@xevo.com> <1893515.ueZbnqy5sa@elrond> Message-ID: On 02/12/2018 11:11 AM, Martin Kelly wrote: > On 02/08/2018 02:39 PM, Jan-Simon M?ller wrote: >> Am Donnerstag, 8. Februar 2018, 22:33:19 CET schrieb Martin Kelly: >>> Hi, >>> >>> I noticed we recently started pulling in the meta-gplv2 layer for >>> agl-demo and defaulting to its recipes in the AGL distro settings. >>> Although I can see the reasoning for this, it also breaks a number of >>> recipes because what's in meta-gplv2 is very old (e.g. readline 5 vs >>> readline 7). I noticed this breakage when trying to build networkmanager >>> (which needs at least readline 6), but I'm sure there are many other >>> breakages because of such old recipes. >>> >>> I'm wondering if anyone has objections to making this all controlled at >>> the top-level, while preserving the current GPLv2 default. >>> >>> My first thoughts on how to do this are: >>> >>> - An AGL feature called "agl-demo-gplv3" that would add in agl-demo but >>> not meta-gplv2. >>> - A DISTRO_FEATURE "gplv3", unset by default. If it is not set, then we >>> make the PREFERRED_VERSION for various libraries default to gplv2 >>> versions in our distro settings. >> >> Yes, right now its global.? In general ack, that a switch would be good. >> >> We might have to be a little more specific (e.g. no gplv3 on >> _class-target but >> allow on _class-nativesdk or _class-native ). >> >> @Matt: thoughts ? suggestions ? >> >> Best, >> Jan-Simon >> > Matt, thoughts? Perhaps we can move the discussion over to code :). I have two CR's out now: https://gerrit.automotivelinux.org/gerrit/#/c/13405/ https://gerrit.automotivelinux.org/gerrit/#/c/13407/ From jsmoeller at linuxfoundation.org Mon Feb 12 21:14:41 2018 From: jsmoeller at linuxfoundation.org (Jan-Simon =?ISO-8859-1?Q?M=F6ller?=) Date: Mon, 12 Feb 2018 22:14:41 +0100 Subject: [agl-discussions] Electric Eel v5.0.1 build and testreport available Message-ID: <8187104.0q0psdO8nB@samweis.auenland.lan> Hi all ! A build of EE v5.0.1 is available at https://download.automotivelinux.org/AGL/release/eel/5.0.1/ The tests in LAVA ran and the report is here: https://wiki.automotivelinux.org/agl-distro/releases/5.0.1/test/summary -- Sincerely yours, Jan-Simon M?ller jsmoeller at linuxfoundation.org From srinath.duraisamy at intel.com Tue Feb 13 00:37:58 2018 From: srinath.duraisamy at intel.com (Duraisamy, Srinath) Date: Tue, 13 Feb 2018 00:37:58 +0000 Subject: [agl-discussions] Naviagation app with maps In-Reply-To: References: Message-ID: Thanks for the steps. It worked. Regards Srinath From: automotive-discussions-bounces at lists.linuxfoundation.org [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On Behalf Of Dominig ar Foll (Intel Open Source) Sent: Monday, February 12, 2018 2:27 AM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] Naviagation app with maps Le 10/02/2018 ? 03:45, Duraisamy, Srinath a ?crit : Hi, I would like to demo AGL with maps working. I got to know it supports only Japan and UK maps. But how can I download the maps and see the app working ?? It would be very helpul, if you can provide the steps or document about it. Good idea. I have added a chapter in the Troubleshooting section, but it will requires 24 hours before being visible on the Doc web site. In the mean time please find here a short HowTo. a) Method 1 on target download. =========================== 1) Install the new image on the target 2) boot a first time to install the demo Apps 3) execute the scripts - /usr/AGL/apps/download_mapdata_uk.sh or - /usr/AGL/apps/download_mapdata_jp.sh b) At image creation ================ Download on your build machine the desire maps and uncompress them on your target image before 1st boot. Quicker and does not require to have the network enabled on the target device. Map can be found here. http://agl.wismobi.com/data/japan_TR9/navi_data.tar.gz http://agl.wismobi.com/data/UnitedKingdom_TR9/navi_data_UK.tar.gz Once that you have built your image on the SD card, uncompress the desired map in on the SD card at the position /YourMountPoint/var/mapdata (YourMountPoint will vary with your build system). Thanks Srinath _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsmoeller at linuxfoundation.org Tue Feb 13 13:22:29 2018 From: jsmoeller at linuxfoundation.org (jsmoeller at linuxfoundation.org) Date: Tue, 13 Feb 2018 13:22:29 +0000 Subject: [agl-discussions] Aktualisierte Einladung: EG-CIAT Biweekly Call - Alle 2 Wochen von 14:00 bis 15:00 am Dienstag von Di 19. Jul. 2016 bis Di 27. Feb. (MESZ) (automotive-discussions@lists.linuxfoundation.org) Message-ID: <94eb2c1a6356edfe28056517e269@google.com> Dieser Termin wurde ge?ndert. Titel: EG-CIAT Biweekly Call Please join my meeting from your computer, tablet or smartphone. https://global.gotomeeting.com/join/997304269 You can also dial in using your phone. United States (Toll Free): 1 877 568 4106 United States: +1 (571) 317-3129 Access Code: 997-304-269 More phone numbers France (Toll Free): 0 805 541 047 France: +33 170 950 594 Germany (Toll Free): 0 800 723 5270 Germany: +49 692 5736 7210 First GoToMeeting? Try a test session: http://help.citrix.com/getready Wann: Alle 2 Wochen von 14:00 bis 15:00 am Dienstag von Di 19. Jul. 2016 bis Di 27. Feb. Berlin (ge?ndert) Wo: https://global.gotomeeting.com/join/997304269 Kalender: automotive-discussions at lists.linuxfoundation.org Wer * Walt Miner- Veranstalter * automotive-discussions at lists.linuxfoundation.org * Noriaki Fukuyasu * dcauchy at linuxfoundation.org Termininformationen: https://www.google.com/calendar/event?action=VIEW&eid=cXVhbnZqYTBrMWZwMDFsZGtnM3RiOG01b2cgYXV0b21vdGl2ZS1kaXNjdXNzaW9uc0BsaXN0cy5saW51eGZvdW5kYXRpb24ub3Jn&tok=NzIjbGludXhmb3VuZGF0aW9uLm9yZ19pMHJzOGFta20wZmxkZTdrcTV1NGI5dGVmNEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tNjBjYWIxNmY5MjJjMTc4ZDFlMDgxOWI0ODI2YjcwNTUzZTRiYTIxYg&ctz=Europe/Berlin&hl=de Einladung von Google Kalender: https://www.google.com/calendar/ Sie erhalten diese E-Mail unter automotive-discussions at lists.linuxfoundation.org, da Sie ein Gast bei diesem Termin sind. Lehnen Sie diesen Termin ab, um keine weiteren Informationen zu diesem Termin zu erhalten. Sie k?nnen auch unter https://www.google.com/calendar/ ein Google-Konto erstellen und Ihre Benachrichtigungseinstellungen f?r Ihren gesamten Kalender steuern. Wenn Sie diese Einladung weiterleiten, kann jeder Empf?nger Ihre Antwort auf die Einladung ?ndern. Weitere Informationen finden Sie unter https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3279 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3355 bytes Desc: not available URL: From jsmoeller at linuxfoundation.org Tue Feb 13 13:22:29 2018 From: jsmoeller at linuxfoundation.org (jsmoeller at linuxfoundation.org) Date: Tue, 13 Feb 2018 13:22:29 +0000 Subject: [agl-discussions] Aktualisierte Einladung: EG-CIAT Biweekly Call - Alle 2 Wochen von 14:00 bis 15:00 am Dienstag (MEZ) (automotive-discussions@lists.linuxfoundation.org) Message-ID: <001a114cd100ebcf7c056517e249@google.com> Dieser Termin wurde ge?ndert. Titel: EG-CIAT Biweekly Call Please join my meeting from your computer, tablet or smartphone. https://global.gotomeeting.com/join/997304269 You can also dial in using your phone. United States (Toll Free): 1 877 568 4106 United States: +1 (571) 317-3129 Access Code: 997-304-269 More phone numbers France (Toll Free): 0 805 541 047 France: +33 170 950 594 Germany (Toll Free): 0 800 723 5270 Germany: +49 692 5736 7210 First GoToMeeting? Try a test session: http://help.citrix.com/getready Wann: Alle 2 Wochen von 14:00 bis 15:00 am Dienstag Berlin (ge?ndert) Wo: https://global.gotomeeting.com/join/997304269 Kalender: automotive-discussions at lists.linuxfoundation.org Wer * Jan-Simon Moeller- Veranstalter * Walt Miner * automotive-discussions at lists.linuxfoundation.org * dcauchy at linuxfoundation.org * Noriaki Fukuyasu Termininformationen: https://www.google.com/calendar/event?action=VIEW&eid=NDBzc3Jna3RmZWdlYWZsMmpiYmp1Z3Nzc3MgYXV0b21vdGl2ZS1kaXNjdXNzaW9uc0BsaXN0cy5saW51eGZvdW5kYXRpb24ub3Jn&tok=NzIjbGludXhmb3VuZGF0aW9uLm9yZ19pMHJzOGFta20wZmxkZTdrcTV1NGI5dGVmNEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tYTIxZDE4M2U4M2MwMTQzNTJhN2UxNTIzMGM0NGFiNWU4MWJmNzA1NA&ctz=Europe/Berlin&hl=de Einladung von Google Kalender: https://www.google.com/calendar/ Sie erhalten diese E-Mail unter automotive-discussions at lists.linuxfoundation.org, da Sie ein Gast bei diesem Termin sind. Lehnen Sie diesen Termin ab, um keine weiteren Informationen zu diesem Termin zu erhalten. Sie k?nnen auch unter https://www.google.com/calendar/ ein Google-Konto erstellen und Ihre Benachrichtigungseinstellungen f?r Ihren gesamten Kalender steuern. Wenn Sie diese Einladung weiterleiten, kann jeder Empf?nger Ihre Antwort auf die Einladung ?ndern. Weitere Informationen finden Sie unter https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3351 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3429 bytes Desc: not available URL: From jsmoeller at linuxfoundation.org Tue Feb 13 13:22:29 2018 From: jsmoeller at linuxfoundation.org (jsmoeller at linuxfoundation.org) Date: Tue, 13 Feb 2018 13:22:29 +0000 Subject: [agl-discussions] Aktualisierte Einladung: EG-CIAT Biweekly Call - Alle 2 Wochen von 14:00 bis 15:00 am Dienstag von Di 25. Apr. 2017 bis Di 27. Feb. (MESZ) (automotive-discussions@lists.linuxfoundation.org) Message-ID: <001a114b9424e9a7ae056517e291@google.com> Dieser Termin wurde ge?ndert. Titel: EG-CIAT Biweekly Call Please join my meeting from your computer, tablet or smartphone. https://global.gotomeeting.com/join/997304269 You can also dial in using your phone. United States (Toll Free): 1 877 568 4106 United States: +1 (571) 317-3129 Access Code: 997-304-269 More phone numbers France (Toll Free): 0 805 541 047 France: +33 170 950 594 Germany (Toll Free): 0 800 723 5270 Germany: +49 692 5736 7210 First GoToMeeting? Try a test session: http://help.citrix.com/getready Wann: Alle 2 Wochen von 14:00 bis 15:00 am Dienstag von Di 25. Apr. 2017 bis Di 27. Feb. Berlin (ge?ndert) Wo: https://global.gotomeeting.com/join/997304269 Kalender: automotive-discussions at lists.linuxfoundation.org Wer * Walt Miner- Veranstalter * dcauchy at linuxfoundation.org * Noriaki Fukuyasu * automotive-discussions at lists.linuxfoundation.org Termininformationen: https://www.google.com/calendar/event?action=VIEW&eid=cXVhbnZqYTBrMWZwMDFsZGtnM3RiOG01b2dfUjIwMTcwNDI1VDEyMDAwMCBhdXRvbW90aXZlLWRpc2N1c3Npb25zQGxpc3RzLmxpbnV4Zm91bmRhdGlvbi5vcmc&tok=NzIjbGludXhmb3VuZGF0aW9uLm9yZ19pMHJzOGFta20wZmxkZTdrcTV1NGI5dGVmNEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tNjM2Mzg0MDhiNjYyNjFjZDlkOGQyMGE3NjMwYzhlMGYyMGNiNTlmZg&ctz=Europe/Berlin&hl=de Einladung von Google Kalender: https://www.google.com/calendar/ Sie erhalten diese E-Mail unter automotive-discussions at lists.linuxfoundation.org, da Sie ein Gast bei diesem Termin sind. Lehnen Sie diesen Termin ab, um keine weiteren Informationen zu diesem Termin zu erhalten. Sie k?nnen auch unter https://www.google.com/calendar/ ein Google-Konto erstellen und Ihre Benachrichtigungseinstellungen f?r Ihren gesamten Kalender steuern. Wenn Sie diese Einladung weiterleiten, kann jeder Empf?nger Ihre Antwort auf die Einladung ?ndern. Weitere Informationen finden Sie unter https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3364 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3442 bytes Desc: not available URL: From wminer at linuxfoundation.org Tue Feb 13 15:59:46 2018 From: wminer at linuxfoundation.org (wminer at linuxfoundation.org) Date: Tue, 13 Feb 2018 15:59:46 +0000 Subject: [agl-discussions] Updated invitation: EG Virtualization @ Fri Feb 16, 2018 7am - 8am (CST) (automotive-discussions@lists.linuxfoundation.org) Message-ID: <089e08313d606ddcea05651a1586@google.com> This event has been changed. Title: EG Virtualization 1. Please join my meeting. https://global.gotomeeting.com/join/728365005 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. Australia: +61 2 9091 7603 Austria: +43 1 2530 22500 Belgium: +32 (0) 27 00 6375 Canada (toll-free): 1 888 299 1889 Canada: +1 (647) 497-9373 Denmark: +45 32 72 03 69 Finland: +358 (0) 923 17 0555 France: +33 (0) 170 950 585 Germany: +49 (0) 692 5736 7208 India (toll-free): 000 800 852 1424 Ireland: +353 (0) 15 255 598 Italy: +39 0 699 26 68 65 Japan (toll-free): 0 120 352 900 Korea, Republic of (toll-free): 0806180880 Netherlands: +31 (0) 707 709 520 New Zealand: +64 9 887 3469 Norway: +47 23 96 01 18 Spain: +34 932 75 1230 Sweden: +46 (0) 853 527 817 Switzerland: +41 (0) 225 4599 60 United Kingdom: +44 (0) 20 3713 5010 United States (toll-free): 1 866 899 4679 United States: +1 (571) 317-3117 Access Code: 728-365-005 Audio PIN: Shown after joining the meeting Meeting ID: 728-365-005 When: Fri Feb 16, 2018 7am ? 8am Central Time (changed) Where: https://www.gotomeeting.com/join/728365005 Calendar: automotive-discussions at lists.linuxfoundation.org Who: * Walt Miner - creator * automotive-discussions at lists.linuxfoundation.org * dcauchy at linuxfoundation.org * Noriaki Fukuyasu * Jan-Simon Moeller * Michele Paolino Event details: https://www.google.com/calendar/event?action=VIEW&eid=MDJiaDM1Yzd0b282NjVzZnRxdWF2bWM3bGggYXV0b21vdGl2ZS1kaXNjdXNzaW9uc0BsaXN0cy5saW51eGZvdW5kYXRpb24ub3Jn&tok=NzIjbGludXhmb3VuZGF0aW9uLm9yZ19pMHJzOGFta20wZmxkZTdrcTV1NGI5dGVmNEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tY2JkMzVmYWM4YzJmMWQyYjBiMTQ1MDc0NTNiODdkZDRkOWU4NDcwZA&ctz=America/Chicago&hl=en Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account automotive-discussions at lists.linuxfoundation.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3751 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3826 bytes Desc: not available URL: From jose.bollo at iot.bzh Tue Feb 13 16:31:29 2018 From: jose.bollo at iot.bzh (=?UTF-8?B?Sm9zw6k=?= Bollo) Date: Tue, 13 Feb 2018 17:31:29 +0100 Subject: [agl-discussions] ivi-shell layer visibility problem In-Reply-To: <1518453620.6988.45.camel@pengutronix.de> References: <1518453620.6988.45.camel@pengutronix.de> Message-ID: <20180213173129.4e84d928@d-jobol.iot.bzh> On Mon, 12 Feb 2018 17:40:20 +0100 Jan L?bbe wrote: > Hi, > > I've been trying to run the 5.0.1 demo on an i.MX6 with etnaviv. After > updating libdrm, gstreamer, mesa, meson and wayland to the versions in > OE rocko or master, wayland-ivi-extension to 2.1 and finally agl- > service-windowmanager-2017 to master it mostly works. > > One problem I see is that the layer visibilities don't seem to work > consistently: > 1. On some boots, the UI is invisible and only "LayerManagerControl > set surface 1 visibility" makes it show up. > 2. Even on "good" boots, if I then start an app (which works fine), I > can't switch back to the home screen. Running "LayerManagerControl set > layer 1001 visibility 0" makes it visible again. > > So it seems that the window manager (?) is not handling visibility > correctly in all cases. Is that a known problem? I also has the issue and it is a known problem. Unfortunately for you, I'm not an expert of the window manager and can't help you. Best regards Jos? Bollo > Also, is there some > documentation on how it is supposed to work? > > Best regards, > Jan L?bbe From eucan at de.adit-jv.com Wed Feb 14 07:25:32 2018 From: eucan at de.adit-jv.com (Ucan, Emre (ADITG/ESB)) Date: Wed, 14 Feb 2018 07:25:32 +0000 Subject: [agl-discussions] ivi-shell layer visibility problem In-Reply-To: <1518453620.6988.45.camel@pengutronix.de> References: <1518453620.6988.45.camel@pengutronix.de> Message-ID: Hi Jan, Here some documentation: https://at.projects.genivi.org/wiki/display/PROJ/Wayland+IVI+Extension+Design Can you send me the output of LayerManagerControl get scene in bad case, good case ? Best regards Emre Ucan Engineering Software Base (ADITG/ESB) Tel. +49 5121 49 6937 > -----Original Message----- > From: automotive-discussions-bounces at lists.linuxfoundation.org > [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On > Behalf Of Jan L?bbe > Sent: Montag, 12. Februar 2018 17:58 > To: automotive-discussions at lists.linuxfoundation.org > Subject: [agl-discussions] ivi-shell layer visibility problem > > Hi, > > I've been trying to run the 5.0.1 demo on an i.MX6 with etnaviv. After > updating libdrm, gstreamer, mesa, meson and wayland to the versions in > OE rocko or master, wayland-ivi-extension to 2.1 and finally agl- > service-windowmanager-2017 to master it mostly works. > > One problem I see is that the layer visibilities don't seem to work > consistently: > 1. On some boots, the UI is invisible and only "LayerManagerControl set > surface 1 visibility" makes it show up. > 2. Even on "good" boots, if I then start an app (which works fine), I > can't switch back to the home screen. Running "LayerManagerControl set > layer 1001 visibility 0" makes it visible again. > > So it seems that the window manager (?) is not handling visibility > correctly in all cases. Is that a known problem? Also, is there some > documentation on how it is supposed to work? > > Best regards, > Jan L?bbe > -- > Pengutronix e.K. | | > Industrial Linux Solutions | http://www.pengutronix.de/ | > Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From jlu at pengutronix.de Wed Feb 14 08:38:23 2018 From: jlu at pengutronix.de (Jan =?ISO-8859-1?Q?L=FCbbe?=) Date: Wed, 14 Feb 2018 09:38:23 +0100 Subject: [agl-discussions] ivi-shell layer visibility problem In-Reply-To: References: <1518453620.6988.45.camel@pengutronix.de> Message-ID: <1518597503.6988.95.camel@pengutronix.de> Hi Emre, On Wed, 2018-02-14 at 07:25 +0000, Ucan, Emre (ADITG/ESB) wrote: > Here some documentation: > https://at.projects.genivi.org/wiki/display/PROJ/Wayland+IVI+Extensio > n+Design Thanks! > Can you send me the output of LayerManagerControl get scene in bad > case, good case ? Please take a look here, this is for the problem on startup: https://gist.github.com/jluebbe/1e7d98ce258f486b209b9c2c7d91a307#file-startup-good-scene-txt https://gist.github.com/jluebbe/1e7d98ce258f486b209b9c2c7d91a307#file-startup-bad-scene-txt The difference is: --- startup-bad.scene.txt 2018-02-14 09:29:09.095766870 +0100 +++ startup-good.scene.txt 2018-02-14 09:29:09.131766636 +0100 @@ -24,13 +24,13 @@ surface 1 (0x1) --------------------------------------- - - created by pid: 444 + - created by pid: 442 - original size: x=1080, y=1920 - destination region: x=0, y=0, w=1080, h=1920 - source region: x=0, y=0, w=1080, h=1920 - opacity: 1 - - visibility: 0 - - frame counter: 2 + - visibility: 1 + - frame counter: 13 - on layer: 1000(0x3e8) layer 1001 (0x3e9) In the good case, I then clicked on the Music icon, which worked correctly: https://gist.github.com/jluebbe/1e7d98ce258f486b209b9c2c7d91a307#file-music-good-scene-txt Then I clicked on the Home icon, but the music player stayed visible: https://gist.github.com/jluebbe/1e7d98ce258f486b209b9c2c7d91a307#file-back-to-homescreen-bad-scene-txt Best regards, Jan L?bbe -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | From knimitz at witz-inc.co.jp Wed Feb 14 09:08:03 2018 From: knimitz at witz-inc.co.jp (Kazumasa Mitsunari) Date: Wed, 14 Feb 2018 18:08:03 +0900 Subject: [agl-discussions] ivi-shell layer visibility problem In-Reply-To: <1518597503.6988.95.camel@pengutronix.de> References: <1518453620.6988.45.camel@pengutronix.de> <1518597503.6988.95.camel@pengutronix.de> Message-ID: <78b1aef4-59b6-3d18-5c47-8d9e7f46aacd@witz-inc.co.jp> Hi Jan I don't have i.MX6 but I'd like to know what happens. Could you please create a Jira ticket ? And could you please add the following environment variables into /etc/afm/unit.d/xxx (any file name is ok) and get journal log? USE_HMI_DEBUG=5 WAYLAND_DEBUG=1 Best Regards ?Kazumasa Mitsunari On 2018/02/14 17:38, Jan L?bbe wrote: > Hi Emre, > > On Wed, 2018-02-14 at 07:25 +0000, Ucan, Emre (ADITG/ESB) wrote: >> Here some documentation: >> https://at.projects.genivi.org/wiki/display/PROJ/Wayland+IVI+Extensio >> n+Design > Thanks! > >> Can you send me the output of LayerManagerControl get scene in bad >> case, good case ? > Please take a look here, this is for the problem on startup: > https://gist.github.com/jluebbe/1e7d98ce258f486b209b9c2c7d91a307#file-startup-good-scene-txt > https://gist.github.com/jluebbe/1e7d98ce258f486b209b9c2c7d91a307#file-startup-bad-scene-txt > > The difference is: > --- startup-bad.scene.txt 2018-02-14 09:29:09.095766870 +0100 > +++ startup-good.scene.txt 2018-02-14 09:29:09.131766636 +0100 > @@ -24,13 +24,13 @@ > > surface 1 (0x1) > --------------------------------------- > - - created by pid: 444 > + - created by pid: 442 > - original size: x=1080, y=1920 > - destination region: x=0, y=0, w=1080, h=1920 > - source region: x=0, y=0, w=1080, h=1920 > - opacity: 1 > - - visibility: 0 > - - frame counter: 2 > + - visibility: 1 > + - frame counter: 13 > - on layer: 1000(0x3e8) > > layer 1001 (0x3e9) > > > In the good case, I then clicked on the Music icon, which worked correctly: > https://gist.github.com/jluebbe/1e7d98ce258f486b209b9c2c7d91a307#file-music-good-scene-txt > > Then I clicked on the Home icon, but the music player stayed visible: > https://gist.github.com/jluebbe/1e7d98ce258f486b209b9c2c7d91a307#file-back-to-homescreen-bad-scene-txt > > Best regards, > Jan L?bbe -- ******************************* WITZ Corporation ??????? ??????? Base Technology Development Dept. ?Advanced Basic Technology Sect. ?Kazumasa Mitsunari Mail:knimitz at witz-inc.co.jp TEL:06-6451-2017 ******************************* From eucan at de.adit-jv.com Wed Feb 14 10:30:57 2018 From: eucan at de.adit-jv.com (Ucan, Emre (ADITG/ESB)) Date: Wed, 14 Feb 2018 10:30:57 +0000 Subject: [agl-discussions] ivi-shell layer visibility problem In-Reply-To: <1518597503.6988.95.camel@pengutronix.de> References: <1518453620.6988.45.camel@pengutronix.de> <1518597503.6988.95.camel@pengutronix.de> Message-ID: Hello Jan, I think they are window manager bugs. Surface 1 is the home screen, and surface 2 is the music player. In good startup, visibility of surface 1 is set to 1. Therefore, it is visible. In bad startup, visibility of surface 1 is 0. Therefore, it is not visible. Window manager has to set the visibility. When you clicked music player button, window manager set visibility of surface 2 to 1. Therefore, music player is visible. But window manager does not set back to 0 when you clicked the homescreen button. Best regards Emre Ucan Engineering Software Base (ADITG/ESB) Tel. +49 5121 49 6937 > -----Original Message----- > From: Jan L?bbe [mailto:jlu at pengutronix.de] > Sent: Mittwoch, 14. Februar 2018 09:39 > To: Ucan, Emre (ADITG/ESB); automotive- > discussions at lists.linuxfoundation.org > Subject: Re: [agl-discussions] ivi-shell layer visibility problem > > Hi Emre, > > On Wed, 2018-02-14 at 07:25 +0000, Ucan, Emre (ADITG/ESB) wrote: > > Here some documentation: > > https://at.projects.genivi.org/wiki/display/PROJ/Wayland+IVI+Extensio > > n+Design > > Thanks! > > > Can you send me the output of LayerManagerControl get scene in bad > > case, good case ? > > Please take a look here, this is for the problem on startup: > https://gist.github.com/jluebbe/1e7d98ce258f486b209b9c2c7d91a307#file- > startup-good-scene-txt > https://gist.github.com/jluebbe/1e7d98ce258f486b209b9c2c7d91a307#file- > startup-bad-scene-txt > > The difference is: > --- startup-bad.scene.txt 2018-02-14 09:29:09.095766870 +0100 > +++ startup-good.scene.txt 2018-02-14 09:29:09.131766636 +0100 > @@ -24,13 +24,13 @@ > > surface 1 (0x1) > --------------------------------------- > - - created by pid: 444 > + - created by pid: 442 > - original size: x=1080, y=1920 > - destination region: x=0, y=0, w=1080, h=1920 > - source region: x=0, y=0, w=1080, h=1920 > - opacity: 1 > - - visibility: 0 > - - frame counter: 2 > + - visibility: 1 > + - frame counter: 13 > - on layer: 1000(0x3e8) > > layer 1001 (0x3e9) > > > In the good case, I then clicked on the Music icon, which worked correctly: > https://gist.github.com/jluebbe/1e7d98ce258f486b209b9c2c7d91a307#file- > music-good-scene-txt > > Then I clicked on the Home icon, but the music player stayed visible: > https://gist.github.com/jluebbe/1e7d98ce258f486b209b9c2c7d91a307#file- > back-to-homescreen-bad-scene-txt > > Best regards, > Jan L?bbe > -- > Pengutronix e.K. | | > Industrial Linux Solutions | http://www.pengutronix.de/ | > Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | From jlu at pengutronix.de Wed Feb 14 11:05:39 2018 From: jlu at pengutronix.de (Jan =?ISO-8859-1?Q?L=FCbbe?=) Date: Wed, 14 Feb 2018 12:05:39 +0100 Subject: [agl-discussions] ivi-shell layer visibility problem In-Reply-To: <78b1aef4-59b6-3d18-5c47-8d9e7f46aacd@witz-inc.co.jp> References: <1518453620.6988.45.camel@pengutronix.de> <1518597503.6988.95.camel@pengutronix.de> <78b1aef4-59b6-3d18-5c47-8d9e7f46aacd@witz-inc.co.jp> Message-ID: <1518606339.6988.105.camel@pengutronix.de> Hi, On Wed, 2018-02-14 at 18:08 +0900, Kazumasa Mitsunari wrote: > I don't have i.MX6 but I'd like to know what happens. > Could you please create a Jira ticket ? > And could you please add the following environment variables into > /etc/afm/unit.d/xxx (any file name is ok) > and get journal log? > > USE_HMI_DEBUG=5 > WAYLAND_DEBUG=1 I've created https://jira.automotivelinux.org/browse/SPEC-1293 and uploaded the journal logs for both cases. Best regards, -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | From tmatsuzawa at xevo.com Thu Feb 15 03:46:48 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Thu, 15 Feb 2018 03:46:48 +0000 Subject: [agl-discussions] Bluetooth audio? Message-ID: Hello. Looks like Raspbian now uses bluez-alsa (https://github.com/Arkq/bluez-alsa) to support bluetooth audio without using pulseaudio. https://www.raspberrypi.org/blog/raspbian-stretch/ >For Stretch, we are using the bluez-alsa package to make Bluetooth audio work with ALSA itself. Any experience with it (well I should be trying it also..) and any decision on using it for the AGL distribution, with reduced pulseaudio dependency? By the way, I can see there is a good detailed observation of PA, which I wanted to read before: https://gavv.github.io/blog/pulseaudio-under-the-hood/ It has "Partially or completely disable PulseAudio" section, where it mentions about bluez-alsa project, but I am not sure if it is the only project for the same goal. From tmatsuzawa at xevo.com Thu Feb 15 05:48:10 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Thu, 15 Feb 2018 05:48:10 +0000 Subject: [agl-discussions] UP2 board DP connection? Message-ID: Hello. I am playing with my UP2 board, connecting two displays to the board, one to HDMI port and another to DP (not eDP) port. (The board has HDMI/DP stacked socket). I can see only HDMI port is working, and DP is not. (After power-on, BIOS screen and after are only displayed on the display attached to HDMI port). Is there how-to information of the either or both of below? - Use DP as my display (connect my display to DP, boot my board and see BIOS and after are displayed on the display). - Enable both HDMI and DP displays (connect two displayes to HDMI port and DP port, and let the system recognize that I have two displayes attached to the board). I looked into the BIOS setting menus, but I am not sure if I have options for this there. Any comment or suggestion is appreciated. From fulup.arfoll at iot.bzh Thu Feb 15 09:19:38 2018 From: fulup.arfoll at iot.bzh (Fulup Ar Foll) Date: Thu, 15 Feb 2018 10:19:38 +0100 Subject: [agl-discussions] Bluetooth audio? In-Reply-To: References: Message-ID: <7ccfa6a2-c0d6-3131-4cb5-200b606febeb@iot.bzh> Takashi, I did a quick trial of alsa/bluetooth in December. First impression was good but more intensive test still needed, before publishing any conclusion. Ronan from ur team is in charge of a more complete evaluation of alsa-bluez. We choose to delay those test because we wanted to move to new version of Yocto before adding any new component to AGL.. Fulup On 15/02/18 04:46, Takashi Matsuzawa wrote: > Hello. > > Looks like Raspbian now uses bluez-alsa (https://github.com/Arkq/bluez-alsa) to support bluetooth audio without using pulseaudio. > > https://www.raspberrypi.org/blog/raspbian-stretch/ > >> For Stretch, we are using the bluez-alsa package to make Bluetooth audio work with ALSA itself. > > Any experience with it (well I should be trying it also..) and any decision on using it for the AGL distribution, with reduced pulseaudio dependency? > > By the way, I can see there is a good detailed observation of PA, which I wanted to read before: > > https://gavv.github.io/blog/pulseaudio-under-the-hood/ > > It has "Partially or completely disable PulseAudio" section, where it mentions about bluez-alsa project, but I am not sure if it is the only project for the same goal. > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > From wminer at linuxfoundation.org Thu Feb 15 13:24:29 2018 From: wminer at linuxfoundation.org (Walt Miner) Date: Thu, 15 Feb 2018 07:24:29 -0600 Subject: [agl-discussions] Daring Dab 4.0.3 Patch Release Available Message-ID: A patch release (4.0.3) has been made to Daring Dab and is now available on the dab branch. Everyone using the Dab release should update to this release. Release notes, information on downloading the source code, pre-built binaries, or setting up git can be found at [1]. Build instructions were updated on the wiki and the README.md files in meta-agl and meta-agl-demo. There is no plan for a 4.0.4 release at this time. Patches may be submitted to the dab branch for consideration for a future 4.0.4 release. For upcoming patch releases any "must-fix" will be tagged with the"DD-must-fix" label in Jira. If there is a defect you think should be considered a must fix for an upcoming patch release either a) Create change on the dab branch in gerrit. This can either be a Dab specific fix or a fix that was also merged onto master. b) Indicate a change is required for Dab in Jira. Please create a JIRA issue to cherry pick the fix onto the Dab branch and assign it to Jan-Simon Moeller for consideration. Regards, Walt [1] https://wiki.automotivelinux.org/agl-distro/release-notes?&#dab_403 -- Walt Miner Engineering Project Manager The Linux Foundation mobile: +1.847.502.7087 Visit us at: automotive.linuxfoundation.org www.linuxfoundation.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From kkushal32 at gmail.com Thu Feb 15 17:36:54 2018 From: kkushal32 at gmail.com (Kushal K S V S) Date: Thu, 15 Feb 2018 23:06:54 +0530 Subject: [agl-discussions] [GSoC] Interested in working on AGL for GSoC 2018 Message-ID: Hi everyone, I am Kushal. I was going through the project lists for GSoC 2018 and found AGL really interesting. I really like the idea and I could see how this can be the next big thing. I would love to contribute to this project. I am interested in working on Task#1 ( writing demonstrator Applications ) in the project ideas list as my project this summer. I worked for 'The FreeType Org' in last year's GSoC (2017). I would say I am really comfortable and experienced working on C/C++ projects. Right now, I am going through the docs, building the Source Code on Linux with VMware and setting up SDK using docker. I am running into this problem when I follow the SDK Quick Setup guide. KUSHALs-MBP:docker-worker-generator kushalksvs$ ./contrib/create_container 0 Using instance ID #0 (user kushalksvs) Unable to find image 'docker.automotivelinux.org/agl/worker-generic:5.0' locally docker: Error response from daemon: Get https://docker.automotivelinux.org/v2/: Service Unavailable. See 'docker run --help' Any references and/or instructions I should read through first / are helpful? How to proceed further. Also what are the space requirements for this ? Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wminer at linuxfoundation.org Thu Feb 15 21:58:03 2018 From: wminer at linuxfoundation.org (Walt Miner) Date: Thu, 15 Feb 2018 15:58:03 -0600 Subject: [agl-discussions] Electric Eel 5.0.1 patch release available Message-ID: A patch release (5.0.1) has been made to Electric Eel and is now available on the eel branch. Everyone using the Eel release should update to this release. Release notes, information on downloading the source code, pre-built binaries, or setting up git can be found at [1]. Build instructions were updated on the wiki and the README.md files in meta-agl and meta-agl-demo. The merge window for the 5.0.2 release will close on March 28 Please submit any patches to be considered for the patch release before that date. For upcoming patch releases any "must-fix" will be tagged with the "EE-must-fix" label in Jira. If there is a defect you think should be considered a must fix for an upcoming patch release either a) Create change on the eel branch in gerrit. This can either be an Eel specific fix or a fix that was also merged onto master. b) Indicate a change is required for Eel in Jira. Please create a JIRA issue to cherry pick the fix onto the eel branch and assign it to Jan-Simon Moeller for consideration. Regards, Walt [1] https://wiki.automotivelinux.org/agl-distro/release-notes?&#eel_501 -- Walt Miner Engineering Project Manager The Linux Foundation mobile: +1.847.502.7087 Visit us at: automotive.linuxfoundation.org www.linuxfoundation.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From tmatsuzawa at xevo.com Fri Feb 16 00:40:21 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Fri, 16 Feb 2018 00:40:21 +0000 Subject: [agl-discussions] UP2 board DP connection? In-Reply-To: References: Message-ID: By the way, the following method of knowing output display names works? >$ journalctl |grep Output I Tried this on my UP2 board with master snapshot and ee 5.0.1 but could not get HDMI-A-1 from it. Looking into weston.log in /run/..., I can see HDMI-A-1 name. Will I see two Output names if I connect two displays to this board and everything works well? ________________________________________ From: Takashi Matsuzawa Sent: Thursday, February 15, 2018 2:48 PM To: automotive-discussions at lists.linuxfoundation.org Subject: UP2 board DP connection? Hello. I am playing with my UP2 board, connecting two displays to the board, one to HDMI port and another to DP (not eDP) port. (The board has HDMI/DP stacked socket). I can see only HDMI port is working, and DP is not. (After power-on, BIOS screen and after are only displayed on the display attached to HDMI port). Is there how-to information of the either or both of below? - Use DP as my display (connect my display to DP, boot my board and see BIOS and after are displayed on the display). - Enable both HDMI and DP displays (connect two displayes to HDMI port and DP port, and let the system recognize that I have two displayes attached to the board). I looked into the BIOS setting menus, but I am not sure if I have options for this there. Any comment or suggestion is appreciated. From tmatsuzawa at xevo.com Fri Feb 16 01:13:02 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Fri, 16 Feb 2018 01:13:02 +0000 Subject: [agl-discussions] Bluetooth audio? In-Reply-To: <7ccfa6a2-c0d6-3131-4cb5-200b606febeb@iot.bzh> References: , <7ccfa6a2-c0d6-3131-4cb5-200b606febeb@iot.bzh> Message-ID: Good to know the status. I think PA today also work with ofono to provide HFP support. The audo scenarios around BT audio should cover A2DP, AVRCP, HFP use-cases at least.. ________________________________________ From: Fulup Ar Foll Sent: Thursday, February 15, 2018 6:19 PM To: Takashi Matsuzawa; automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] Bluetooth audio? Takashi, I did a quick trial of alsa/bluetooth in December. First impression was good but more intensive test still needed, before publishing any conclusion. Ronan from ur team is in charge of a more complete evaluation of alsa-bluez. We choose to delay those test because we wanted to move to new version of Yocto before adding any new component to AGL.. Fulup On 15/02/18 04:46, Takashi Matsuzawa wrote: > Hello. > > Looks like Raspbian now uses bluez-alsa (https://github.com/Arkq/bluez-alsa) to support bluetooth audio without using pulseaudio. > > https://www.raspberrypi.org/blog/raspbian-stretch/ > >> For Stretch, we are using the bluez-alsa package to make Bluetooth audio work with ALSA itself. > > Any experience with it (well I should be trying it also..) and any decision on using it for the AGL distribution, with reduced pulseaudio dependency? > > By the way, I can see there is a good detailed observation of PA, which I wanted to read before: > > https://gavv.github.io/blog/pulseaudio-under-the-hood/ > > It has "Partially or completely disable PulseAudio" section, where it mentions about bluez-alsa project, but I am not sure if it is the only project for the same goal. > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > From wminer at linuxfoundation.org Fri Feb 16 01:21:09 2018 From: wminer at linuxfoundation.org (Walt Miner) Date: Thu, 15 Feb 2018 19:21:09 -0600 Subject: [agl-discussions] Agenda for SAT and EG Meeting at AMM Message-ID: I posted a preliminary agenda for SAT and Expert Group meetings on Thursday of the AMM in Tokyo[1]. We have two rooms that we can utilize so I created two parallel tracks during the day. I think I accommodated all of the Expert Group requests and topics we set aside for F2F meetings at the AMM. If I left out an EG or a topic, please let me know ASAP so I can re-arrange the schedule. Regards. Walt [1] https://wiki.automotivelinux.org/agl-distro/feb2018-f2f -- Walt Miner Engineering Project Manager The Linux Foundation mobile: +1.847.502.7087 Visit us at: automotive.linuxfoundation.org www.linuxfoundation.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From tmatsuzawa at xevo.com Fri Feb 16 02:01:38 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Fri, 16 Feb 2018 02:01:38 +0000 Subject: [agl-discussions] haptic touch panel. In-Reply-To: References: , Message-ID: Re: button response Just curious: In production headunits who plays "beep" (response to the button push)? Maybe it is not the app calling "aplay"? There is dedicated process for this, or an IC outside of Linux? (So that requests from non-linux part of the system can be handled as well.) If having such "beep" service is a common practice, having "vibrate" service (which talks with the actuator on I2C bus) should be preferred. Though demo environment and production may be different, adding multiple devices on I2C bus may mean I need mutex or queueing among the apps / process to not to block the bus. That kind of function is outside of wayland/window system? Or part of it? ________________________________________ From: Takashi Matsuzawa Sent: Thursday, February 8, 2018 12:37 PM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: haptic touch panel. By the way, AGL UI currently can give sound feedback (beep) when buttons, etc. are pressed? That may be the places where we may also want to give vibration, or maybe flash (for hearing-impaired drivers) feedbacks. ________________________________________ From: Takashi Matsuzawa Sent: Wednesday, February 7, 2018 4:21 PM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: haptic touch panel. I can see an example deisgn of haptic feedback touch panel: http://www.ti.com/lit/ug/tidu968/tidu968.pdf It uses DRV2667 chip to drive piezo actuators which are attached to a WVGA touch panel. On the document how-to DIY information is available, but it is not available as kit to purchse. This is giving feedback by actuator vibration, actuators are controlled by I2C signals from the host. I can see hobbiest I2C breakout board for DRV2667 is available (they sell this wit piezo actuators as set), so it may not be too difficult to make up something to give touch vibration on panel. (Since AGL uses Full HD palnel, you may need multiples of actuators?) https://hackaday.io/project/3086-piezo-haptic-flex-module I think this might be very primitive demo. (Not really sure - since I have not tried it yet. Perhaps choice of waveform and number of actuators may give you good result.) Alternative (not necessarily the choice is binary) option might be that going with mor professional and high-quality devices, maybe collaborating with special device manufactureres. There may be more complex or advanced haptic solution available. e.g. simulating the surface by ultrasonic wave or static electricity, so that you can "feel" buttons on the panel. But they may need very special hardware or panels, which probably be difficult to get or hard to control. But it may mean the demo systm becomes very expensive, and not all of the members can easily try. From wmizuno at jp.adit-jv.com Fri Feb 16 04:48:43 2018 From: wmizuno at jp.adit-jv.com (Mizuno, Wataru (ADITJ/SWG)) Date: Fri, 16 Feb 2018 04:48:43 +0000 Subject: [agl-discussions] haptic touch panel. In-Reply-To: References: , Message-ID: <3AF4192FBB4D2C458558336708E909930500A82B@ky0exch01.adit-jv.com> Hello Matsuzawa-san, I'm interested in haptic device. Do you have any software design of this device? I couldn't find how the location of button is managed in the document on your mail. Regarding the wayland/weston, I think from wayland point of view haptic feedback is handled out of compositor. Because current wayland compositor like weston doesn't have any idea about which surface has what kind of feature. i.e. weston cannot know which surface has the role of button. But I sometimes sees haptic device on cockpit at motor show. I feel it is needed for automotive usecase. Best regards, Wataru Mizuno ADITJ / SWG +81-(0)566-56-0946 -----Original Message----- From: automotive-discussions-bounces at lists.linuxfoundation.org [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On Behalf Of Takashi Matsuzawa Sent: Friday, February 16, 2018 11:02 AM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] haptic touch panel. Re: button response Just curious: In production headunits who plays "beep" (response to the button push)? Maybe it is not the app calling "aplay"? There is dedicated process for this, or an IC outside of Linux? (So that requests from non-linux part of the system can be handled as well.) If having such "beep" service is a common practice, having "vibrate" service (which talks with the actuator on I2C bus) should be preferred. Though demo environment and production may be different, adding multiple devices on I2C bus may mean I need mutex or queueing among the apps / process to not to block the bus. That kind of function is outside of wayland/window system? Or part of it? ________________________________________ From: Takashi Matsuzawa Sent: Thursday, February 8, 2018 12:37 PM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: haptic touch panel. By the way, AGL UI currently can give sound feedback (beep) when buttons, etc. are pressed? That may be the places where we may also want to give vibration, or maybe flash (for hearing-impaired drivers) feedbacks. ________________________________________ From: Takashi Matsuzawa Sent: Wednesday, February 7, 2018 4:21 PM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: haptic touch panel. I can see an example deisgn of haptic feedback touch panel: http://www.ti.com/lit/ug/tidu968/tidu968.pdf It uses DRV2667 chip to drive piezo actuators which are attached to a WVGA touch panel. On the document how-to DIY information is available, but it is not available as kit to purchse. This is giving feedback by actuator vibration, actuators are controlled by I2C signals from the host. I can see hobbiest I2C breakout board for DRV2667 is available (they sell this wit piezo actuators as set), so it may not be too difficult to make up something to give touch vibration on panel. (Since AGL uses Full HD palnel, you may need multiples of actuators?) https://hackaday.io/project/3086-piezo-haptic-flex-module I think this might be very primitive demo. (Not really sure - since I have not tried it yet. Perhaps choice of waveform and number of actuators may give you good result.) Alternative (not necessarily the choice is binary) option might be that going with mor professional and high-quality devices, maybe collaborating with special device manufactureres. There may be more complex or advanced haptic solution available. e.g. simulating the surface by ultrasonic wave or static electricity, so that you can "feel" buttons on the panel. But they may need very special hardware or panels, which probably be difficult to get or hard to control. But it may mean the demo systm becomes very expensive, and not all of the members can easily try. _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From tmatsuzawa at xevo.com Fri Feb 16 06:00:37 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Fri, 16 Feb 2018 06:00:37 +0000 Subject: [agl-discussions] haptic touch panel. In-Reply-To: <3AF4192FBB4D2C458558336708E909930500A82B@ky0exch01.adit-jv.com> References: , , <3AF4192FBB4D2C458558336708E909930500A82B@ky0exch01.adit-jv.com> Message-ID: I am sorry, I currently do not have my implementetaion. But I think maybe some clarification on expected architecture (for reference demo) is needed. (Which iof the possible architecture choice is used for this reference, etc.) Any prior study on classification on possible architecture exists? That may help us identifying where our reference should be positioned. I think production haptic devices are sometimes intelligent. The device (knobs, rotary switch) has ability to respond to the operation independent of the host sytsem. I know a case where an app (or system) download button coordinate information to the device, so that the device (with hardware cusor on screen) knows which coordinates are buttons and when to give feedbacks. Some knobs gives feedback by itself, regardless of host recognizing the input. But I feel this cannot be generalized. Also, it may also have benefit that host / app recognizes the input and give feedback. - The input device to be used is intelligent? Or not intelligent (e.g. simple piezo actuator that vibrates)? - Should app ACKs? Or UI framework (buttons on screen) ACKs? Or device itself ACKs? - What kind of feedback? Vibration? Audio? Visual? I personally feel common demo should be easy to be constructed, so that more team can develop / test on it, using the same reference. But of course, this does not prevent some teams using intelligent / proprietary solution. ________________________________________ From: Mizuno, Wataru (ADITJ/SWG) Sent: Friday, February 16, 2018 1:48 PM To: Takashi Matsuzawa; automotive-discussions at lists.linuxfoundation.org Subject: RE: haptic touch panel. Hello Matsuzawa-san, I'm interested in haptic device. Do you have any software design of this device? I couldn't find how the location of button is managed in the document on your mail. Regarding the wayland/weston, I think from wayland point of view haptic feedback is handled out of compositor. Because current wayland compositor like weston doesn't have any idea about which surface has what kind of feature. i.e. weston cannot know which surface has the role of button. But I sometimes sees haptic device on cockpit at motor show. I feel it is needed for automotive usecase. Best regards, Wataru Mizuno ADITJ / SWG +81-(0)566-56-0946 -----Original Message----- From: automotive-discussions-bounces at lists.linuxfoundation.org [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On Behalf Of Takashi Matsuzawa Sent: Friday, February 16, 2018 11:02 AM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] haptic touch panel. Re: button response Just curious: In production headunits who plays "beep" (response to the button push)? Maybe it is not the app calling "aplay"? There is dedicated process for this, or an IC outside of Linux? (So that requests from non-linux part of the system can be handled as well.) If having such "beep" service is a common practice, having "vibrate" service (which talks with the actuator on I2C bus) should be preferred. Though demo environment and production may be different, adding multiple devices on I2C bus may mean I need mutex or queueing among the apps / process to not to block the bus. That kind of function is outside of wayland/window system? Or part of it? ________________________________________ From: Takashi Matsuzawa Sent: Thursday, February 8, 2018 12:37 PM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: haptic touch panel. By the way, AGL UI currently can give sound feedback (beep) when buttons, etc. are pressed? That may be the places where we may also want to give vibration, or maybe flash (for hearing-impaired drivers) feedbacks. ________________________________________ From: Takashi Matsuzawa Sent: Wednesday, February 7, 2018 4:21 PM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: haptic touch panel. I can see an example deisgn of haptic feedback touch panel: http://www.ti.com/lit/ug/tidu968/tidu968.pdf It uses DRV2667 chip to drive piezo actuators which are attached to a WVGA touch panel. On the document how-to DIY information is available, but it is not available as kit to purchse. This is giving feedback by actuator vibration, actuators are controlled by I2C signals from the host. I can see hobbiest I2C breakout board for DRV2667 is available (they sell this wit piezo actuators as set), so it may not be too difficult to make up something to give touch vibration on panel. (Since AGL uses Full HD palnel, you may need multiples of actuators?) https://hackaday.io/project/3086-piezo-haptic-flex-module I think this might be very primitive demo. (Not really sure - since I have not tried it yet. Perhaps choice of waveform and number of actuators may give you good result.) Alternative (not necessarily the choice is binary) option might be that going with mor professional and high-quality devices, maybe collaborating with special device manufactureres. There may be more complex or advanced haptic solution available. e.g. simulating the surface by ultrasonic wave or static electricity, so that you can "feel" buttons on the panel. But they may need very special hardware or panels, which probably be difficult to get or hard to control. But it may mean the demo systm becomes very expensive, and not all of the members can easily try. _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From geoffroy.vancutsem at intel.com Fri Feb 16 09:16:53 2018 From: geoffroy.vancutsem at intel.com (VanCutsem, Geoffroy) Date: Fri, 16 Feb 2018 09:16:53 +0000 Subject: [agl-discussions] UP2 board DP connection? In-Reply-To: References: Message-ID: > -----Original Message----- > From: automotive-discussions-bounces at lists.linuxfoundation.org > [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On > Behalf Of Takashi Matsuzawa > Sent: Friday, February 16, 2018 1:40 AM > To: automotive-discussions at lists.linuxfoundation.org > Subject: Re: [agl-discussions] UP2 board DP connection? > > By the way, the following method of knowing output display names works? > > >$ journalctl |grep Output > > I Tried this on my UP2 board with master snapshot and ee 5.0.1 but could > not get HDMI-A-1 from it. If your kernel has the debug filesystem option turned on (and debugfs is actually mounted), you should be able to see all display outputs available (whether connected or not) in /sys/kernel/debug/dri/0/i915_display_info. I > > Looking into weston.log in /run/..., I can see HDMI-A-1 name. > Will I see two Output names if I connect two displays to this board and > everything works well? > > ________________________________________ > From: Takashi Matsuzawa > Sent: Thursday, February 15, 2018 2:48 PM > To: automotive-discussions at lists.linuxfoundation.org > Subject: UP2 board DP connection? > > Hello. > > I am playing with my UP2 board, connecting two displays to the board, one > to HDMI port and another to DP (not eDP) port. > (The board has HDMI/DP stacked socket). > > I can see only HDMI port is working, and DP is not. > (After power-on, BIOS screen and after are only displayed on the display > attached to HDMI port). > > Is there how-to information of the either or both of below? > > - Use DP as my display (connect my display to DP, boot my board and see > BIOS and after are displayed on the display). > > - Enable both HDMI and DP displays (connect two displayes to HDMI port > and DP port, and let the system recognize that I have two displayes attached > to the board). > > I looked into the BIOS setting menus, but I am not sure if I have options for > this there. > > Any comment or suggestion is appreciated. > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From jose.bollo at iot.bzh Fri Feb 16 09:55:11 2018 From: jose.bollo at iot.bzh (=?UTF-8?B?Sm9zw6k=?= Bollo) Date: Fri, 16 Feb 2018 10:55:11 +0100 Subject: [agl-discussions] [RFC] Development / Gerrit Workflow tuning In-Reply-To: <2468018.AWp1xHMOA4@elrond> References: <2468018.AWp1xHMOA4@elrond> Message-ID: <20180216105511.05baf76d@d-jobol.iot.bzh> On Wed, 07 Feb 2018 16:07:57 +0100 Jan-Simon M?ller wrote: > Hi all ! > > As a follow-up of today's SAT call we'd like to gather your feedback > about the current gerrit workflow and how we can improve it. > > Please reply with your thoughts: > - what is working good and should be kept as-is ? > - what is slowing us down ? > - what else would you change ? I'd like to share some concern about the use of SRCREV and AUTOREV. I'm understanding that some of us would like to lighten developers (or integrators) load by making the yocto meta-layers of AGL using the AUTOREV feature (that's the idea but in the facts it is subtly more complicated). They argue that developers will only review source code that will automatically enter the distribution without a second review for the recipe. I got issues with this model. When working on bump to rocko, it was not obvious to know clearly the reason of problems. It is more a theoretical issue that a real one but... How to be sure that the system adjustment are valid when at the same time applications may change? It clearly asks the question of distinguishing the work flows: the system flow and the application flow. I'm working on a component of AGL that requires forward work, test and, sometime, revert on impasse. This can be reviewed and I can use sandbox for testing. But I really appreciate to separate this development process from how and when AGL distribution bumps to use latest available and tested version. Yesterday, I worked on an issue related to session close on time update (SPEC-1296). I made a change for EEL. I pushed it on branch EEL but, unfortunately, made no review. So the patch entered, de facto, in EEL but: - how to make a new image that get in download.automotive.org now? - how to clearly see that a EEL image has or not the fix? I wrote in penultimate paragraph that my work can be reviewed. I confirm it. But honestly, I'm busy and have no much time to get in review of other projects. I trust my fellow developers to do their best all the time. However, I am interested in knowing when they submit a newer version, what are the new features and bug fixes. I think that a specific review that changes PV and/or SRCREV fits well this interest and in the same time put the history of AGL in the git layers of AGL. For all of these reason, I'd like to avoid use of AUTOREV, AGL_BRANCH or AGL_APP_REVISION. My 2c Best regards Jos? Bollo > For the next development cycle, we'd like to gather your feedback on > the proposed adaptations for the gerrit process: > > - We want to increase the number of maintainers with merge access to > avoid bottlenecks and speed-up the flow of code. > - Each profile (IVI, telematics, core) would have a set of > maintainers (>=3) > - src / staging would have a set of maintainers (>=5) > - Maintainers would be nominated by the community and approved by SAT > - Maintainers get +2 and merge rights in gerrit > - gerrit will be adapted to: > -- ignore the vote of the submitter/owner of the patch (no vote on > own patch) -- votes become additive (e.g. +2 & +2 = +4) > --- e.g. a +4 is required for merge > --- up for discussion > --- if +2 [=1*+2 merger review or as option 2*+1 normal > reviews] --- or +4 [= 2*+2 merger review or as option 4*+1 normal > reviews] -- all src / staging repos need to go through gerrit reviews > going forward (no more direct push) > > > Please tell us your thoughts about the above questions and the > proposal. > > > Thanks. > > Best regards, > > Jan-Simon M?ller > AGL Release Manager > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From tmatsuzawa at xevo.com Fri Feb 16 09:55:22 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Fri, 16 Feb 2018 09:55:22 +0000 Subject: [agl-discussions] UP2 board DP connection? In-Reply-To: References: , Message-ID: Hello. Thank you for your info. I just tried and output is like this. So, DP-1 is seen by Linux kernel but there is no display connected? But I am actually connecting my display (powerd on) to DP, but using DP<->HDMI conversion cable. Cable is wrong?(I should have avoided a cheap one??) Unfortunately his is the only (full)DP cable in my office, so I cannot try another today.. >Connector info >-------------- >connector 51: type DP-1, status: disconnected > DPCD rev: 0 > audio support: no > DP branch device present: no > modes: >connector 58: type HDMI-A-1, status: connected > name: > physical dimensions: 520x320mm > subpixel order: Unknown > CEA rev: 3 > audio support: yes > modes: > id 62:.... ________________________________________ From: VanCutsem, Geoffroy Sent: Friday, February 16, 2018 6:16 PM To: Takashi Matsuzawa; automotive-discussions at lists.linuxfoundation.org Subject: RE: UP2 board DP connection? > -----Original Message----- > From: automotive-discussions-bounces at lists.linuxfoundation.org > [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On > Behalf Of Takashi Matsuzawa > Sent: Friday, February 16, 2018 1:40 AM > To: automotive-discussions at lists.linuxfoundation.org > Subject: Re: [agl-discussions] UP2 board DP connection? > > By the way, the following method of knowing output display names works? > > >$ journalctl |grep Output > > I Tried this on my UP2 board with master snapshot and ee 5.0.1 but could > not get HDMI-A-1 from it. If your kernel has the debug filesystem option turned on (and debugfs is actually mounted), you should be able to see all display outputs available (whether connected or not) in /sys/kernel/debug/dri/0/i915_display_info. I > > Looking into weston.log in /run/..., I can see HDMI-A-1 name. > Will I see two Output names if I connect two displays to this board and > everything works well? > > ________________________________________ > From: Takashi Matsuzawa > Sent: Thursday, February 15, 2018 2:48 PM > To: automotive-discussions at lists.linuxfoundation.org > Subject: UP2 board DP connection? > > Hello. > > I am playing with my UP2 board, connecting two displays to the board, one > to HDMI port and another to DP (not eDP) port. > (The board has HDMI/DP stacked socket). > > I can see only HDMI port is working, and DP is not. > (After power-on, BIOS screen and after are only displayed on the display > attached to HDMI port). > > Is there how-to information of the either or both of below? > > - Use DP as my display (connect my display to DP, boot my board and see > BIOS and after are displayed on the display). > > - Enable both HDMI and DP displays (connect two displayes to HDMI port > and DP port, and let the system recognize that I have two displayes attached > to the board). > > I looked into the BIOS setting menus, but I am not sure if I have options for > this there. > > Any comment or suggestion is appreciated. > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From jsmoeller at linuxfoundation.org Fri Feb 16 10:23:14 2018 From: jsmoeller at linuxfoundation.org (Jan-Simon =?ISO-8859-1?Q?M=F6ller?=) Date: Fri, 16 Feb 2018 11:23:14 +0100 Subject: [agl-discussions] [RFC] Development / Gerrit Workflow tuning In-Reply-To: <20180216105511.05baf76d@d-jobol.iot.bzh> References: <2468018.AWp1xHMOA4@elrond> <20180216105511.05baf76d@d-jobol.iot.bzh> Message-ID: <1665550.UFTR610KUO@elrond> Hi all! > I'd like to share some concern about the use of SRCREV and AUTOREV. I agree with Jose. The meta-layers / recipes should use fixed hashes. Best regards, Jan-Simon From philip.wise at here.com Fri Feb 16 10:31:40 2018 From: philip.wise at here.com (Wise, Philip) Date: Fri, 16 Feb 2018 10:31:40 +0000 Subject: [agl-discussions] [RFC] Development / Gerrit Workflow tuning In-Reply-To: <1665550.UFTR610KUO@elrond> References: <2468018.AWp1xHMOA4@elrond> <20180216105511.05baf76d@d-jobol.iot.bzh>,<1665550.UFTR610KUO@elrond> Message-ID: >> I'd like to share some concern about the use of SRCREV and AUTOREV. >I agree with Jose. The meta-layers / recipes should use fixed hashes. One trick that might be useful is to provide a class that sets one or more packages to ${AUTOREV}, something like SRCREV_pn-aktualizr ?= "${AUTOREV}" We do this in the meta-updater layer: https://github.com/advancedtelematic/meta-updater/blob/rocko/classes/sota_bleeding.inc Developers working on the package in question normally include a line like "require classes/sota_bleeding.inc" in their site.conf and therefore always get the newest head, but downstream consumers of the layer don't, and they get a stable version that has at least been though a set of Yocto-level integration tests. ________________________________ From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Jan-Simon M?ller Sent: 16 February 2018 11:23:14 To: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] [RFC] Development / Gerrit Workflow tuning Hi all! > I'd like to share some concern about the use of SRCREV and AUTOREV. I agree with Jose. The meta-layers / recipes should use fixed hashes. Best regards, Jan-Simon _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.linuxfoundation.org%2Fmailman%2Flistinfo%2Fautomotive-discussions&data=01%7C01%7C%7Cc26bbfcb54524eec00d908d57527503b%7C6d4034cd72254f72b85391feaea64919%7C1&sdata=YvQgeojSChMmnC4I6pCFk2P261Cd1Qp7f5K2%2FVC%2Fd3M%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From tmatsuzawa at xevo.com Fri Feb 16 10:48:49 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Fri, 16 Feb 2018 10:48:49 +0000 Subject: [agl-discussions] haptic touch panel. In-Reply-To: References: , , <3AF4192FBB4D2C458558336708E909930500A82B@ky0exch01.adit-jv.com>, Message-ID: Well, I can see W3C Vibration API and similar on various SDKs, but they are simple low-level on/off switch... (But anyway visible to application code.) ________________________________________ From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Takashi Matsuzawa Sent: Friday, February 16, 2018 3:00 PM To: Mizuno, Wataru (ADITJ/SWG); automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] haptic touch panel. [This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] I am sorry, I currently do not have my implementetaion. But I think maybe some clarification on expected architecture (for reference demo) is needed. (Which iof the possible architecture choice is used for this reference, etc.) Any prior study on classification on possible architecture exists? That may help us identifying where our reference should be positioned. I think production haptic devices are sometimes intelligent. The device (knobs, rotary switch) has ability to respond to the operation independent of the host sytsem. I know a case where an app (or system) download button coordinate information to the device, so that the device (with hardware cusor on screen) knows which coordinates are buttons and when to give feedbacks. Some knobs gives feedback by itself, regardless of host recognizing the input. But I feel this cannot be generalized. Also, it may also have benefit that host / app recognizes the input and give feedback. - The input device to be used is intelligent? Or not intelligent (e.g. simple piezo actuator that vibrates)? - Should app ACKs? Or UI framework (buttons on screen) ACKs? Or device itself ACKs? - What kind of feedback? Vibration? Audio? Visual? I personally feel common demo should be easy to be constructed, so that more team can develop / test on it, using the same reference. But of course, this does not prevent some teams using intelligent / proprietary solution. ________________________________________ From: Mizuno, Wataru (ADITJ/SWG) Sent: Friday, February 16, 2018 1:48 PM To: Takashi Matsuzawa; automotive-discussions at lists.linuxfoundation.org Subject: RE: haptic touch panel. Hello Matsuzawa-san, I'm interested in haptic device. Do you have any software design of this device? I couldn't find how the location of button is managed in the document on your mail. Regarding the wayland/weston, I think from wayland point of view haptic feedback is handled out of compositor. Because current wayland compositor like weston doesn't have any idea about which surface has what kind of feature. i.e. weston cannot know which surface has the role of button. But I sometimes sees haptic device on cockpit at motor show. I feel it is needed for automotive usecase. Best regards, Wataru Mizuno ADITJ / SWG +81-(0)566-56-0946 -----Original Message----- From: automotive-discussions-bounces at lists.linuxfoundation.org [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On Behalf Of Takashi Matsuzawa Sent: Friday, February 16, 2018 11:02 AM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] haptic touch panel. Re: button response Just curious: In production headunits who plays "beep" (response to the button push)? Maybe it is not the app calling "aplay"? There is dedicated process for this, or an IC outside of Linux? (So that requests from non-linux part of the system can be handled as well.) If having such "beep" service is a common practice, having "vibrate" service (which talks with the actuator on I2C bus) should be preferred. Though demo environment and production may be different, adding multiple devices on I2C bus may mean I need mutex or queueing among the apps / process to not to block the bus. That kind of function is outside of wayland/window system? Or part of it? ________________________________________ From: Takashi Matsuzawa Sent: Thursday, February 8, 2018 12:37 PM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: haptic touch panel. By the way, AGL UI currently can give sound feedback (beep) when buttons, etc. are pressed? That may be the places where we may also want to give vibration, or maybe flash (for hearing-impaired drivers) feedbacks. ________________________________________ From: Takashi Matsuzawa Sent: Wednesday, February 7, 2018 4:21 PM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: haptic touch panel. I can see an example deisgn of haptic feedback touch panel: http://www.ti.com/lit/ug/tidu968/tidu968.pdf It uses DRV2667 chip to drive piezo actuators which are attached to a WVGA touch panel. On the document how-to DIY information is available, but it is not available as kit to purchse. This is giving feedback by actuator vibration, actuators are controlled by I2C signals from the host. I can see hobbiest I2C breakout board for DRV2667 is available (they sell this wit piezo actuators as set), so it may not be too difficult to make up something to give touch vibration on panel. (Since AGL uses Full HD palnel, you may need multiples of actuators?) https://hackaday.io/project/3086-piezo-haptic-flex-module I think this might be very primitive demo. (Not really sure - since I have not tried it yet. Perhaps choice of waveform and number of actuators may give you good result.) Alternative (not necessarily the choice is binary) option might be that going with mor professional and high-quality devices, maybe collaborating with special device manufactureres. There may be more complex or advanced haptic solution available. e.g. simulating the surface by ultrasonic wave or static electricity, so that you can "feel" buttons on the panel. But they may need very special hardware or panels, which probably be difficult to get or hard to control. But it may mean the demo systm becomes very expensive, and not all of the members can easily try. _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From geoffroy.vancutsem at intel.com Fri Feb 16 10:52:15 2018 From: geoffroy.vancutsem at intel.com (VanCutsem, Geoffroy) Date: Fri, 16 Feb 2018 10:52:15 +0000 Subject: [agl-discussions] UP2 board DP connection? In-Reply-To: References: , Message-ID: Hi Matsuzawa-san, > -----Original Message----- > From: Takashi Matsuzawa [mailto:tmatsuzawa at xevo.com] > Sent: Friday, February 16, 2018 10:55 AM > To: VanCutsem, Geoffroy ; automotive- > discussions at lists.linuxfoundation.org > Subject: Re: UP2 board DP connection? > > Hello. > Thank you for your info. > > I just tried and output is like this. > > So, DP-1 is seen by Linux kernel but there is no display connected? > But I am actually connecting my display (powerd on) to DP, but using DP<- > >HDMI conversion cable. > > Cable is wrong?(I should have avoided a cheap one??) Unfortunately his is > the only (full)DP cable in my office, so I cannot try another today.. I don't have a UP Squared board to test with but this is a possibility. I would try booting a live distribution (Ubuntu/Fedora) from a USB stick and look at the output reported there (just to rule out something to do with AGL itself). I must confess that I tend to stay away from cheap cables these days, I've had too many issues with them in the past and it usually ends up costing me more in troubleshooting time than the extra money needed to buy a good quality one. I would definitely try different cables (DP-to-HDMI adapter) and also make sure the HDMI cable itself is good (try swapping it out with the one you have connected to the UP Square board HDMI connector now). > > >Connector info > >-------------- > >connector 51: type DP-1, status: disconnected > > DPCD rev: 0 > > audio support: no > > DP branch device present: no > > modes: > >connector 58: type HDMI-A-1, status: connected > > name: > > physical dimensions: 520x320mm > > subpixel order: Unknown > > CEA rev: 3 > > audio support: yes > > modes: > > id 62:.... > > ________________________________________ > From: VanCutsem, Geoffroy > Sent: Friday, February 16, 2018 6:16 PM > To: Takashi Matsuzawa; automotive-discussions at lists.linuxfoundation.org > Subject: RE: UP2 board DP connection? > > > > > -----Original Message----- > > From: automotive-discussions-bounces at lists.linuxfoundation.org > > [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On > > Behalf Of Takashi Matsuzawa > > Sent: Friday, February 16, 2018 1:40 AM > > To: automotive-discussions at lists.linuxfoundation.org > > Subject: Re: [agl-discussions] UP2 board DP connection? > > > > By the way, the following method of knowing output display names works? > > > > >$ journalctl |grep Output > > > > I Tried this on my UP2 board with master snapshot and ee 5.0.1 but > > could not get HDMI-A-1 from it. > > If your kernel has the debug filesystem option turned on (and debugfs is > actually mounted), you should be able to see all display outputs available > (whether connected or not) in /sys/kernel/debug/dri/0/i915_display_info. I > > > > > Looking into weston.log in /run/..., I can see HDMI-A-1 name. > > Will I see two Output names if I connect two displays to this board > > and everything works well? > > > > ________________________________________ > > From: Takashi Matsuzawa > > Sent: Thursday, February 15, 2018 2:48 PM > > To: automotive-discussions at lists.linuxfoundation.org > > Subject: UP2 board DP connection? > > > > Hello. > > > > I am playing with my UP2 board, connecting two displays to the board, > > one to HDMI port and another to DP (not eDP) port. > > (The board has HDMI/DP stacked socket). > > > > I can see only HDMI port is working, and DP is not. > > (After power-on, BIOS screen and after are only displayed on the > > display attached to HDMI port). > > > > Is there how-to information of the either or both of below? > > > > - Use DP as my display (connect my display to DP, boot my board and > > see BIOS and after are displayed on the display). > > > > - Enable both HDMI and DP displays (connect two displayes to HDMI port > > and DP port, and let the system recognize that I have two displayes > > attached to the board). > > > > I looked into the BIOS setting menus, but I am not sure if I have > > options for this there. > > > > Any comment or suggestion is appreciated. > > _______________________________________________ > > automotive-discussions mailing list > > automotive-discussions at lists.linuxfoundation.org > > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussi > > ons From jsmoeller at linuxfoundation.org Fri Feb 16 10:54:10 2018 From: jsmoeller at linuxfoundation.org (Jan-Simon =?ISO-8859-1?Q?M=F6ller?=) Date: Fri, 16 Feb 2018 11:54:10 +0100 Subject: [agl-discussions] [RFC] Development / Gerrit Workflow tuning In-Reply-To: References: <2468018.AWp1xHMOA4@elrond> <1665550.UFTR610KUO@elrond> Message-ID: <6516277.8tbjELoXfj@elrond> Am Freitag, 16. Februar 2018, 11:31:40 CET schrieb Wise, Philip: > >> I'd like to share some concern about the use of SRCREV and AUTOREV. > > > >I agree with Jose. The meta-layers / recipes should use fixed hashes. > > One trick that might be useful is to provide a class that sets one or more > packages to ${AUTOREV}, something like > SRCREV_pn-aktualizr ?= "${AUTOREV}" > Yes, we can have an inc/class/agl-feature for 'bleeding-edge' versions of specific/all repos. That might help developers in bumping during development. Best, JS From jsmoeller at linuxfoundation.org Fri Feb 16 10:57:03 2018 From: jsmoeller at linuxfoundation.org (Jan-Simon =?ISO-8859-1?Q?M=F6ller?=) Date: Fri, 16 Feb 2018 11:57:03 +0100 Subject: [agl-discussions] [RFC] Development / Gerrit Workflow tuning In-Reply-To: <6516277.8tbjELoXfj@elrond> References: <2468018.AWp1xHMOA4@elrond> <6516277.8tbjELoXfj@elrond> Message-ID: <3327463.okOkK4lGit@elrond> Am Freitag, 16. Februar 2018, 11:54:10 CET schrieb Jan-Simon M?ller: > > One trick that might be useful is to provide a class that sets one or more > > packages to ${AUTOREV}, something like > > SRCREV_pn-aktualizr ?= "${AUTOREV}" > > Yes, we can have an inc/class/agl-feature for 'bleeding-edge' versions of > specific/all repos. That might help developers in bumping during > development. And/or for local development EXTERNALSRC capabilities to add in your local.conf: INHERIT += "externalsrc" EXTERNALSRC_pn-myrecipe = "path-to-your-source-tree" Best, JS From kien.t.dinh at intel.com Fri Feb 16 11:15:23 2018 From: kien.t.dinh at intel.com (Dinh, Kien T) Date: Fri, 16 Feb 2018 11:15:23 +0000 Subject: [agl-discussions] UP2 board DP connection? Message-ID: Matsuzawa-san, I think you can try with the DP to HDMI active adapter. On the Up squared forum they reported that the active one worked instead of passive one. Regards, Kien ?On 2018/02/16 19:52, "automotive-discussions-bounces at lists.linuxfoundation.org on behalf of VanCutsem, Geoffroy" wrote: Hi Matsuzawa-san, > -----Original Message----- > From: Takashi Matsuzawa [mailto:tmatsuzawa at xevo.com] > Sent: Friday, February 16, 2018 10:55 AM > To: VanCutsem, Geoffroy ; automotive- > discussions at lists.linuxfoundation.org > Subject: Re: UP2 board DP connection? > > Hello. > Thank you for your info. > > I just tried and output is like this. > > So, DP-1 is seen by Linux kernel but there is no display connected? > But I am actually connecting my display (powerd on) to DP, but using DP<- > >HDMI conversion cable. > > Cable is wrong?(I should have avoided a cheap one??) Unfortunately his is > the only (full)DP cable in my office, so I cannot try another today.. I don't have a UP Squared board to test with but this is a possibility. I would try booting a live distribution (Ubuntu/Fedora) from a USB stick and look at the output reported there (just to rule out something to do with AGL itself). I must confess that I tend to stay away from cheap cables these days, I've had too many issues with them in the past and it usually ends up costing me more in troubleshooting time than the extra money needed to buy a good quality one. I would definitely try different cables (DP-to-HDMI adapter) and also make sure the HDMI cable itself is good (try swapping it out with the one you have connected to the UP Square board HDMI connector now). > > >Connector info > >-------------- > >connector 51: type DP-1, status: disconnected > > DPCD rev: 0 > > audio support: no > > DP branch device present: no > > modes: > >connector 58: type HDMI-A-1, status: connected > > name: > > physical dimensions: 520x320mm > > subpixel order: Unknown > > CEA rev: 3 > > audio support: yes > > modes: > > id 62:.... > > ________________________________________ > From: VanCutsem, Geoffroy > Sent: Friday, February 16, 2018 6:16 PM > To: Takashi Matsuzawa; automotive-discussions at lists.linuxfoundation.org > Subject: RE: UP2 board DP connection? > > > > > -----Original Message----- > > From: automotive-discussions-bounces at lists.linuxfoundation.org > > [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On > > Behalf Of Takashi Matsuzawa > > Sent: Friday, February 16, 2018 1:40 AM > > To: automotive-discussions at lists.linuxfoundation.org > > Subject: Re: [agl-discussions] UP2 board DP connection? > > > > By the way, the following method of knowing output display names works? > > > > >$ journalctl |grep Output > > > > I Tried this on my UP2 board with master snapshot and ee 5.0.1 but > > could not get HDMI-A-1 from it. > > If your kernel has the debug filesystem option turned on (and debugfs is > actually mounted), you should be able to see all display outputs available > (whether connected or not) in /sys/kernel/debug/dri/0/i915_display_info. I > > > > > Looking into weston.log in /run/..., I can see HDMI-A-1 name. > > Will I see two Output names if I connect two displays to this board > > and everything works well? > > > > ________________________________________ > > From: Takashi Matsuzawa > > Sent: Thursday, February 15, 2018 2:48 PM > > To: automotive-discussions at lists.linuxfoundation.org > > Subject: UP2 board DP connection? > > > > Hello. > > > > I am playing with my UP2 board, connecting two displays to the board, > > one to HDMI port and another to DP (not eDP) port. > > (The board has HDMI/DP stacked socket). > > > > I can see only HDMI port is working, and DP is not. > > (After power-on, BIOS screen and after are only displayed on the > > display attached to HDMI port). > > > > Is there how-to information of the either or both of below? > > > > - Use DP as my display (connect my display to DP, boot my board and > > see BIOS and after are displayed on the display). > > > > - Enable both HDMI and DP displays (connect two displayes to HDMI port > > and DP port, and let the system recognize that I have two displayes > > attached to the board). > > > > I looked into the BIOS setting menus, but I am not sure if I have > > options for this there. > > > > Any comment or suggestion is appreciated. > > _______________________________________________ > > automotive-discussions mailing list > > automotive-discussions at lists.linuxfoundation.org > > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussi > > ons _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From knimitz at witz-inc.co.jp Fri Feb 16 11:48:56 2018 From: knimitz at witz-inc.co.jp (Kazumasa Mitsunari) Date: Fri, 16 Feb 2018 20:48:56 +0900 Subject: [agl-discussions] [RFC] Development / Gerrit Workflow tuning In-Reply-To: <20180216105511.05baf76d@d-jobol.iot.bzh> References: <2468018.AWp1xHMOA4@elrond> <20180216105511.05baf76d@d-jobol.iot.bzh> Message-ID: <26f9aea0-ecbd-5906-7a70-798f7bfd52d7@witz-inc.co.jp> Hi I understood your concern. I agree with Jose. And I have a concern of the version. I'd like to know there is a rule for the version of recipe. The recipes developed in AGL are normally named as "XXXX_git.bb". I'm understanding "git" is useful for people to use the latest code. I'd like to know we can choose to set version such like "XXXX_1.0.bb". When the code is changed largely in sandbox for example and want to merge, other people can't know the major change only with SRCREV. I think using version is useful to notify people of major or minor change. In my opinion, if there is no change of interface or behavior, the change of SRCREV hash is enough. If there are some changes of interface or behavior, it's thankful for people to know the change. Best Regards ?Kazumasa Mitsunari On 2018/02/16 18:55, Jos? Bollo wrote: > On Wed, 07 Feb 2018 16:07:57 +0100 > Jan-Simon M?ller wrote: > >> Hi all ! >> >> As a follow-up of today's SAT call we'd like to gather your feedback >> about the current gerrit workflow and how we can improve it. >> >> Please reply with your thoughts: >> - what is working good and should be kept as-is ? >> - what is slowing us down ? >> - what else would you change ? > I'd like to share some concern about the use of SRCREV and AUTOREV. > > I'm understanding that some of us would like to lighten developers (or > integrators) load by making the yocto meta-layers of AGL using the > AUTOREV feature (that's the idea but in the facts it is subtly more > complicated). They argue that developers will only review source code > that will automatically enter the distribution without a second review > for the recipe. > > I got issues with this model. > > When working on bump to rocko, it was not obvious to know clearly the > reason of problems. It is more a theoretical issue that a real one > but... How to be sure that the system adjustment are valid when at the > same time applications may change? It clearly asks the question of > distinguishing the work flows: the system flow and the application flow. > > I'm working on a component of AGL that requires forward work, > test and, sometime, revert on impasse. This can be reviewed and I can > use sandbox for testing. But I really appreciate to separate this > development process from how and when AGL distribution bumps to use > latest available and tested version. > > Yesterday, I worked on an issue related to session close on time update > (SPEC-1296). I made a change for EEL. I pushed it on branch EEL but, > unfortunately, made no review. So the patch entered, de facto, in EEL > but: > - how to make a new image that get in download.automotive.org now? > - how to clearly see that a EEL image has or not the fix? > > I wrote in penultimate paragraph that my work can be reviewed. I > confirm it. But honestly, I'm busy and have no much time to get in > review of other projects. I trust my fellow developers to do their best > all the time. However, I am interested in knowing when they submit a > newer version, what are the new features and bug fixes. I think that > a specific review that changes PV and/or SRCREV fits well this > interest and in the same time put the history of AGL in the git layers > of AGL. > > For all of these reason, I'd like to avoid use of AUTOREV, AGL_BRANCH > or AGL_APP_REVISION. > > My 2c > > Best regards > Jos? Bollo > >> For the next development cycle, we'd like to gather your feedback on >> the proposed adaptations for the gerrit process: >> >> - We want to increase the number of maintainers with merge access to >> avoid bottlenecks and speed-up the flow of code. >> - Each profile (IVI, telematics, core) would have a set of >> maintainers (>=3) >> - src / staging would have a set of maintainers (>=5) >> - Maintainers would be nominated by the community and approved by SAT >> - Maintainers get +2 and merge rights in gerrit >> - gerrit will be adapted to: >> -- ignore the vote of the submitter/owner of the patch (no vote on >> own patch) -- votes become additive (e.g. +2 & +2 = +4) >> --- e.g. a +4 is required for merge >> --- up for discussion >> --- if +2 [=1*+2 merger review or as option 2*+1 normal >> reviews] --- or +4 [= 2*+2 merger review or as option 4*+1 normal >> reviews] -- all src / staging repos need to go through gerrit reviews >> going forward (no more direct push) >> >> >> Please tell us your thoughts about the above questions and the >> proposal. >> >> >> Thanks. >> >> Best regards, >> >> Jan-Simon M?ller >> AGL Release Manager >> >> _______________________________________________ >> automotive-discussions mailing list >> automotive-discussions at lists.linuxfoundation.org >> https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions -- ******************************* WITZ Corporation ??????? ??????? Base Technology Development Dept. ?Advanced Basic Technology Sect. ?Kazumasa Mitsunari Mail:knimitz at witz-inc.co.jp TEL:06-6451-2017 ******************************* From jsmoeller at linuxfoundation.org Fri Feb 16 12:07:14 2018 From: jsmoeller at linuxfoundation.org (Jan-Simon =?ISO-8859-1?Q?M=F6ller?=) Date: Fri, 16 Feb 2018 13:07:14 +0100 Subject: [agl-discussions] [RFC] Development / Gerrit Workflow tuning In-Reply-To: <26f9aea0-ecbd-5906-7a70-798f7bfd52d7@witz-inc.co.jp> References: <2468018.AWp1xHMOA4@elrond> <20180216105511.05baf76d@d-jobol.iot.bzh> <26f9aea0-ecbd-5906-7a70-798f7bfd52d7@witz-inc.co.jp> Message-ID: <3043013.lOf7AYbRKJ@elrond> Hi ! Am Freitag, 16. Februar 2018, 12:48:56 CET schrieb Kazumasa Mitsunari: > Hi > > I understood your concern. I agree with Jose. > > And I have a concern of the version. > > I'd like to know there is a rule for the version of recipe. > > The recipes developed in AGL are normally named as "XXXX_git.bb". > I'm understanding "git" is useful for people to use the latest code. > > I'd like to know we can choose to set version such like "XXXX_1.0.bb". Yes, bitbake understands versions. And by default it will chose the 'latest'/'highest': E.g.: XYZ_1.0.bb XYZ_2.0.bb --> bitbake will build XYZ_2.0 But: XYZ_1.0.bb XYZ_2.0.bb XYZ_git.bb --> bitbake will build XYZ_git as it is considered the 'latest'. We can tweak this in the local.conf with PREFERRED_VERSION_XYZ="2.0" > In my opinion, if there is no change of interface or behavior, the > change of SRCREV hash is enough. > If there are some changes of interface or behavior, it's thankful for > people to know the change. Yes, you can version your recipes and make API changes visible by changing the version number. Best regards, Jan-Simon From knimitz at witz-inc.co.jp Fri Feb 16 12:15:04 2018 From: knimitz at witz-inc.co.jp (Kazumasa Mitsunari) Date: Fri, 16 Feb 2018 21:15:04 +0900 Subject: [agl-discussions] [RFC] Development / Gerrit Workflow tuning In-Reply-To: <3043013.lOf7AYbRKJ@elrond> References: <2468018.AWp1xHMOA4@elrond> <20180216105511.05baf76d@d-jobol.iot.bzh> <26f9aea0-ecbd-5906-7a70-798f7bfd52d7@witz-inc.co.jp> <3043013.lOf7AYbRKJ@elrond> Message-ID: Hi Thank you for letting me know:) Best Regards ?Kazumasa Mitsunari On 2018?02?16? 21:07, Jan-Simon M?ller wrote: > Hi ! > > Am Freitag, 16. Februar 2018, 12:48:56 CET schrieb Kazumasa Mitsunari: >> Hi >> >> I understood your concern. I agree with Jose. >> >> And I have a concern of the version. >> >> I'd like to know there is a rule for the version of recipe. >> >> The recipes developed in AGL are normally named as "XXXX_git.bb". >> I'm understanding "git" is useful for people to use the latest code. >> >> I'd like to know we can choose to set version such like "XXXX_1.0.bb". > Yes, bitbake understands versions. And by default it will chose the > 'latest'/'highest': > > E.g.: > XYZ_1.0.bb > XYZ_2.0.bb > --> bitbake will build XYZ_2.0 > > But: > XYZ_1.0.bb > XYZ_2.0.bb > XYZ_git.bb > --> bitbake will build XYZ_git as it is considered the 'latest'. > > We can tweak this in the local.conf with > PREFERRED_VERSION_XYZ="2.0" > >> In my opinion, if there is no change of interface or behavior, the >> change of SRCREV hash is enough. >> If there are some changes of interface or behavior, it's thankful for >> people to know the change. > Yes, you can version your recipes and make API changes visible by changing the > version number. > > Best regards, > Jan-Simon > -- ******************************* WITZ Corporation ??????? ??????? Base Technology Development Dept. ?Advanced Basic Technology Sect. ?Kazumasa Mitsunari Mail:knimitz at witz-inc.co.jp ******************************* From wminer at linuxfoundation.org Fri Feb 16 13:55:29 2018 From: wminer at linuxfoundation.org (wminer at linuxfoundation.org) Date: Fri, 16 Feb 2018 13:55:29 +0000 Subject: [agl-discussions] Canceled event: EG Virtualization @ Fri Feb 23, 2018 7am - 8am (CST) (automotive-discussions@lists.linuxfoundation.org) Message-ID: <001a1145ace4744105056554b29e@google.com> This event has been canceled. Title: EG Virtualization 1. Please join my meeting. https://global.gotomeeting.com/join/728365005 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. Australia: +61 2 9091 7603 Austria: +43 1 2530 22500 Belgium: +32 (0) 27 00 6375 Canada (toll-free): 1 888 299 1889 Canada: +1 (647) 497-9373 Denmark: +45 32 72 03 69 Finland: +358 (0) 923 17 0555 France: +33 (0) 170 950 585 Germany: +49 (0) 692 5736 7208 India (toll-free): 000 800 852 1424 Ireland: +353 (0) 15 255 598 Italy: +39 0 699 26 68 65 Japan (toll-free): 0 120 352 900 Korea, Republic of (toll-free): 0806180880 Netherlands: +31 (0) 707 709 520 New Zealand: +64 9 887 3469 Norway: +47 23 96 01 18 Spain: +34 932 75 1230 Sweden: +46 (0) 853 527 817 Switzerland: +41 (0) 225 4599 60 United Kingdom: +44 (0) 20 3713 5010 United States (toll-free): 1 866 899 4679 United States: +1 (571) 317-3117 Access Code: 728-365-005 Audio PIN: Shown after joining the meeting Meeting ID: 728-365-005 When: Fri Feb 23, 2018 7am ? 8am Central Time Where: https://www.gotomeeting.com/join/728365005 Calendar: automotive-discussions at lists.linuxfoundation.org Who: * Walt Miner - creator * Michele Paolino * Noriaki Fukuyasu * automotive-discussions at lists.linuxfoundation.org * Jan-Simon Moeller * dcauchy at linuxfoundation.org Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account automotive-discussions at lists.linuxfoundation.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3258 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3332 bytes Desc: not available URL: From wminer at linuxfoundation.org Fri Feb 16 13:58:05 2018 From: wminer at linuxfoundation.org (wminer at linuxfoundation.org) Date: Fri, 16 Feb 2018 13:58:05 +0000 Subject: [agl-discussions] Canceled event: [AGL-SAT] Biweekly Call @ Thu Mar 1, 2018 8am - 9am (CST) (automotive-discussions@lists.linuxfoundation.org) Message-ID: <089e082429c4be3fd3056554bb8a@google.com> This event has been canceled. Title: [AGL-SAT] Biweekly Call AGL-SAT Biweekly Meeting Please join my meeting from your computer, tablet or smartphone. https://global.gotomeeting.com/join/796425741 You can also dial in using your phone. United States (Toll-free) 1 877 309 2070 United States +1 (312) 757-3119 Access Code: 796-425-741 More phone numbers Australia +61 2 8355 1034 Austria +43 7 2088 0716 Belgium +32 (0) 28 93 7002 Canada (Toll-free) 1 877 777 3281 Canada +1 (647) 497-9372 Denmark +45 69 91 84 58 Finland +358 (0) 923 17 0556 France +33 (0) 170 950 590 Germany +49 (0) 692 5736 7206 India (Toll-free) 000 800 100 8227 Ireland +353 (0) 19 030 053 Italy +39 0 699 26 68 65 Japan (Toll-free) 0 120 242 200 Korea, Republic of (Toll-free) 0806180880 Netherlands +31 (0) 208 080 759 New Zealand +64 9 974 9579 Norway +47 21 04 30 59 Spain +34 931 76 1534 Sweden +46 (0) 852 500 691 Switzerland +41 (0) 435 0026 89 United Kingdom +44 (0) 20 3713 5011 First GoToMeeting? Try a test session: http://help.citrix.com/getready When: Thu Mar 1, 2018 8am ? 9am Central Time Where: https://global.gotomeeting.com/join/796425741 Calendar: automotive-discussions at lists.linuxfoundation.org Who: * Walt Miner - creator * Noriaki Fukuyasu * dcauchy at linuxfoundation.org * automotive-discussions at lists.linuxfoundation.org Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account automotive-discussions at lists.linuxfoundation.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3009 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3080 bytes Desc: not available URL: From wminer at linuxfoundation.org Fri Feb 16 13:58:14 2018 From: wminer at linuxfoundation.org (wminer at linuxfoundation.org) Date: Fri, 16 Feb 2018 13:58:14 +0000 Subject: [agl-discussions] Canceled event: App FW & Security Biweekly Call @ Wed Feb 28, 2018 8am - 9am (CST) (automotive-discussions@lists.linuxfoundation.org) Message-ID: <089e082fd43c562009056554bc51@google.com> This event has been canceled. Title: App FW & Security Biweekly Call 1. Please join my meeting. https://global.gotomeeting.com/join/324926029 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. Australia: +61 2 8355 1020 Austria: +43 1 2530 22520 Belgium: +32 (0) 28 08 4368 Canada: +1 (647) 497-9353 Canada (toll-free): 1 888 455 1389 Denmark: +45 69 91 89 28 Finland: +358 (0) 942 59 7850 France: +33 (0) 170 950 594 Germany: +49 (0) 692 5736 7317 India (toll-free): 000 800 100 7855 Ireland: +353 (0) 15 360 728 Italy: +39 0 247 92 13 01 Japan (toll-free): 0 120 663 800 Korea, Republic of (toll-free): 0806150880 Netherlands: +31 (0) 208 080 219 New Zealand: +64 9 280 6302 Norway: +47 75 80 32 07 Spain: +34 911 82 9906 Sweden: +46 (0) 852 500 186 Switzerland: +41 (0) 435 0167 13 United Kingdom: +44 (0) 330 221 0088 United States: +1 (646) 749-3129 United States (toll-free): 1 877 568 4106 Access Code: 324-926-029 Audio PIN: Shown after joining the meeting Meeting ID: 324-926-029 When: Wed Feb 28, 2018 8am ? 9am Central Time Where: https://www.gotomeeting.com/join/324926029 Calendar: automotive-discussions at lists.linuxfoundation.org Who: * Walt Miner - creator * Noriaki Fukuyasu * automotive-discussions at lists.linuxfoundation.org * dcauchy at linuxfoundation.org Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account automotive-discussions at lists.linuxfoundation.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2964 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3034 bytes Desc: not available URL: From wminer at linuxfoundation.org Fri Feb 16 13:58:25 2018 From: wminer at linuxfoundation.org (wminer at linuxfoundation.org) Date: Fri, 16 Feb 2018 13:58:25 +0000 Subject: [agl-discussions] Canceled event: AGL Dev Meeting - Weekly @ Tue Feb 27, 2018 8am - 9am (CST) (automotive-discussions@lists.linuxfoundation.org) Message-ID: <94eb2c0defa0eff80c056554bc0c@google.com> This event has been canceled. Title: AGL Dev Meeting - Weekly When: Tue Feb 27, 2018 8am ? 9am Central Time Where: See https://wiki.automotivelinux.org/dev-call-info Calendar: automotive-discussions at lists.linuxfoundation.org Who: * Walt Miner - creator * dcauchy at linuxfoundation.org * automotive-discussions at lists.linuxfoundation.org * Noriaki Fukuyasu Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account automotive-discussions at lists.linuxfoundation.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1927 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 1984 bytes Desc: not available URL: From wminer at linuxfoundation.org Fri Feb 16 13:59:01 2018 From: wminer at linuxfoundation.org (wminer at linuxfoundation.org) Date: Fri, 16 Feb 2018 13:59:01 +0000 Subject: [agl-discussions] Canceled event: [EG-Connectivity]Biweekly Call @ Thu Feb 22, 2018 8am - 9am (CST) (automotive-discussions@lists.linuxfoundation.org) Message-ID: <001a114b2f4618fd30056554bf93@google.com> This event has been canceled. Title: [EG-Connectivity]Biweekly Call Conference Information: 1. Join https://global.gotomeeting.com/join/254629557 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. Australia: +61 2 9091 7603 Italy: +39 0 699 26 68 65 Austria: +43 (0) 7 2088 0716 Japan (toll-free): 0 120 242 200 Belgium: +32 (0) 28 08 4372 Netherlands: +31 (0) 208 080 759 Canada: +1 (647) 497-9380 New Zealand: +64 9 974 9579 Canada (toll-free): 1 877 777 3281 Norway: +47 21 04 30 59 Denmark: +45 (0) 69 91 84 58 Spain: +34 931 76 1534 Finland: +358 (0) 931 58 1773 Sweden: +46 (0) 852 500 691 France: +33 (0) 170 950 590 Switzerland: +41 (0) 435 0026 89 Germany: +49 (0) 692 5736 7300 United Kingdom: +44 (0) 20 3713 5011 India (toll-free): 000 800 100 8227 United States (toll-free): 1 877 309 2070 Ireland: +353 (0) 15 360 756 United States: +1 (312) 757-3119 Access Code: 254-629-557 Audio PIN: Shown after joining the meeting Meeting ID: 254-629-557 When: Thu Feb 22, 2018 8am ? 9am Central Time Where: https://global.gotomeeting.com/join/254629557 Calendar: automotive-discussions at lists.linuxfoundation.org Who: * Walt Miner - creator * dcauchy at linuxfoundation.org * Jan-Simon Moeller * Noriaki Fukuyasu * automotive-discussions at lists.linuxfoundation.org Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account automotive-discussions at lists.linuxfoundation.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2775 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 2838 bytes Desc: not available URL: From wminer at linuxfoundation.org Fri Feb 16 13:59:29 2018 From: wminer at linuxfoundation.org (wminer at linuxfoundation.org) Date: Fri, 16 Feb 2018 13:59:29 +0000 Subject: [agl-discussions] Canceled event: EG Graphics and UI @ Mon Feb 19, 2018 8am - 9am (CST) (automotive-discussions@lists.linuxfoundation.org) Message-ID: <001a114b4528c9544b056554c071@google.com> This event has been canceled. Title: EG Graphics and UI 1. Please join my meeting. https://global.gotomeeting.com/join/552452861 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. Australia: +61 2 8355 1034 Austria: +43 7 2088 0716 Belgium: +32 (0) 28 08 4372 Canada (toll-free): 1 877 777 3281 Canada: +1 (647) 497-9372 Denmark: +45 69 91 84 58 Finland: +358 (0) 923 17 0556 France: +33 (0) 170 950 590 Germany: +49 (0) 692 5736 7206 India (toll-free): 000 800 100 8227 Ireland: +353 (0) 19 030 053 Italy: +39 0 699 26 68 65 Japan (toll-free): 0 120 242 200 Korea, Republic of (toll-free): 0806180880 Netherlands: +31 (0) 208 080 759 New Zealand: +64 9 974 9579 Norway: +47 21 04 30 59 Spain: +34 931 76 1534 Sweden: +46 (0) 852 500 691 Switzerland: +41 (0) 435 0026 89 United Kingdom: +44 (0) 20 3713 5011 United States (toll-free): 1 877 309 2070 United States: +1 (571) 317-3116 Access Code: 552-452-861 Audio PIN: Shown after joining the meeting Meeting ID: 552-452-861 When: Mon Feb 19, 2018 8am ? 9am Central Time Where: https://www.gotomeeting.com/join/552452861 Calendar: automotive-discussions at lists.linuxfoundation.org Who: * Walt Miner - creator * Jan-Simon Moeller * Noriaki Fukuyasu * automotive-discussions at lists.linuxfoundation.org * dcauchy at linuxfoundation.org Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account automotive-discussions at lists.linuxfoundation.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2816 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 2880 bytes Desc: not available URL: From wminer at linuxfoundation.org Fri Feb 16 13:59:47 2018 From: wminer at linuxfoundation.org (wminer at linuxfoundation.org) Date: Fri, 16 Feb 2018 13:59:47 +0000 Subject: [agl-discussions] Canceled event: AGL Dev Meeting - Weekly @ Tue Feb 20, 2018 8am - 9am (CST) (automotive-discussions@lists.linuxfoundation.org) Message-ID: <089e082fd43cd6e387056554c16c@google.com> This event has been canceled. Title: AGL Dev Meeting - Weekly When: Tue Feb 20, 2018 8am ? 9am Central Time Where: See https://wiki.automotivelinux.org/dev-call-info Calendar: automotive-discussions at lists.linuxfoundation.org Who: * Walt Miner - creator * dcauchy at linuxfoundation.org * automotive-discussions at lists.linuxfoundation.org * Noriaki Fukuyasu Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account automotive-discussions at lists.linuxfoundation.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1927 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 1984 bytes Desc: not available URL: From changhyeok.bae at gmail.com Sun Feb 18 14:23:19 2018 From: changhyeok.bae at gmail.com (Changhyeok Bae) Date: Sun, 18 Feb 2018 23:23:19 +0900 Subject: [agl-discussions] [RFC] Development / Gerrit Workflow tuning In-Reply-To: References: <2468018.AWp1xHMOA4@elrond> <20180216105511.05baf76d@d-jobol.iot.bzh> <26f9aea0-ecbd-5906-7a70-798f7bfd52d7@witz-inc.co.jp> <3043013.lOf7AYbRKJ@elrond> Message-ID: > I'd like to share some concern about the use of SRCREV and AUTOREV. I also agree with Jose and Jan-Simon and we need to fix SRCREV. My company (LG Electronics) uses yocto to develop LG webOS and we fix SRCREV. Actually we use tag and tag hash of component's repo in SRCREV. If you would like to use my company's method, I can let you know in detail. Thanks Changhyeok 2018-02-16 21:15 GMT+09:00 Kazumasa Mitsunari : > Hi > > Thank you for letting me know:) > > Best Regards > Kazumasa Mitsunari > > > On 2018?02?16? 21:07, Jan-Simon M?ller wrote: > >> Hi ! >> >> Am Freitag, 16. Februar 2018, 12:48:56 CET schrieb Kazumasa Mitsunari: >> >>> Hi >>> >>> I understood your concern. I agree with Jose. >>> >>> And I have a concern of the version. >>> >>> I'd like to know there is a rule for the version of recipe. >>> >>> The recipes developed in AGL are normally named as "XXXX_git.bb". >>> I'm understanding "git" is useful for people to use the latest code. >>> >>> I'd like to know we can choose to set version such like "XXXX_1.0.bb". >>> >> Yes, bitbake understands versions. And by default it will chose the >> 'latest'/'highest': >> >> E.g.: >> XYZ_1.0.bb >> XYZ_2.0.bb >> --> bitbake will build XYZ_2.0 >> >> But: >> XYZ_1.0.bb >> XYZ_2.0.bb >> XYZ_git.bb >> --> bitbake will build XYZ_git as it is considered the 'latest'. >> >> We can tweak this in the local.conf with >> PREFERRED_VERSION_XYZ="2.0" >> >> In my opinion, if there is no change of interface or behavior, the >>> change of SRCREV hash is enough. >>> If there are some changes of interface or behavior, it's thankful for >>> people to know the change. >>> >> Yes, you can version your recipes and make API changes visible by >> changing the >> version number. >> >> Best regards, >> Jan-Simon >> >> > -- > ******************************* > WITZ Corporation > ??????? ??????? > Base Technology Development Dept. > Advanced Basic Technology Sect. > Kazumasa Mitsunari > Mail:knimitz at witz-inc.co.jp > ******************************* > > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > -- Thanks Changhyeok -------------- next part -------------- An HTML attachment was scrubbed... URL: From wmizuno at jp.adit-jv.com Mon Feb 19 01:20:32 2018 From: wmizuno at jp.adit-jv.com (Mizuno, Wataru (ADITJ/SWG)) Date: Mon, 19 Feb 2018 01:20:32 +0000 Subject: [agl-discussions] haptic touch panel. In-Reply-To: References: , , <3AF4192FBB4D2C458558336708E909930500A82B@ky0exch01.adit-jv.com>, Message-ID: <3AF4192FBB4D2C458558336708E909930500DA3C@ky0exch01.adit-jv.com> Hello Matsuzawa-san, >But I think maybe some clarification on expected architecture (for reference demo) is needed. >(Which iof the possible architecture choice is used for this reference, etc.) Any prior study on classification on possible architecture exists? That may help us identifying where our reference should be positioned. I don't know the fixed architecture of haptic device. My opinion is to handle haptic device from app is better solution for wayland. Because current wayland application processes input events by theirselves since I think vibration feed back is result of input event. Best regards, Wataru Mizuno ADITJ / SWG +81-(0)566-56-0946 -----Original Message----- From: Takashi Matsuzawa [mailto:tmatsuzawa at xevo.com] Sent: Friday, February 16, 2018 7:49 PM To: Mizuno, Wataru (ADITJ/SWG); automotive-discussions at lists.linuxfoundation.org Subject: Re: haptic touch panel. Importance: Low Well, I can see W3C Vibration API and similar on various SDKs, but they are simple low-level on/off switch... (But anyway visible to application code.) ________________________________________ From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Takashi Matsuzawa Sent: Friday, February 16, 2018 3:00 PM To: Mizuno, Wataru (ADITJ/SWG); automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] haptic touch panel. [This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] I am sorry, I currently do not have my implementetaion. But I think maybe some clarification on expected architecture (for reference demo) is needed. (Which iof the possible architecture choice is used for this reference, etc.) Any prior study on classification on possible architecture exists? That may help us identifying where our reference should be positioned. I think production haptic devices are sometimes intelligent. The device (knobs, rotary switch) has ability to respond to the operation independent of the host sytsem. I know a case where an app (or system) download button coordinate information to the device, so that the device (with hardware cusor on screen) knows which coordinates are buttons and when to give feedbacks. Some knobs gives feedback by itself, regardless of host recognizing the input. But I feel this cannot be generalized. Also, it may also have benefit that host / app recognizes the input and give feedback. - The input device to be used is intelligent? Or not intelligent (e.g. simple piezo actuator that vibrates)? - Should app ACKs? Or UI framework (buttons on screen) ACKs? Or device itself ACKs? - What kind of feedback? Vibration? Audio? Visual? I personally feel common demo should be easy to be constructed, so that more team can develop / test on it, using the same reference. But of course, this does not prevent some teams using intelligent / proprietary solution. ________________________________________ From: Mizuno, Wataru (ADITJ/SWG) Sent: Friday, February 16, 2018 1:48 PM To: Takashi Matsuzawa; automotive-discussions at lists.linuxfoundation.org Subject: RE: haptic touch panel. Hello Matsuzawa-san, I'm interested in haptic device. Do you have any software design of this device? I couldn't find how the location of button is managed in the document on your mail. Regarding the wayland/weston, I think from wayland point of view haptic feedback is handled out of compositor. Because current wayland compositor like weston doesn't have any idea about which surface has what kind of feature. i.e. weston cannot know which surface has the role of button. But I sometimes sees haptic device on cockpit at motor show. I feel it is needed for automotive usecase. Best regards, Wataru Mizuno ADITJ / SWG +81-(0)566-56-0946 -----Original Message----- From: automotive-discussions-bounces at lists.linuxfoundation.org [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On Behalf Of Takashi Matsuzawa Sent: Friday, February 16, 2018 11:02 AM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] haptic touch panel. Re: button response Just curious: In production headunits who plays "beep" (response to the button push)? Maybe it is not the app calling "aplay"? There is dedicated process for this, or an IC outside of Linux? (So that requests from non-linux part of the system can be handled as well.) If having such "beep" service is a common practice, having "vibrate" service (which talks with the actuator on I2C bus) should be preferred. Though demo environment and production may be different, adding multiple devices on I2C bus may mean I need mutex or queueing among the apps / process to not to block the bus. That kind of function is outside of wayland/window system? Or part of it? ________________________________________ From: Takashi Matsuzawa Sent: Thursday, February 8, 2018 12:37 PM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: haptic touch panel. By the way, AGL UI currently can give sound feedback (beep) when buttons, etc. are pressed? That may be the places where we may also want to give vibration, or maybe flash (for hearing-impaired drivers) feedbacks. ________________________________________ From: Takashi Matsuzawa Sent: Wednesday, February 7, 2018 4:21 PM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: haptic touch panel. I can see an example deisgn of haptic feedback touch panel: http://www.ti.com/lit/ug/tidu968/tidu968.pdf It uses DRV2667 chip to drive piezo actuators which are attached to a WVGA touch panel. On the document how-to DIY information is available, but it is not available as kit to purchse. This is giving feedback by actuator vibration, actuators are controlled by I2C signals from the host. I can see hobbiest I2C breakout board for DRV2667 is available (they sell this wit piezo actuators as set), so it may not be too difficult to make up something to give touch vibration on panel. (Since AGL uses Full HD palnel, you may need multiples of actuators?) https://hackaday.io/project/3086-piezo-haptic-flex-module I think this might be very primitive demo. (Not really sure - since I have not tried it yet. Perhaps choice of waveform and number of actuators may give you good result.) Alternative (not necessarily the choice is binary) option might be that going with mor professional and high-quality devices, maybe collaborating with special device manufactureres. There may be more complex or advanced haptic solution available. e.g. simulating the surface by ultrasonic wave or static electricity, so that you can "feel" buttons on the panel. But they may need very special hardware or panels, which probably be difficult to get or hard to control. But it may mean the demo systm becomes very expensive, and not all of the members can easily try. _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From tmatsuzawa at xevo.com Mon Feb 19 02:25:44 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Mon, 19 Feb 2018 02:25:44 +0000 Subject: [agl-discussions] haptic touch panel. In-Reply-To: <3AF4192FBB4D2C458558336708E909930500DA3C@ky0exch01.adit-jv.com> References: , , <3AF4192FBB4D2C458558336708E909930500A82B@ky0exch01.adit-jv.com>, , <3AF4192FBB4D2C458558336708E909930500DA3C@ky0exch01.adit-jv.com> Message-ID: By the way, there may be patent issues with haptic enabled touch panels. (Commercial products may need careful research on it, I can see on media that lawsuit against smartphone companies related to such technology is recently common) But as far as the demo is for non-commercial purpose, it is free from such concern? Or, just use such device/proprietary library - existing product - and ask the developer to go to the licensees when he wants it to make it part of his product. Or, find out open-source / free implementation (but it may not guaranteed that such is free of patent issue.) ________________________________________ From: Mizuno, Wataru (ADITJ/SWG) Sent: Monday, February 19, 2018 10:20 AM To: Takashi Matsuzawa; automotive-discussions at lists.linuxfoundation.org Subject: RE: haptic touch panel. Hello Matsuzawa-san, >But I think maybe some clarification on expected architecture (for reference demo) is needed. >(Which iof the possible architecture choice is used for this reference, etc.) Any prior study on classification on possible architecture exists? That may help us identifying where our reference should be positioned. I don't know the fixed architecture of haptic device. My opinion is to handle haptic device from app is better solution for wayland. Because current wayland application processes input events by theirselves since I think vibration feed back is result of input event. Best regards, Wataru Mizuno ADITJ / SWG +81-(0)566-56-0946 -----Original Message----- From: Takashi Matsuzawa [mailto:tmatsuzawa at xevo.com] Sent: Friday, February 16, 2018 7:49 PM To: Mizuno, Wataru (ADITJ/SWG); automotive-discussions at lists.linuxfoundation.org Subject: Re: haptic touch panel. Importance: Low Well, I can see W3C Vibration API and similar on various SDKs, but they are simple low-level on/off switch... (But anyway visible to application code.) ________________________________________ From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Takashi Matsuzawa Sent: Friday, February 16, 2018 3:00 PM To: Mizuno, Wataru (ADITJ/SWG); automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] haptic touch panel. [This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] I am sorry, I currently do not have my implementetaion. But I think maybe some clarification on expected architecture (for reference demo) is needed. (Which iof the possible architecture choice is used for this reference, etc.) Any prior study on classification on possible architecture exists? That may help us identifying where our reference should be positioned. I think production haptic devices are sometimes intelligent. The device (knobs, rotary switch) has ability to respond to the operation independent of the host sytsem. I know a case where an app (or system) download button coordinate information to the device, so that the device (with hardware cusor on screen) knows which coordinates are buttons and when to give feedbacks. Some knobs gives feedback by itself, regardless of host recognizing the input. But I feel this cannot be generalized. Also, it may also have benefit that host / app recognizes the input and give feedback. - The input device to be used is intelligent? Or not intelligent (e.g. simple piezo actuator that vibrates)? - Should app ACKs? Or UI framework (buttons on screen) ACKs? Or device itself ACKs? - What kind of feedback? Vibration? Audio? Visual? I personally feel common demo should be easy to be constructed, so that more team can develop / test on it, using the same reference. But of course, this does not prevent some teams using intelligent / proprietary solution. ________________________________________ From: Mizuno, Wataru (ADITJ/SWG) Sent: Friday, February 16, 2018 1:48 PM To: Takashi Matsuzawa; automotive-discussions at lists.linuxfoundation.org Subject: RE: haptic touch panel. Hello Matsuzawa-san, I'm interested in haptic device. Do you have any software design of this device? I couldn't find how the location of button is managed in the document on your mail. Regarding the wayland/weston, I think from wayland point of view haptic feedback is handled out of compositor. Because current wayland compositor like weston doesn't have any idea about which surface has what kind of feature. i.e. weston cannot know which surface has the role of button. But I sometimes sees haptic device on cockpit at motor show. I feel it is needed for automotive usecase. Best regards, Wataru Mizuno ADITJ / SWG +81-(0)566-56-0946 -----Original Message----- From: automotive-discussions-bounces at lists.linuxfoundation.org [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On Behalf Of Takashi Matsuzawa Sent: Friday, February 16, 2018 11:02 AM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] haptic touch panel. Re: button response Just curious: In production headunits who plays "beep" (response to the button push)? Maybe it is not the app calling "aplay"? There is dedicated process for this, or an IC outside of Linux? (So that requests from non-linux part of the system can be handled as well.) If having such "beep" service is a common practice, having "vibrate" service (which talks with the actuator on I2C bus) should be preferred. Though demo environment and production may be different, adding multiple devices on I2C bus may mean I need mutex or queueing among the apps / process to not to block the bus. That kind of function is outside of wayland/window system? Or part of it? ________________________________________ From: Takashi Matsuzawa Sent: Thursday, February 8, 2018 12:37 PM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: haptic touch panel. By the way, AGL UI currently can give sound feedback (beep) when buttons, etc. are pressed? That may be the places where we may also want to give vibration, or maybe flash (for hearing-impaired drivers) feedbacks. ________________________________________ From: Takashi Matsuzawa Sent: Wednesday, February 7, 2018 4:21 PM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: haptic touch panel. I can see an example deisgn of haptic feedback touch panel: http://www.ti.com/lit/ug/tidu968/tidu968.pdf It uses DRV2667 chip to drive piezo actuators which are attached to a WVGA touch panel. On the document how-to DIY information is available, but it is not available as kit to purchse. This is giving feedback by actuator vibration, actuators are controlled by I2C signals from the host. I can see hobbiest I2C breakout board for DRV2667 is available (they sell this wit piezo actuators as set), so it may not be too difficult to make up something to give touch vibration on panel. (Since AGL uses Full HD palnel, you may need multiples of actuators?) https://hackaday.io/project/3086-piezo-haptic-flex-module I think this might be very primitive demo. (Not really sure - since I have not tried it yet. Perhaps choice of waveform and number of actuators may give you good result.) Alternative (not necessarily the choice is binary) option might be that going with mor professional and high-quality devices, maybe collaborating with special device manufactureres. There may be more complex or advanced haptic solution available. e.g. simulating the surface by ultrasonic wave or static electricity, so that you can "feel" buttons on the panel. But they may need very special hardware or panels, which probably be difficult to get or hard to control. But it may mean the demo systm becomes very expensive, and not all of the members can easily try. _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From Ahmad.BaniJamali at oulu.fi Mon Feb 19 14:40:10 2018 From: Ahmad.BaniJamali at oulu.fi (Ahmad Bani Jamali) Date: Mon, 19 Feb 2018 14:40:10 +0000 Subject: [agl-discussions] Invitation for an online Survey_Software Architecture for automotive IoT Cloud Platform Message-ID: Hi all, To remind you about the survey if did not have time to go through it before. All the Best, Ahmad From: Ahmad Bani Jamali Sent: keskiviikko 7. helmikuuta 2018 17.23 To: 'automotive-discussions at lists.linuxfoundation.org' ; 'automotive-sat at lists.linuxfoundation.org' Subject: Invitation for an online Survey_Software Architecture for automotive IoT Cloud Platform Dear AGL partners, We empirically investigate "software architectures of automotive IoT cloud platforms" including design patterns (styles), quality attributes, evaluation methods, and tools. For this research, we depend on your contribution! We would very much appreciate if you fill out our survey and also forward it to other people with relevant expertise. Link to survey: https://link.webropolsurveys.com/S/EDEA9BBBACF9E0FB Thank you very much for your kind support! Ahmad Banijamali & Pasi Kuvaja University of Oulu M3S Research Unit http://www.oulu.fi/m3s/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From wminer at linuxfoundation.org Tue Feb 20 03:12:04 2018 From: wminer at linuxfoundation.org (Walt Miner) Date: Tue, 20 Feb 2018 12:12:04 +0900 Subject: [agl-discussions] Agenda for SAT and EG Meeting at AMM In-Reply-To: References: Message-ID: Several people have asked about the agenda for Thursday's meetings. It is available on the Wiki page [1] [1] https://wiki.automotivelinux.org/agl-distro/feb2018-f2f Regards, Walt On Fri, Feb 16, 2018 at 10:21 AM, Walt Miner wrote: > I posted a preliminary agenda for SAT and Expert Group meetings on > Thursday of the AMM in Tokyo[1]. We have two rooms that we can utilize so > I created two parallel tracks during the day. I think I accommodated all > of the Expert Group requests and topics we set aside for F2F meetings at > the AMM. If I left out an EG or a topic, please let me know ASAP so I can > re-arrange the schedule. > > Regards. > Walt > > > > > [1] https://wiki.automotivelinux.org/agl-distro/feb2018-f2f > > > > -- > Walt Miner > > > > Engineering Project Manager > The Linux Foundation > mobile: +1.847.502.7087 > > > Visit us at: > automotive.linuxfoundation.org > www.linuxfoundation.org > > > -- Walt Miner Engineering Project Manager The Linux Foundation mobile: +1.847.502.7087 Visit us at: automotive.linuxfoundation.org www.linuxfoundation.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christian.Benien at nuance.com Tue Feb 20 08:55:20 2018 From: Christian.Benien at nuance.com (Benien, Christian) Date: Tue, 20 Feb 2018 08:55:20 +0000 Subject: [agl-discussions] Running AGL on Windows laptop / broken download links Message-ID: Hi, I'm trying to get started with application development for AGL. The documentation for building the apps is pretty good and easy to follow. I'm currently stuck when trying to run my app on AGL. I don't have a dedicated target board, all I have is my Windows laptop. I've seen some guides for running the QEMU image in VirtualBox, but all download links to QEMU images are broken, e.g. on this page here: https://wiki.automotivelinux.org/agl-distro/release-notes#eel_501 Browsing the download server, I've possibly found the correct link: https://download.automotivelinux.org/AGL/release/eel/5.0.1/qemux86-64/deploy/images/qemux86-64/agl-demo-platform-crosssdk-qemux86-64.vmdk.xz I have some mixed success running this in VirtualBox. Sometimes I get a broken UI, sometimes the screen stays black. Two questions: * Is it possible at all to run AGL on a Windows laptop? Should the above image work? Anything special to configure in VirtualBox? * Can somebody please fix the links? Thanks and best regards Christian -------------- next part -------------- An HTML attachment was scrubbed... URL: From tmatsuzawa at xevo.com Tue Feb 20 11:51:58 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Tue, 20 Feb 2018 11:51:58 +0000 Subject: [agl-discussions] UP2 board DP connection? In-Reply-To: References: Message-ID: Hello. Just tried alternative ("active") DP to HDMI cable and the display lit up even if the cable is connected to DP port. ________________________________________ From: Dinh, Kien T Sent: Friday, February 16, 2018 8:15 PM To: VanCutsem, Geoffroy; Takashi Matsuzawa; automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] UP2 board DP connection? Matsuzawa-san, I think you can try with the DP to HDMI active adapter. On the Up squared forum they reported that the active one worked instead of passive one. Regards, Kien ?On 2018/02/16 19:52, "automotive-discussions-bounces at lists.linuxfoundation.org on behalf of VanCutsem, Geoffroy" wrote: Hi Matsuzawa-san, > -----Original Message----- > From: Takashi Matsuzawa [mailto:tmatsuzawa at xevo.com] > Sent: Friday, February 16, 2018 10:55 AM > To: VanCutsem, Geoffroy ; automotive- > discussions at lists.linuxfoundation.org > Subject: Re: UP2 board DP connection? > > Hello. > Thank you for your info. > > I just tried and output is like this. > > So, DP-1 is seen by Linux kernel but there is no display connected? > But I am actually connecting my display (powerd on) to DP, but using DP<- > >HDMI conversion cable. > > Cable is wrong?(I should have avoided a cheap one??) Unfortunately his is > the only (full)DP cable in my office, so I cannot try another today.. I don't have a UP Squared board to test with but this is a possibility. I would try booting a live distribution (Ubuntu/Fedora) from a USB stick and look at the output reported there (just to rule out something to do with AGL itself). I must confess that I tend to stay away from cheap cables these days, I've had too many issues with them in the past and it usually ends up costing me more in troubleshooting time than the extra money needed to buy a good quality one. I would definitely try different cables (DP-to-HDMI adapter) and also make sure the HDMI cable itself is good (try swapping it out with the one you have connected to the UP Square board HDMI connector now). > > >Connector info > >-------------- > >connector 51: type DP-1, status: disconnected > > DPCD rev: 0 > > audio support: no > > DP branch device present: no > > modes: > >connector 58: type HDMI-A-1, status: connected > > name: > > physical dimensions: 520x320mm > > subpixel order: Unknown > > CEA rev: 3 > > audio support: yes > > modes: > > id 62:.... > > ________________________________________ > From: VanCutsem, Geoffroy > Sent: Friday, February 16, 2018 6:16 PM > To: Takashi Matsuzawa; automotive-discussions at lists.linuxfoundation.org > Subject: RE: UP2 board DP connection? > > > > > -----Original Message----- > > From: automotive-discussions-bounces at lists.linuxfoundation.org > > [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On > > Behalf Of Takashi Matsuzawa > > Sent: Friday, February 16, 2018 1:40 AM > > To: automotive-discussions at lists.linuxfoundation.org > > Subject: Re: [agl-discussions] UP2 board DP connection? > > > > By the way, the following method of knowing output display names works? > > > > >$ journalctl |grep Output > > > > I Tried this on my UP2 board with master snapshot and ee 5.0.1 but > > could not get HDMI-A-1 from it. > > If your kernel has the debug filesystem option turned on (and debugfs is > actually mounted), you should be able to see all display outputs available > (whether connected or not) in /sys/kernel/debug/dri/0/i915_display_info. I > > > > > Looking into weston.log in /run/..., I can see HDMI-A-1 name. > > Will I see two Output names if I connect two displays to this board > > and everything works well? > > > > ________________________________________ > > From: Takashi Matsuzawa > > Sent: Thursday, February 15, 2018 2:48 PM > > To: automotive-discussions at lists.linuxfoundation.org > > Subject: UP2 board DP connection? > > > > Hello. > > > > I am playing with my UP2 board, connecting two displays to the board, > > one to HDMI port and another to DP (not eDP) port. > > (The board has HDMI/DP stacked socket). > > > > I can see only HDMI port is working, and DP is not. > > (After power-on, BIOS screen and after are only displayed on the > > display attached to HDMI port). > > > > Is there how-to information of the either or both of below? > > > > - Use DP as my display (connect my display to DP, boot my board and > > see BIOS and after are displayed on the display). > > > > - Enable both HDMI and DP displays (connect two displayes to HDMI port > > and DP port, and let the system recognize that I have two displayes > > attached to the board). > > > > I looked into the BIOS setting menus, but I am not sure if I have > > options for this there. > > > > Any comment or suggestion is appreciated. > > _______________________________________________ > > automotive-discussions mailing list > > automotive-discussions at lists.linuxfoundation.org > > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussi > > ons _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From ashley.stevenson at forgerock.com Wed Feb 21 01:14:24 2018 From: ashley.stevenson at forgerock.com (Ashley Stevenson) Date: Wed, 21 Feb 2018 10:14:24 +0900 Subject: [agl-discussions] First Vehicle-to-Cloud Expert Group Tomorrow @ AMM Message-ID: Hi everyone, You're invited to join our very first Vehicle-to-Cloud Expert Group tomorrow, here in Tokyo, 11AM, in Katsuga. If you're not in Tokyo this week, we will be working to establish the regular meeting cadence. We now have the shell of our wiki page posted here: (https://wiki.automotivelinux.org/eg-v2c). If you're interested in joining, please add you name and company to the member list. Thanks! -- Ashley Stevenson, ForgeRock -------------- next part -------------- An HTML attachment was scrubbed... URL: From mkelly at xevo.com Wed Feb 21 01:21:17 2018 From: mkelly at xevo.com (Martin Kelly) Date: Tue, 20 Feb 2018 17:21:17 -0800 Subject: [agl-discussions] Next steps on OpenCL support for the H3 Message-ID: <1600f958-9cbf-b4db-2794-b78ac778e5ba@xevo.com> Hi, As you know, I recently submitted patches for enabling OpenCL support on the Renesas H3 and Salvator-X boards [1]. Kurokawa-san had concerns about using the OpenCL drivers in the same package as the current gles-user-module and says that Renesas can support only the existing GLES drivers [2]. I would like to drive consensus on the right way to handle the packaging here so that we can get OpenCL support added into the H3. Since the H3 has a very capable GPU, it's an immensely useful feature. I think the central question is about the differences between the Renesas OpenCL drivers and the existing GLES drivers [3]. It appears these drivers are released at different cadences, such that the GLES drivers have Yocto 3.40 support but the OpenCL drivers do not. In addition, it appears that the OpenCL drivers replace the GLES drivers, as they provide both an OpenCL and a GLES stack. For this reason, using both may create issues, and it's not clear whether it's safe to mix and match the GLES with the OpenCL drivers, or if they are mutually exclusive. Kurokawa-san or others at Renesas: What is the recommended way to use the OpenCL drivers on the H3 with AGL? In other words, how should I change the OpenCL patches so we can get OpenCL supported officially in AGL :) ? I am happy to adapt my patches to make this work but am unsure about the best way to do it, since the driver code is proprietary. Thanks, Martin [1] https://gerrit.automotivelinux.org/gerrit/#/c/13375/ https://gerrit.automotivelinux.org/gerrit/#/c/13377/ https://gerrit.automotivelinux.org/gerrit/#/c/13379/ https://gerrit.automotivelinux.org/gerrit/#/c/13381/ [2] https://gerrit.automotivelinux.org/gerrit/#/c/13375/ [3] Existing GLES drivers: https://www.renesas.com/en-eu/solutions/automotive/rcar-demoboard.html OpenCL drivers: https://www.renesas.com/en-us/solutions/automotive/rcar-opencl.html From ashley.stevenson at forgerock.com Thu Feb 22 07:28:55 2018 From: ashley.stevenson at forgerock.com (Ashley Stevenson) Date: Thu, 22 Feb 2018 16:28:55 +0900 Subject: [agl-discussions] Slides - First Vehicle-to-Cloud Expert Group Meeting Message-ID: Hi all, Many thanks to those who participated in today's first V2C EG in Tokyo today. Find attached the short slide deck from today's meeting. I will also be publishing the notes I took during the meeting to the new V2C EG Wiki. I see that some of you have already added your name to the attendee list for today on the wiki. If you have not already, please do, as I did not catch the spelling of some names, and would like to add to the meeting minutes. Finally, please feel free to email me directly with any suggestions for use cases, or other topics, along with suggestions for a recurring virtual meeting time slot. Best, -- Ashley Stevenson @ ForgeRock -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: V2C EG Meeting 1 20180222.pdf Type: application/pdf Size: 1745778 bytes Desc: not available URL: From jung at drimaes.com Thu Feb 22 08:14:39 2018 From: jung at drimaes.com (=?UTF-8?B?7KCV7JiB66y4?=) Date: Thu, 22 Feb 2018 17:14:39 +0900 Subject: [agl-discussions] QEMU resolution isuue. In-Reply-To: <182eb92ecf844e23898c4b2a8cad13a5@JPA000SECMN07.palet.jp.panasonic.com> References: <182eb92ecf844e23898c4b2a8cad13a5@JPA000SECMN07.palet.jp.panasonic.com> Message-ID: Hi, Thank you for ur reply. But, It is not working for me. I knew new way to run qemu useing 'runqemu' command on yocto. Thanks about that. Regards, Josh,Jung 2018-02-06 16:14 GMT+09:00 : > Hi, > > > > You might need ?-vga virtio? and ?-usbdevice tablet?. > > You can also use ?runqemu? if you built your own yocto/agl environment. > > > > Here is my instructions to run QEMU. > > > > $ cd > > $ source poky/oe-init-build-env > > $ runqemu tmp/deploy/images/qemux86-64/agl-demo-platform-qemux86-64.qemuboot.conf > kvm serial > > > > For your reference, following is the part of log of runqemu.. > > > > runqemu - INFO - Running tmp/work/x86_64-linux/qemu- > helper-native/1.0-r1/recipe-sysroot-native/usr/bin//qemu-system-x86_64 > -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:02 -netdev > tap,id=net0,ifname=tap0,script=no,downscript=no -drive > file=tmp/deploy/images/qemux86-64/agl-demo-platform- > qemux86-64-20180206055341.rootfs.ext4,if=virtio,format=raw -show-cursor > -usb -usbdevice tablet -device virtio-rng-pci -vga virtio -machine q35 > -cpu kvm64 -cpu qemu64,+ssse3,+sse4.1,+sse4.2,+popcnt -enable-kvm -m 2048 > -serial mon:vc -serial mon:stdio -serial null -kernel > tmp/deploy/images/qemux86-64/bzImage--4.10.17+git0+ > 40ee48ac09_c1d8c4408b-r0-qemux86-64-20171214150211.bin -append > 'root=/dev/vda rw highres=off console=ttyS0 mem=2048M ip=192.168.7.2:: > 192.168.7.1:255.255.255.0 vga=0 uvesafb.mode_option=1024x768-32 > oprofile.timer=1 uvesafb.task_timeout=-1 ' > > > > Regards, > > Tadao Tanikawa > > > > *From:* automotive-discussions-bounces at lists.linuxfoundation.org [mailto: > automotive-discussions-bounces at lists.linuxfoundation.org] *On Behalf Of * > ??? > *Sent:* Tuesday, February 06, 2018 1:51 PM > *To:* Matt Ranostay > *Cc:* automotive-discussions at lists.linuxfoundation.org > *Subject:* Re: [agl-discussions] QEMU resolution isuue. > > > > Hi Matt, > Thanks your reply. > > I used "-show-cursor" command like below. > > # sudo qemu-system-x86_64 -enable-kvm -m 2048 -hda > agl-demo-platform-crosssdk-qemux86-64-20180107080143.v > qemu64,+ssse3,+sse4.1,+sse4.2,+popcnt -vga std -show-cursor -device > virtio-rng-pci -serial mon:stdio -serial null -soundhw hda -net nic,vlan=0 > -net user,hostfwd=tcp::2222-:22 -netdev bridge,br=br0,id=net0 -device > virtio-net-pci,netdev=net0,mac=52:54:00:12:34:59 > > > > 2018-02-06 13:44 GMT+09:00 Matt Ranostay : > > On Mon, Feb 5, 2018 at 8:33 PM, ??? wrote: > > Hi All, > > > > Now I,m testing AGL 5.0 on QEMU. > > > > I have a problem on my testing. > > QEMU resolution is not currects like attachments[attach1]. > > > > > > So, I tried 2 way. > > First, I modified mode to 1080x1920 weston.ini files. ( weston.ivi dir : > > /etc/xdg/weston/weston.ini ) > > But, It was not still working well. > > > > Second, I added transform=270 to weston.ini files. ( weston.ivi dir : > > /etc/xdg/weston/weston.ini ) > > resolution is little bit OK like attatchments[attatch2], but mouse point > did > > not operate normally. > > > > > > Please help me in this regard. > > > > You need to pass "-show-cursor" on your qemu command line. > > - Matt > > > > > > Thanks & Regards, > > Josh. > > > > > > ( reference site : > > http://docs.automotivelinux.org/docs/getting_started/en/ > dev/reference/homescreen/ > > ) > > ( refetence site : > > https://lists.linuxfoundation.org/pipermail/automotive- > discussions/2017-January/003335.html > > ) > > > > > > -- > > Jung Young Moon DrimAES Inc. > > > > Address ?? ??? ???? 273 ???????2? 803? ????? > > Mobile 010-4907-2117 > > Mail jung at drimaes.com > > > > _______________________________________________ > > automotive-discussions mailing list > > automotive-discussions at lists.linuxfoundation.org > > https://lists.linuxfoundation.org/mailman/listinfo/ > automotive-discussions > > > > > > > -- > > *Jung Young Moon DrimAES Inc.* > > > *Address* ?? ??? ???? 273 ???????2? 803? ????? > *Mobile* 010-4907-2117 > > *Mail* jung at drimaes.com > -- *Jung Young Moon DrimAES Inc.* *Address* ?? ??? ???? 273 ???????2? 803? ????? *Mobile* 010-4907-2117 *Mail* jung at drimaes.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jung at drimaes.com Thu Feb 22 08:24:18 2018 From: jung at drimaes.com (=?UTF-8?B?7KCV7JiB66y4?=) Date: Thu, 22 Feb 2018 17:24:18 +0900 Subject: [agl-discussions] How to see Applications Debug Message ? Message-ID: Hi everyone, I am working with AGL 5.0 on QEMU and testing Applications(ex.Homescreen ... ) My question is that how can I see debug message? In Homescreen source code(main.c,Homescreen project), it uses debug message like qDebg(...) or HMI_DEBUG(...). But when I execute Homescreen on AGL, I couldn't see any message. Do you have any way to see debug message? Please help me in this regard. Thanks & Regards, Josh. automotive-discussions at lists.linuxfoundation.org -- *Jung Young Moon DrimAES Inc.* *Address* ?? ??? ???? 273 ???????2? 803? ????? *Mobile* 010-4907-2117 *Mail* jung at drimaes.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jose.bollo at iot.bzh Thu Feb 22 08:36:11 2018 From: jose.bollo at iot.bzh (=?UTF-8?B?Sm9zw6k=?= Bollo) Date: Thu, 22 Feb 2018 09:36:11 +0100 Subject: [agl-discussions] How to see Applications Debug Message ? In-Reply-To: References: Message-ID: <20180222093611.187b4fa7@d-jobol.iot.bzh> On Thu, 22 Feb 2018 17:24:18 +0900 ??? wrote: > Hi everyone, Hi josh, Look at the file /etc/afm/unit.env.d/hmi-debug Message are reported in journal. Best regards Jos? Bollo > I am working with AGL 5.0 on QEMU and testing > Applications(ex.Homescreen ... ) > My question is that how can I see debug message? > > > In Homescreen source code(main.c,Homescreen project), it uses debug > message like qDebg(...) or HMI_DEBUG(...). > But when I execute Homescreen on AGL, I couldn't see any message. > > > Do you have any way to see debug message? > > > > Please help me in this regard. > > > Thanks & Regards, > Josh. > > > > > automotive-discussions at lists.linuxfoundation.org From jung at drimaes.com Thu Feb 22 08:41:28 2018 From: jung at drimaes.com (=?UTF-8?B?7KCV7JiB66y4?=) Date: Thu, 22 Feb 2018 17:41:28 +0900 Subject: [agl-discussions] How to see Applications Debug Message ? In-Reply-To: <20180222093611.187b4fa7@d-jobol.iot.bzh> References: <20180222093611.187b4fa7@d-jobol.iot.bzh> Message-ID: Thank you for your fast reply. I checked that dir you mentioned, but there are only 2 things "qt-for-ivi-shell" and "qtquickcontrols2-style". there aren't hmi-debug. Should I need to any setting? when yocto build? or another settings? Thanks & Regards, Josh. 2018-02-22 17:36 GMT+09:00 Jos? Bollo : > On Thu, 22 Feb 2018 17:24:18 +0900 > ??? wrote: > > > Hi everyone, > > Hi josh, > > Look at the file /etc/afm/unit.env.d/hmi-debug > > Message are reported in journal. > > Best regards > Jos? Bollo > > > I am working with AGL 5.0 on QEMU and testing > > Applications(ex.Homescreen ... ) > > My question is that how can I see debug message? > > > > > > In Homescreen source code(main.c,Homescreen project), it uses debug > > message like qDebg(...) or HMI_DEBUG(...). > > But when I execute Homescreen on AGL, I couldn't see any message. > > > > > > Do you have any way to see debug message? > > > > > > > > Please help me in this regard. > > > > > > Thanks & Regards, > > Josh. > > > > > > > > > > automotive-discussions at lists.linuxfoundation.org > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > -- *Jung Young Moon DrimAES Inc.* *Address* ?? ??? ???? 273 ???????2? 803? ????? *Mobile* 010-4907-2117 *Mail* jung at drimaes.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Satoru.Ueda at jp.sony.com Thu Feb 22 09:23:07 2018 From: Satoru.Ueda at jp.sony.com (Satoru Ueda) Date: Thu, 22 Feb 2018 18:23:07 +0900 Subject: [agl-discussions] Linux Foundation Japan Technical Jamboree #64 Message-ID: <9656dca2-05b2-3796-30e3-569e2abe093b@sony.com> Dear All AGL members, # especially residents in Japan. Please allow me to introduce you of a technical discussion event of OSS for embedded system. https://elinux.org/Japan_Technical_Jamboree_64 CELP have been holding a technical discussion event in Tokyo which is named "Japan Technical Jamboree" since 2004 ( https://elinux.org/Japan_Technical_Jamboree_Guidance ). The next Jamboree will be held on Friday next week at Nakano Sunplaza starting at 10AM. All of you may attend at free of charge without any registration. - In the morning session, Tim Bird (Technical Advisory Board member of Linux community, Fuego maintainer) will summarize the recent topics of embedded system OSS. - It is also a great chance to discuss about "Fuego". - In the afternoon, you can bring your topics to make detail technological discussion. (Please contact me. I will add your topics into the agenda). As many of you may know, many of the core developers of embedded system OSS are assembling there and making heated discussion (in Japanese ). https://elinux.org/Japan_Technical_Jamboree_63#Agenda Here, in the previous Japan Jamboree wiki, you will find the video archives are linked from the agenda list. Hope above informative for you. Best regards, S. Ueda -- | Satoru Ueda / TEL: +81-(0)50-3750-3882 | Alliance Management Sec. UX Planning Dept. UX Business Development Div. | Sony Corporation From jose.bollo at iot.bzh Thu Feb 22 09:51:58 2018 From: jose.bollo at iot.bzh (=?UTF-8?B?Sm9zw6k=?= Bollo) Date: Thu, 22 Feb 2018 10:51:58 +0100 Subject: [agl-discussions] How to see Applications Debug Message ? In-Reply-To: References: <20180222093611.187b4fa7@d-jobol.iot.bzh> Message-ID: <20180222105158.14a5d76a@d-jobol.iot.bzh> On Thu, 22 Feb 2018 17:41:28 +0900 ??? wrote: > Thank you for your fast reply. > > I checked that dir you mentioned, but there are only 2 things > "qt-for-ivi-shell" and "qtquickcontrols2-style". > there aren't hmi-debug. > > Should I need to any setting? when yocto build? or another settings? I think that it depends on the version of AGL you are using (I'm using master/rocko). So create that file: cat > /etc/afm/unit.env.d/hmi-debug << EOC #You can select log level of HMI framework #1 ERROR #2 WARNING #3 NOTICE #4 INFO #5 DEBUG #If you want to output debug log about hmi-framework, please uncomment the following. #USE_HMI_DEBUG=5 EOC See https://git.automotivelinux.org/AGL/meta-agl-devel/tree/meta-hmi-framework/recipes-demo-hmi/hmi-debug Best Regards Jos? Bollo > > > > Thanks & Regards, > Josh. > > > 2018-02-22 17:36 GMT+09:00 Jos? Bollo : > > > On Thu, 22 Feb 2018 17:24:18 +0900 > > ??? wrote: > > > > > Hi everyone, > > > > Hi josh, > > > > Look at the file /etc/afm/unit.env.d/hmi-debug > > > > Message are reported in journal. > > > > Best regards > > Jos? Bollo > > > > > I am working with AGL 5.0 on QEMU and testing > > > Applications(ex.Homescreen ... ) > > > My question is that how can I see debug message? > > > > > > > > > In Homescreen source code(main.c,Homescreen project), it uses > > > debug message like qDebg(...) or HMI_DEBUG(...). > > > But when I execute Homescreen on AGL, I couldn't see any message. > > > > > > > > > Do you have any way to see debug message? > > > > > > > > > > > > Please help me in this regard. > > > > > > > > > Thanks & Regards, > > > Josh. > > > > > > > > > > > > > > > automotive-discussions at lists.linuxfoundation.org > > > > _______________________________________________ > > automotive-discussions mailing list > > automotive-discussions at lists.linuxfoundation.org > > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > > > > > From jose.bollo at iot.bzh Thu Feb 22 16:21:20 2018 From: jose.bollo at iot.bzh (=?UTF-8?B?Sm9zw6k=?= Bollo) Date: Thu, 22 Feb 2018 17:21:20 +0100 Subject: [agl-discussions] Status of actual master Message-ID: <20180222172120.6946e288@d-jobol.iot.bzh> I'm currently trying to run master version but I have no home screen displayed. I filled SPEC-1303. https://jira.automotivelinux.org/browse/SPEC-1303 I'd like to know whether I'm the only one to get that issue. Best regards Jos? From srinath.duraisamy at intel.com Thu Feb 22 23:28:40 2018 From: srinath.duraisamy at intel.com (Duraisamy, Srinath) Date: Thu, 22 Feb 2018 23:28:40 +0000 Subject: [agl-discussions] Electric Eel v5.0.1 build parted command not found Message-ID: Hi all, I build Eel v5.0.1 for intel platforms and able to flash it on a USB disk. But when I try flash it on mmcblk in target platform. I am getting the below error mkefi-agl.sh parted: command not found Failed to create MSDOS partition table I tried the latest mkefi-agl.sh script and the script in Eel v5.0.1 but I get the same error in both cases. Do I have to try with a different script ? Thanks in advance. Srinath -------------- next part -------------- An HTML attachment was scrubbed... URL: From mkelly at xevo.com Fri Feb 23 00:04:38 2018 From: mkelly at xevo.com (Martin Kelly) Date: Thu, 22 Feb 2018 16:04:38 -0800 Subject: [agl-discussions] Electric Eel v5.0.1 build parted command not found In-Reply-To: References: Message-ID: <48058762-376e-99c7-0abd-fb0a90522380@xevo.com> Hi, I believe mkefi-agl.sh should be run from your desktop, not from the target device. If you do that, you can just apt/yum install parted and it should work. parted is not typically installed on a target image, though you could install it if you wanted to. On 02/22/2018 03:28 PM, Duraisamy, Srinath wrote: > > Hi all, > > I build Eel v5.0.1 for intel platforms and able to flash it on a USB disk. > > But when I try flash it on ?mmcblk in target platform. I am getting > the below error > > mkefi-agl.sh ?parted: command not found > > Failed to create MSDOS partition table > > I tried the latest mkefi-agl.sh script and the script in Eel v5.0.1 > but I get the same error in both cases. > > Do I have to try with a different script ? > > Thanks in advance. > > Srinath > > > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions -------------- next part -------------- An HTML attachment was scrubbed... URL: From srinath.duraisamy at intel.com Fri Feb 23 01:41:57 2018 From: srinath.duraisamy at intel.com (Duraisamy, Srinath) Date: Fri, 23 Feb 2018 01:41:57 +0000 Subject: [agl-discussions] Electric Eel v5.0.1 build parted command not found In-Reply-To: <48058762-376e-99c7-0abd-fb0a90522380@xevo.com> References: <48058762-376e-99c7-0abd-fb0a90522380@xevo.com> Message-ID: Hi Thanks for the mail. Any idea how can I flash the AGL image booted from USB onto mmcblk ?? Thanks Srinath From: Martin Kelly [mailto:mkelly at xevo.com] Sent: Thursday, February 22, 2018 4:05 PM To: Duraisamy, Srinath ; automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] Electric Eel v5.0.1 build parted command not found Hi, I believe mkefi-agl.sh should be run from your desktop, not from the target device. If you do that, you can just apt/yum install parted and it should work. parted is not typically installed on a target image, though you could install it if you wanted to. On 02/22/2018 03:28 PM, Duraisamy, Srinath wrote: Hi all, I build Eel v5.0.1 for intel platforms and able to flash it on a USB disk. But when I try flash it on mmcblk in target platform. I am getting the below error mkefi-agl.sh parted: command not found Failed to create MSDOS partition table I tried the latest mkefi-agl.sh script and the script in Eel v5.0.1 but I get the same error in both cases. Do I have to try with a different script ? Thanks in advance. Srinath _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions -------------- next part -------------- An HTML attachment was scrubbed... URL: From mkelly at xevo.com Fri Feb 23 02:03:25 2018 From: mkelly at xevo.com (Martin Kelly) Date: Thu, 22 Feb 2018 18:03:25 -0800 Subject: [agl-discussions] Electric Eel v5.0.1 build parted command not found In-Reply-To: References: <48058762-376e-99c7-0abd-fb0a90522380@xevo.com> Message-ID: The guide here should tell you how: http://docs.automotivelinux.org/docs/getting_started/en/dev/reference/machines/intel.html Note this section: http://docs.automotivelinux.org/docs/getting_started/en/dev/reference/machines/intel.html#create-a-bootable-media You need to insert the SD card into your desktop machine and then figure out which device file it is. On 02/22/2018 05:41 PM, Duraisamy, Srinath wrote: > > Hi Thanks for the mail. > > Any idea how can I flash the AGL image ?booted from USB onto mmcblk ?? > > Thanks > > Srinath > > *From:*Martin Kelly [mailto:mkelly at xevo.com] > *Sent:* Thursday, February 22, 2018 4:05 PM > *To:* Duraisamy, Srinath ; > automotive-discussions at lists.linuxfoundation.org > *Subject:* Re: [agl-discussions] Electric Eel v5.0.1 build parted > command not found > > Hi, > > I believe mkefi-agl.sh should be run from your desktop, not from the > target device. If you do that, you can just apt/yum install parted and > it should work. parted is not typically installed on a target image, > though you could install it if you wanted to. > > On 02/22/2018 03:28 PM, Duraisamy, Srinath wrote: > > Hi all, > > I build Eel v5.0.1 for intel platforms and able to flash it on a > USB disk. > > But when I try flash it on ?mmcblk in target platform. I am > getting the below error > > mkefi-agl.sh ?parted: command not found > > Failed to create MSDOS partition table > > I tried the latest mkefi-agl.sh script and the script in Eel > v5.0.1 but I get the same error in both cases. > > Do I have to try with a different script ? > > Thanks in advance. > > Srinath > > > > > _______________________________________________ > > automotive-discussions mailing list > > automotive-discussions at lists.linuxfoundation.org > > > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tmatsuzawa at xevo.com Fri Feb 23 02:18:53 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Fri, 23 Feb 2018 02:18:53 +0000 Subject: [agl-discussions] Electric Eel v5.0.1 build parted command not found In-Reply-To: References: <48058762-376e-99c7-0abd-fb0a90522380@xevo.com> , Message-ID: In case you are trying below (installing on eMMC), rebuilding image (so that parted, etc. are there) may be necessary. http://docs.automotivelinux.org/docs/getting_started/en/dev/reference/footers/intel-footer.html#installing-your-image-on-the-internal-emmc >INHERIT += "rm_work" >IMAGE_INSTALL_append = " linux-firmware-iwlwifi-7265d" >IMAGE_INSTALL_append = " parted e2fsprogs dosfstools" >IMAGE_INSTALL_append = " linux-firmware-i915 linux-firmware-ibt linux-firmware-iwlwifi-8000c" But, I think just doing dd may work, despite you must be careful on total / partition sizes? USB stick -> eMMC (prepared offline)SD -> eMMC BTW, in above, I am not sure linux-firmware-xxx part above is necessary for this beside parted. etc. ________________________________________ From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Martin Kelly Sent: Friday, February 23, 2018 11:03 AM To: Duraisamy, Srinath; automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] Electric Eel v5.0.1 build parted command not found This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing Feedback The guide here should tell you how: http://docs.automotivelinux.org/docs/getting_started/en/dev/reference/machines/intel.html Note this section: http://docs.automotivelinux.org/docs/getting_started/en/dev/reference/machines/intel.html#create-a-bootable-media You need to insert the SD card into your desktop machine and then figure out which device file it is. On 02/22/2018 05:41 PM, Duraisamy, Srinath wrote: Hi Thanks for the mail. Any idea how can I flash the AGL image booted from USB onto mmcblk ?? Thanks Srinath From: Martin Kelly [mailto:mkelly at xevo.com] Sent: Thursday, February 22, 2018 4:05 PM To: Duraisamy, Srinath ; automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] Electric Eel v5.0.1 build parted command not found Hi, I believe mkefi-agl.sh should be run from your desktop, not from the target device. If you do that, you can just apt/yum install parted and it should work. parted is not typically installed on a target image, though you could install it if you wanted to. On 02/22/2018 03:28 PM, Duraisamy, Srinath wrote: Hi all, I build Eel v5.0.1 for intel platforms and able to flash it on a USB disk. But when I try flash it on mmcblk in target platform. I am getting the below error mkefi-agl.sh parted: command not found Failed to create MSDOS partition table I tried the latest mkefi-agl.sh script and the script in Eel v5.0.1 but I get the same error in both cases. Do I have to try with a different script ? Thanks in advance. Srinath _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From jung at drimaes.com Fri Feb 23 05:51:53 2018 From: jung at drimaes.com (=?UTF-8?B?7KCV7JiB66y4?=) Date: Fri, 23 Feb 2018 14:51:53 +0900 Subject: [agl-discussions] How to see Applications Debug Message ? In-Reply-To: <20180222105158.14a5d76a@d-jobol.iot.bzh> References: <20180222093611.187b4fa7@d-jobol.iot.bzh> <20180222105158.14a5d76a@d-jobol.iot.bzh> Message-ID: Thanks a lot about your reply. I follow up way you mentioned, but sadly nothing to work. ( I did that create hmi-debug file & commnet out "USE_HMI_DEBUG=5" line) I have one more question. How can I see debug message? Do I need any command for? or Is it support after AGL 5.0.1 version? I am so sorry : ( I have so many question about that ... Thanks & Regards, Josh. 2018-02-22 18:51 GMT+09:00 Jos? Bollo : > On Thu, 22 Feb 2018 17:41:28 +0900 > ??? wrote: > > > Thank you for your fast reply. > > > > I checked that dir you mentioned, but there are only 2 things > > "qt-for-ivi-shell" and "qtquickcontrols2-style". > > there aren't hmi-debug. > > > > Should I need to any setting? when yocto build? or another settings? > > I think that it depends on the version of AGL you are using (I'm using > master/rocko). > > So create that file: > > cat > /etc/afm/unit.env.d/hmi-debug << EOC > #You can select log level of HMI framework > #1 ERROR > #2 WARNING > #3 NOTICE > #4 INFO > #5 DEBUG > #If you want to output debug log about hmi-framework, please uncomment > the following. > #USE_HMI_DEBUG=5 > EOC > > See > https://git.automotivelinux.org/AGL/meta-agl-devel/tree/ > meta-hmi-framework/recipes-demo-hmi/hmi-debug > > Best Regards > Jos? Bollo > > > > > > > > > Thanks & Regards, > > Josh. > > > > > > 2018-02-22 17:36 GMT+09:00 Jos? Bollo : > > > > > On Thu, 22 Feb 2018 17:24:18 +0900 > > > ??? wrote: > > > > > > > Hi everyone, > > > > > > Hi josh, > > > > > > Look at the file /etc/afm/unit.env.d/hmi-debug > > > > > > Message are reported in journal. > > > > > > Best regards > > > Jos? Bollo > > > > > > > I am working with AGL 5.0 on QEMU and testing > > > > Applications(ex.Homescreen ... ) > > > > My question is that how can I see debug message? > > > > > > > > > > > > In Homescreen source code(main.c,Homescreen project), it uses > > > > debug message like qDebg(...) or HMI_DEBUG(...). > > > > But when I execute Homescreen on AGL, I couldn't see any message. > > > > > > > > > > > > Do you have any way to see debug message? > > > > > > > > > > > > > > > > Please help me in this regard. > > > > > > > > > > > > Thanks & Regards, > > > > Josh. > > > > > > > > > > > > > > > > > > > > automotive-discussions at lists.linuxfoundation.org > > > > > > _______________________________________________ > > > automotive-discussions mailing list > > > automotive-discussions at lists.linuxfoundation.org > > > https://lists.linuxfoundation.org/mailman/listinfo/ > automotive-discussions > > > > > > > > > > > -- *Jung Young Moon DrimAES Inc.* *Address* ?? ??? ???? 273 ???????2? 803? ????? *Mobile* 010-4907-2117 *Mail* jung at drimaes.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From knimitz at witz-inc.co.jp Fri Feb 23 06:02:12 2018 From: knimitz at witz-inc.co.jp (Kazumasa Mitsunari) Date: Fri, 23 Feb 2018 15:02:12 +0900 Subject: [agl-discussions] How to see Applications Debug Message ? In-Reply-To: References: <20180222093611.187b4fa7@d-jobol.iot.bzh> <20180222105158.14a5d76a@d-jobol.iot.bzh> Message-ID: <206896fa-6103-73a1-2c73-ad024027c2f3@witz-inc.co.jp> Hi > or Is it support after AGL 5.0.1 version? Maybe it's not in eel5.0.1. > I have one more question. > How can I see debug message? Do I need any command for? Currently, the application or service launched by launcher, output logs to journal log. After you add the file, you can see in journal log. # journalctl or # journalctl -f Please check:) Best Regards ?Kazumasa Mitsunari On 2018?02?23? 14:51, ??? wrote: > Thanks a lot about your reply. > > I follow up way you mentioned, but sadly nothing to work. > ( I did that create hmi-debug file & commnet out "USE_HMI_DEBUG=5" line) > > I have one more question. > How can I see debug message? Do I need any command for? > or Is it support after AGL 5.0.1 version? > > I am so sorry : ( > I have so many question about that ... > > Thanks & Regards, > Josh. > > > > 2018-02-22 18:51 GMT+09:00 Jos? Bollo >: > > On Thu, 22 Feb 2018 17:41:28 +0900 > ??? > wrote: > > > Thank you for your fast reply. > > > > I checked that dir you mentioned, but there are only 2 things > > "qt-for-ivi-shell" and "qtquickcontrols2-style". > > there aren't hmi-debug. > > > > Should I need to any setting? when yocto build? or another settings? > > I think that it depends on the version of AGL you are using (I'm using > master/rocko). > > So create that file: > > cat > /etc/afm/unit.env.d/hmi-debug << EOC > #You can select log level of HMI framework > #1 ERROR > #2 WARNING > #3 NOTICE > #4 INFO > #5 DEBUG > #If you want to output debug log about hmi-framework, please uncomment > the following. > #USE_HMI_DEBUG=5 > EOC > > See > https://git.automotivelinux.org/AGL/meta-agl-devel/tree/meta-hmi-framework/recipes-demo-hmi/hmi-debug > > > Best Regards > Jos? Bollo > > > > > > > > > Thanks & Regards, > > Josh. > > > > > > 2018-02-22 17:36 GMT+09:00 Jos? Bollo : > > > > > On Thu, 22 Feb 2018 17:24:18 +0900 > > > ??? > wrote: > > > > > > > Hi everyone, > > > > > > Hi josh, > > > > > > Look at the file /etc/afm/unit.env.d/hmi-debug > > > > > > Message are reported in journal. > > > > > > Best regards > > > Jos? Bollo > > > > > > > I am working? with AGL 5.0 on QEMU and testing > > > > Applications(ex.Homescreen ... ) > > > > My question is that how can I see debug message? > > > > > > > > > > > > In Homescreen source code(main.c,Homescreen project), it uses > > > > debug message like qDebg(...) or HMI_DEBUG(...). > > > > But when I execute Homescreen on AGL, I couldn't see any > message. > > > > > > > > > > > > Do you have any way to see debug message? > > > > > > > > > > > > > > > > Please help me in this regard. > > > > > > > > > > > > Thanks & Regards, > > > > Josh. > > > > > > > > > > > > > > > > > > > > automotive-discussions at lists.linuxfoundation.org > > > > > > > _______________________________________________ > > > automotive-discussions mailing list > > > automotive-discussions at lists.linuxfoundation.org > > > > > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > > > > > > > > > > > > > > > -- > *Jung Young Moon DrimAES Inc.* > * > **Address* ????????????273 ???????2? 803? ????? > *Mobile*?010-4907-2117 > *Mail* jung at drimaes.com > > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions -- ******************************* WITZ Corporation ??????? ??????? Base Technology Development Dept. ?Advanced Basic Technology Sect. ?Kazumasa Mitsunari Mail:knimitz at witz-inc.co.jp ******************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: From jung at drimaes.com Fri Feb 23 07:05:17 2018 From: jung at drimaes.com (=?UTF-8?B?7KCV7JiB66y4?=) Date: Fri, 23 Feb 2018 16:05:17 +0900 Subject: [agl-discussions] How to see Applications Debug Message ? In-Reply-To: <206896fa-6103-73a1-2c73-ad024027c2f3@witz-inc.co.jp> References: <20180222093611.187b4fa7@d-jobol.iot.bzh> <20180222105158.14a5d76a@d-jobol.iot.bzh> <206896fa-6103-73a1-2c73-ad024027c2f3@witz-inc.co.jp> Message-ID: Thanks a lot!!! Work now, I can check debug messsage using "journalctl -f" command. really thanks about reply : ) Thanks & Regards, Josh. 2018-02-23 15:02 GMT+09:00 Kazumasa Mitsunari : > Hi > > or Is it support after AGL 5.0.1 version? > > Maybe it's not in eel5.0.1. > > I have one more question. > How can I see debug message? Do I need any command for? > > Currently, the application or service launched by launcher, output logs to > journal log. > After you add the file, you can see in journal log. > > # journalctl > or > # journalctl -f > > Please check:) > > Best Regards > Kazumasa Mitsunari > > > > On 2018?02?23? 14:51, ??? wrote: > > Thanks a lot about your reply. > > I follow up way you mentioned, but sadly nothing to work. > ( I did that create hmi-debug file & commnet out "USE_HMI_DEBUG=5" line) > > I have one more question. > How can I see debug message? Do I need any command for? > or Is it support after AGL 5.0.1 version? > > I am so sorry : ( > I have so many question about that ... > > Thanks & Regards, > Josh. > > > > 2018-02-22 18:51 GMT+09:00 Jos? Bollo : > >> On Thu, 22 Feb 2018 17:41:28 +0900 >> ??? wrote: >> >> > Thank you for your fast reply. >> > >> > I checked that dir you mentioned, but there are only 2 things >> > "qt-for-ivi-shell" and "qtquickcontrols2-style". >> > there aren't hmi-debug. >> > >> > Should I need to any setting? when yocto build? or another settings? >> >> I think that it depends on the version of AGL you are using (I'm using >> master/rocko). >> >> So create that file: >> >> cat > /etc/afm/unit.env.d/hmi-debug << EOC >> #You can select log level of HMI framework >> #1 ERROR >> #2 WARNING >> #3 NOTICE >> #4 INFO >> #5 DEBUG >> #If you want to output debug log about hmi-framework, please uncomment >> the following. >> #USE_HMI_DEBUG=5 >> EOC >> >> See >> https://git.automotivelinux.org/AGL/meta-agl-devel/tree/meta >> -hmi-framework/recipes-demo-hmi/hmi-debug >> >> Best Regards >> Jos? Bollo >> >> > >> > >> > >> > Thanks & Regards, >> > Josh. >> > >> > >> > 2018-02-22 17:36 GMT+09:00 Jos? Bollo >> : >> > >> > > On Thu, 22 Feb 2018 17:24:18 +0900 >> > > ??? wrote: >> > > >> > > > Hi everyone, >> > > >> > > Hi josh, >> > > >> > > Look at the file /etc/afm/unit.env.d/hmi-debug >> > > >> > > Message are reported in journal. >> > > >> > > Best regards >> > > Jos? Bollo >> > > >> > > > I am working with AGL 5.0 on QEMU and testing >> > > > Applications(ex.Homescreen ... ) >> > > > My question is that how can I see debug message? >> > > > >> > > > >> > > > In Homescreen source code(main.c,Homescreen project), it uses >> > > > debug message like qDebg(...) or HMI_DEBUG(...). >> > > > But when I execute Homescreen on AGL, I couldn't see any message. >> > > > >> > > > >> > > > Do you have any way to see debug message? >> > > > >> > > > >> > > > >> > > > Please help me in this regard. >> > > > >> > > > >> > > > Thanks & Regards, >> > > > Josh. >> > > > >> > > > >> > > > >> > > > >> > > > automotive-discussions at lists.linuxfoundation.org >> > > >> > > _______________________________________________ >> > > automotive-discussions mailing list >> > > automotive-discussions at lists.linuxfoundation.org >> > > https://lists.linuxfoundation.org/mailman/listinfo/automotiv >> e-discussions >> > > >> > >> > >> > >> >> > > > -- > *Jung Young Moon DrimAES Inc.* > > *Address* ?? ??? ???? 273 ???????2? 803? ????? > *Mobile* 010-4907-2117 > *Mail* jung at drimaes.com > > > _______________________________________________ > automotive-discussions mailing listautomotive-discussions at lists.linuxfoundation.orghttps://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > > > -- > ******************************* > WITZ Corporation > ??????? ??????? > Base Technology Development Dept. > ?Advanced Basic Technology Sect. > ?Kazumasa Mitsunari > Mail:knimitz at witz-inc.co.jp > ******************************* > > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > > -- *Jung Young Moon DrimAES Inc.* *Address* ?? ??? ???? 273 ???????2? 803? ????? *Mobile* 010-4907-2117 *Mail* jung at drimaes.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From tmatsuzawa at xevo.com Fri Feb 23 08:07:38 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Fri, 23 Feb 2018 08:07:38 +0000 Subject: [agl-discussions] Enter Password prompt on UP2 board? Message-ID: Hello. I am booting EE5.0.1 on UP2 board, and seeing (UEFI) "Enter Password" prompt (blue text popup on black background) at the boot and can not go further (I can press Enter without password, enter BIOS setting, but I do not seem to be able to exit from BIOS setting. I think this may be related to me changing configuration - connecting/disconnecting displayes, connecting/disconnecting serial port plug. One day this started happening. It once solved (no "Enter Password"), but now it is happening again, not sure what caused this to be happening again. Sorry this may be an issue with this board before booting the Linux OS. But is there known trick to recover this? From tmatsuzawa at xevo.com Fri Feb 23 08:44:04 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Fri, 23 Feb 2018 08:44:04 +0000 Subject: [agl-discussions] Enter Password prompt on UP2 board? In-Reply-To: References: Message-ID: By the way, "admin password" found in below did not work. >https://wiki.up-community.org/Bios_Update I tried to remove RTC battery cable (and USB, etc.), want for seconds, but I am still seeing this.. ________________________________________ From: Takashi Matsuzawa Sent: Friday, February 23, 2018 5:07 PM To: automotive-discussions at lists.linuxfoundation.org Subject: Enter Password prompt on UP2 board? Hello. I am booting EE5.0.1 on UP2 board, and seeing (UEFI) "Enter Password" prompt (blue text popup on black background) at the boot and can not go further (I can press Enter without password, enter BIOS setting, but I do not seem to be able to exit from BIOS setting. I think this may be related to me changing configuration - connecting/disconnecting displayes, connecting/disconnecting serial port plug. One day this started happening. It once solved (no "Enter Password"), but now it is happening again, not sure what caused this to be happening again. Sorry this may be an issue with this board before booting the Linux OS. But is there known trick to recover this? From ronan.lemartret at iot.bzh Fri Feb 23 10:25:21 2018 From: ronan.lemartret at iot.bzh (Ronan Le Martret [ IoT.bzh ]) Date: Fri, 23 Feb 2018 11:25:21 +0100 Subject: [agl-discussions] Running AGL on Windows laptop / broken download links In-Reply-To: References: Message-ID: Hi Christian, the links is now fix. Effectually, currently the AGL virtual image have an unstable UI. If you want to configure virtualbox, you can find more information on qemu image here: http://docs.automotivelinux.org/docs/getting_started/en/dev/reference/machines/qemu.html Regards, Ronan Le Martret [IoT.bzh] 2018-02-20 9:55 GMT+01:00 Benien, Christian : > Hi, > > > > I?m trying to get started with application development for AGL. The > documentation for building the apps is pretty good and easy to follow. > > > > I?m currently stuck when trying to run my app on AGL. I don?t have a > dedicated target board, all I have is my Windows laptop. I?ve seen some > guides for running the QEMU image in VirtualBox, but all download links to > QEMU images are broken, e.g. on this page here: > > > > https://wiki.automotivelinux.org/agl-distro/release-notes#eel_501 > > > > Browsing the download server, I?ve possibly found the correct link: > > https://download.automotivelinux.org/AGL/release/eel/5.0.1/qemux86-64/ > deploy/images/qemux86-64/agl-demo-platform-crosssdk-qemux86-64.vmdk.xz > > > > I have some mixed success running this in VirtualBox. Sometimes I get a > broken UI, sometimes the screen stays black. > > > > Two questions: > > - Is it possible at all to run AGL on a Windows laptop? Should the > above image work? Anything special to configure in VirtualBox? > - Can somebody please fix the links? > > > > Thanks and best regards > > Christian > > > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dominig.arfoll at fridu.net Fri Feb 23 10:26:54 2018 From: dominig.arfoll at fridu.net (Dominig Ar Foll) Date: Fri, 23 Feb 2018 11:26:54 +0100 Subject: [agl-discussions] Electric Eel v5.0.1 build parted command not found In-Reply-To: References: <48058762-376e-99c7-0abd-fb0a90522380@xevo.com> Message-ID: Nice to see good support coming while I travel :-) Thanks to all. Srinrath, you should now have all the required pointers to succeed. The trick is to add the required tool to your image what requires to build your own image as the image built by AGL project team do not include them. If getting the extra tools in default images is a real need for you, please raise a bug in Jira, and affect it to me (if you miss that last detail, it will still come to me but a bit later :-) Regards. Dominig 2018-02-23 3:18 GMT+01:00 Takashi Matsuzawa : > In case you are trying below (installing on eMMC), rebuilding image (so that parted, etc. are there) may be necessary. > > http://docs.automotivelinux.org/docs/getting_started/en/dev/reference/footers/intel-footer.html#installing-your-image-on-the-internal-emmc > >>INHERIT += "rm_work" >>IMAGE_INSTALL_append = " linux-firmware-iwlwifi-7265d" >>IMAGE_INSTALL_append = " parted e2fsprogs dosfstools" >>IMAGE_INSTALL_append = " linux-firmware-i915 linux-firmware-ibt linux-firmware-iwlwifi-8000c" > > But, I think just doing dd may work, despite you must be careful on total / partition sizes? > > USB stick -> eMMC > (prepared offline)SD -> eMMC > > BTW, in above, I am not sure linux-firmware-xxx part above is necessary for this beside parted. etc. > > ________________________________________ > From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Martin Kelly > Sent: Friday, February 23, 2018 11:03 AM > To: Duraisamy, Srinath; automotive-discussions at lists.linuxfoundation.org > Subject: Re: [agl-discussions] Electric Eel v5.0.1 build parted command not found > > > This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing > Feedback > > The guide here should tell you how: > > http://docs.automotivelinux.org/docs/getting_started/en/dev/reference/machines/intel.html > > Note this section: > > http://docs.automotivelinux.org/docs/getting_started/en/dev/reference/machines/intel.html#create-a-bootable-media > > You need to insert the SD card into your desktop machine and then figure out which device file it is. > > On 02/22/2018 05:41 PM, Duraisamy, Srinath wrote: > Hi Thanks for the mail. > Any idea how can I flash the AGL image booted from USB onto mmcblk ?? > > Thanks > Srinath > > From: Martin Kelly [mailto:mkelly at xevo.com] > Sent: Thursday, February 22, 2018 4:05 PM > To: Duraisamy, Srinath ; automotive-discussions at lists.linuxfoundation.org > Subject: Re: [agl-discussions] Electric Eel v5.0.1 build parted command not found > > Hi, > > I believe mkefi-agl.sh should be run from your desktop, not from the target device. If you do that, you can just apt/yum install parted and it should work. parted is not typically installed on a target image, though you could install it if you wanted to. > On 02/22/2018 03:28 PM, Duraisamy, Srinath wrote: > Hi all, > > I build Eel v5.0.1 for intel platforms and able to flash it on a USB disk. > But when I try flash it on mmcblk in target platform. I am getting the below error > > mkefi-agl.sh parted: command not found > Failed to create MSDOS partition table > > I tried the latest mkefi-agl.sh script and the script in Eel v5.0.1 but I get the same error in both cases. > Do I have to try with a different script ? > > Thanks in advance. > Srinath > > > > > > > _______________________________________________ > > automotive-discussions mailing list > > automotive-discussions at lists.linuxfoundation.org > > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre From dominig.arfoll at fridu.net Fri Feb 23 10:33:13 2018 From: dominig.arfoll at fridu.net (Dominig Ar Foll) Date: Fri, 23 Feb 2018 11:33:13 +0100 Subject: [agl-discussions] Enter Password prompt on UP2 board? In-Reply-To: References: Message-ID: Hello, that link gives the correct passwd (upassw0rd with a ZERO not a OOH) but it's a bit of pain to use. It assume a QWERTY keyboard layout whatever is your real keyboard. What happen is that you can get extra characters in the IO buffer from when you ask to get to the BIOS page. My advise is to remove the passwd in the BIOS, once you suceed to access the page. Dominig 2018-02-23 9:44 GMT+01:00 Takashi Matsuzawa : > By the way, "admin password" found in below did not work. > >>https://wiki.up-community.org/Bios_Update > > I tried to remove RTC battery cable (and USB, etc.), want for seconds, but I am still seeing this.. > > ________________________________________ > From: Takashi Matsuzawa > Sent: Friday, February 23, 2018 5:07 PM > To: automotive-discussions at lists.linuxfoundation.org > Subject: Enter Password prompt on UP2 board? > > Hello. > > I am booting EE5.0.1 on UP2 board, and seeing (UEFI) "Enter Password" prompt (blue text popup on black background) at the boot and can not go further (I can press Enter without password, enter BIOS setting, but I do not seem to be able to exit from BIOS setting. > > I think this may be related to me changing configuration - connecting/disconnecting displayes, connecting/disconnecting serial port plug. > One day this started happening. > It once solved (no "Enter Password"), but now it is happening again, not sure what caused this to be happening again. > > Sorry this may be an issue with this board before booting the Linux OS. > But is there known trick to recover this? > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre From tmatsuzawa at xevo.com Fri Feb 23 11:31:46 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Fri, 23 Feb 2018 11:31:46 +0000 Subject: [agl-discussions] Electric Eel v5.0.1 build parted command not found In-Reply-To: References: <48058762-376e-99c7-0abd-fb0a90522380@xevo.com> , Message-ID: Thank you for your suggestion. I could access CRB setup page and could see what is there. As for my issue below, the issue was caused by how I booted the system. I booted from USB stick, but it was connected to the board using USB hub - it seems you need to connect directly to the board, or the board does not recognize the storage at boot? - so it always prompt me to the BIOS setting. By attaching the USB stick to the board, I no longer enter BIOS setting at boot. By the way, I could confirm the system recognizes two displays (DP and HDMI) attached to the board. I could show app surfaces on either of the displays. One thing noticed is that AGL homescreen is initially displayed on DP port display in my dual-display configuration. (If I connect only HDMI display, the homescreen is shown there, but if I have two displays, DP display is always chosen as screen 0). ________________________________________ From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Dominig Ar Foll Sent: Friday, February 23, 2018 7:26:54 PM To: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] Electric Eel v5.0.1 build parted command not found Nice to see good support coming while I travel :-) Thanks to all. Srinrath, you should now have all the required pointers to succeed. The trick is to add the required tool to your image what requires to build your own image as the image built by AGL project team do not include them. If getting the extra tools in default images is a real need for you, please raise a bug in Jira, and affect it to me (if you miss that last detail, it will still come to me but a bit later :-) Regards. Dominig 2018-02-23 3:18 GMT+01:00 Takashi Matsuzawa : > In case you are trying below (installing on eMMC), rebuilding image (so that parted, etc. are there) may be necessary. > > http://docs.automotivelinux.org/docs/getting_started/en/dev/reference/footers/intel-footer.html#installing-your-image-on-the-internal-emmc > >>INHERIT += "rm_work" >>IMAGE_INSTALL_append = " linux-firmware-iwlwifi-7265d" >>IMAGE_INSTALL_append = " parted e2fsprogs dosfstools" >>IMAGE_INSTALL_append = " linux-firmware-i915 linux-firmware-ibt linux-firmware-iwlwifi-8000c" > > But, I think just doing dd may work, despite you must be careful on total / partition sizes? > > USB stick -> eMMC > (prepared offline)SD -> eMMC > > BTW, in above, I am not sure linux-firmware-xxx part above is necessary for this beside parted. etc. > > ________________________________________ > From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of Martin Kelly > Sent: Friday, February 23, 2018 11:03 AM > To: Duraisamy, Srinath; automotive-discussions at lists.linuxfoundation.org > Subject: Re: [agl-discussions] Electric Eel v5.0.1 build parted command not found > > > This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing > Feedback > > The guide here should tell you how: > > http://docs.automotivelinux.org/docs/getting_started/en/dev/reference/machines/intel.html > > Note this section: > > http://docs.automotivelinux.org/docs/getting_started/en/dev/reference/machines/intel.html#create-a-bootable-media > > You need to insert the SD card into your desktop machine and then figure out which device file it is. > > On 02/22/2018 05:41 PM, Duraisamy, Srinath wrote: > Hi Thanks for the mail. > Any idea how can I flash the AGL image booted from USB onto mmcblk ?? > > Thanks > Srinath > > From: Martin Kelly [mailto:mkelly at xevo.com] > Sent: Thursday, February 22, 2018 4:05 PM > To: Duraisamy, Srinath ; automotive-discussions at lists.linuxfoundation.org > Subject: Re: [agl-discussions] Electric Eel v5.0.1 build parted command not found > > Hi, > > I believe mkefi-agl.sh should be run from your desktop, not from the target device. If you do that, you can just apt/yum install parted and it should work. parted is not typically installed on a target image, though you could install it if you wanted to. > On 02/22/2018 03:28 PM, Duraisamy, Srinath wrote: > Hi all, > > I build Eel v5.0.1 for intel platforms and able to flash it on a USB disk. > But when I try flash it on mmcblk in target platform. I am getting the below error > > mkefi-agl.sh parted: command not found > Failed to create MSDOS partition table > > I tried the latest mkefi-agl.sh script and the script in Eel v5.0.1 but I get the same error in both cases. > Do I have to try with a different script ? > > Thanks in advance. > Srinath > > > > > > > _______________________________________________ > > automotive-discussions mailing list > > automotive-discussions at lists.linuxfoundation.org > > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From jung at drimaes.com Mon Feb 26 11:30:08 2018 From: jung at drimaes.com (=?UTF-8?B?7KCV7JiB66y4?=) Date: Mon, 26 Feb 2018 20:30:08 +0900 Subject: [agl-discussions] generate-binding-glue.py Message-ID: Hi everyone, I am studying AGL Windowmanager.(AGL 5.0.0 on QEMU) So, I follow up http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/hmi-framework/3_2-WindowManager-Guide.html When I read "Binding code generation" part In upper website, I saw "generate-binding-glue.py" In order to simplify development. I download windowmager sourcefile https://download.automotivelinux.org/AGL/release/eel/5.0.0/qemux86-64/deploy/sources/x86_64-agl-linux/agl-service-windowmanager-2017-1.0+gitAUTOINC+12c8934465-r0/ . But there were not python file. Where Can I find that file? Please help me in this regard. Thanks & Regards, Josh. -- *Jung Young Moon DrimAES Inc.* *Address* *#803, Ace Twin Tower 2-cha, 273, Digital-ro, Guro-gu, Seoul, Korea * *Mobile* *+82 (0)10 - 4907 - 2117* *Mail* jung at drimaes.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From knimitz at witz-inc.co.jp Mon Feb 26 11:35:41 2018 From: knimitz at witz-inc.co.jp (Kazumasa Mitsunari) Date: Mon, 26 Feb 2018 20:35:41 +0900 Subject: [agl-discussions] generate-binding-glue.py In-Reply-To: References: Message-ID: <7a3f44a6-356f-1d62-2c26-2e7b1344c7e5@witz-inc.co.jp> Hi We are sorry, I forgot update the document. And thanks for pointing it out. The file you pointed is already deleted. So I'm going to update the document as soon as possible. Would you please wait a moment? Best Regards ?Kazumasa Mitsunari On 2018?02?26? 20:30, ??? wrote: > Hi everyone, > > > I am studying AGL Windowmanager.(AGL 5.0.0 on QEMU) > > So, I follow up > http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/hmi-framework/3_2-WindowManager-Guide.html > > When I read "Binding code generation" part In upper website, I saw > |"generate-binding-glue.py" In order to simplify development. > | > |I download windowmager sourcefile > https://download.automotivelinux.org/AGL/release/eel/5.0.0/qemux86-64/deploy/sources/x86_64-agl-linux/agl-service-windowmanager-2017-1.0+gitAUTOINC+12c8934465-r0/. > | > |But there were not python file. > > | > |Where Can I find that file? > | > > Please help me in this regard. > > > > Thanks & Regards, > Josh. > > > -- > *Jung Young Moon DrimAES Inc.* > * > **Address* *#803, Ace Twin Tower 2-cha, 273, Digital-ro, Guro-gu, > Seoul, Korea > * > *Mobile* *+82 (0)10 - 4907 - 2117* > *Mail* jung at drimaes.com > > > > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions -- ******************************* WITZ Corporation ??????? ??????? Base Technology Development Dept. ?Advanced Basic Technology Sect. ?Kazumasa Mitsunari Mail:knimitz at witz-inc.co.jp ******************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: From jung at drimaes.com Mon Feb 26 11:49:52 2018 From: jung at drimaes.com (=?UTF-8?B?7KCV7JiB66y4?=) Date: Mon, 26 Feb 2018 20:49:52 +0900 Subject: [agl-discussions] generate-binding-glue.py In-Reply-To: <7a3f44a6-356f-1d62-2c26-2e7b1344c7e5@witz-inc.co.jp> References: <7a3f44a6-356f-1d62-2c26-2e7b1344c7e5@witz-inc.co.jp> Message-ID: Thank you for your fast reply. you mean that "generate-binding-glue.py" file does not useing anymore? Is it displaced someting new? or just not used ? Thanks & Regards, Josh. 2018-02-26 20:35 GMT+09:00 Kazumasa Mitsunari : > Hi > > We are sorry, > I forgot update the document. > And thanks for pointing it out. > > The file you pointed is already deleted. > > So I'm going to update the document as soon as possible. > > Would you please wait a moment? > > Best Regards > Kazumasa Mitsunari > > > > On 2018?02?26? 20:30, ??? wrote: > > Hi everyone, > > > I am studying AGL Windowmanager.(AGL 5.0.0 on QEMU) > > So, I follow up http://docs.automotivelinux.org/docs/apis_services/en/dev/ > reference/hmi-framework/3_2-WindowManager-Guide.html > > When I read "Binding code generation" part In upper website, I saw "generate-binding-glue.py" > In order to simplify development. > I download windowmager sourcefile https://download. > automotivelinux.org/AGL/release/eel/5.0.0/qemux86-64/ > deploy/sources/x86_64-agl-linux/agl-service-windowmanager-2017-1.0+ > gitAUTOINC+12c8934465-r0/. > But there were not python file. > > Where Can I find that file? > > Please help me in this regard. > > > > Thanks & Regards, > Josh. > > > -- > *Jung Young Moon DrimAES Inc.* > > *Address* *#803, Ace Twin Tower 2-cha, 273, Digital-ro, Guro-gu, Seoul, > Korea > * > *Mobile* *+82 (0)10 - 4907 - 2117* > *Mail* jung at drimaes.com > > > > > _______________________________________________ > automotive-discussions mailing listautomotive-discussions at lists.linuxfoundation.orghttps://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > > > -- > ******************************* > WITZ Corporation > ??????? ??????? > Base Technology Development Dept. > ?Advanced Basic Technology Sect. > ?Kazumasa Mitsunari > Mail:knimitz at witz-inc.co.jp > ******************************* > > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > > -- *Jung Young Moon DrimAES Inc.* *Address* *#803, Ace Twin Tower 2-cha, 273, Digital-ro, Guro-gu, Seoul, Korea * *Mobile* *+82 (0)10 - 4907 - 2117* *Mail* jung at drimaes.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From knimitz at witz-inc.co.jp Mon Feb 26 11:58:00 2018 From: knimitz at witz-inc.co.jp (Kazumasa Mitsunari) Date: Mon, 26 Feb 2018 20:58:00 +0900 Subject: [agl-discussions] generate-binding-glue.py In-Reply-To: References: <7a3f44a6-356f-1d62-2c26-2e7b1344c7e5@witz-inc.co.jp> Message-ID: <906ace43-a814-1647-51c6-b0d31cee0d14@witz-inc.co.jp> Hi > you mean that "|generate-binding-glue.py|" file does not useing anymore? Yes. > Is it displaced someting new? or just not used ? Both of them. Originally it is for simplicity. But in order to improve flexibility, it was better to replace with normal source code. For the detail, please see the commit a5872e5c14a97d738fd9a0daaf0764b655baeebd Best Regards ?Kazumasa Mitsunari On 2018?02?26? 20:49, ??? wrote: > Thank you for your fast reply. > > > you mean that "|generate-binding-glue.py|" file does not useing anymore? > Is it displaced someting new? or just not used ? > > > Thanks & Regards, > Josh. > > > > 2018-02-26 20:35 GMT+09:00 Kazumasa Mitsunari >: > > Hi > > We are sorry, > I forgot update the document. > And thanks for pointing it out. > > The file you pointed is already deleted. > > So I'm going to update the document as soon as possible. > > Would you please wait a moment? > > Best Regards > ?Kazumasa Mitsunari > > > > On 2018?02?26? 20:30, ??? wrote: >> Hi everyone, >> >> >> I am studying AGL Windowmanager.(AGL 5.0.0 on QEMU) >> >> So, I follow up >> http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/hmi-framework/3_2-WindowManager-Guide.html >> >> >> When I read "Binding code generation" part In upper website, I >> saw |"generate-binding-glue.py" In order to simplify development. >> | >> |I download windowmager sourcefile >> https://download.automotivelinux.org/AGL/release/eel/5.0.0/qemux86-64/deploy/sources/x86_64-agl-linux/agl-service-windowmanager-2017-1.0+gitAUTOINC+12c8934465-r0/ >> . >> | >> |But there were not python file. >> >> | >> |Where Can I find that file? >> | >> >> Please help me in this regard. >> >> >> >> Thanks & Regards, >> Josh. >> >> >> -- >> *Jung Young Moon DrimAES Inc.* >> * >> **Address* *#803, Ace Twin Tower 2-cha, 273, Digital-ro, Guro-gu, >> Seoul, Korea >> * >> *Mobile* *+82 (0)10 - 4907 - 2117* >> *Mail* jung at drimaes.com >> >> >> >> >> _______________________________________________ >> automotive-discussions mailing list >> automotive-discussions at lists.linuxfoundation.org >> >> https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions >> > > -- > ******************************* > WITZ Corporation > ??????? ??????? > Base Technology Development Dept. > ?Advanced Basic Technology Sect. > ?Kazumasa Mitsunari > Mail:knimitz at witz-inc.co.jp > ******************************* > > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > > > > > > -- > *Jung Young Moon DrimAES Inc.* > * > **Address* *#803, Ace Twin Tower 2-cha, 273, Digital-ro, Guro-gu, > Seoul, Korea > * > *Mobile* *+82 (0)10 - 4907 - 2117* > *Mail* jung at drimaes.com > > -- ******************************* WITZ Corporation ??????? ??????? Base Technology Development Dept. ?Advanced Basic Technology Sect. ?Kazumasa Mitsunari Mail:knimitz at witz-inc.co.jp ******************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: From jung at drimaes.com Mon Feb 26 12:00:06 2018 From: jung at drimaes.com (=?UTF-8?B?7KCV7JiB66y4?=) Date: Mon, 26 Feb 2018 21:00:06 +0900 Subject: [agl-discussions] generate-binding-glue.py In-Reply-To: <906ace43-a814-1647-51c6-b0d31cee0d14@witz-inc.co.jp> References: <7a3f44a6-356f-1d62-2c26-2e7b1344c7e5@witz-inc.co.jp> <906ace43-a814-1647-51c6-b0d31cee0d14@witz-inc.co.jp> Message-ID: Oh, I understood about that! Thank you for your reply and check commit point! Thanks & Regards, Josh. 2018-02-26 20:58 GMT+09:00 Kazumasa Mitsunari : > Hi > > you mean that "generate-binding-glue.py" file does not useing anymore? > > Yes. > > Is it displaced someting new? or just not used ? > > Both of them. > Originally it is for simplicity. > But in order to improve flexibility, it was better to replace with normal > source code. > For the detail, please see the commit a5872e5c14a97d738fd9a0daaf0764 > b655baeebd > > Best Regards > Kazumasa Mitsunari > > > > On 2018?02?26? 20:49, ??? wrote: > > Thank you for your fast reply. > > > you mean that "generate-binding-glue.py" file does not useing anymore? > Is it displaced someting new? or just not used ? > > > Thanks & Regards, > Josh. > > > > 2018-02-26 20:35 GMT+09:00 Kazumasa Mitsunari : > >> Hi >> >> We are sorry, >> I forgot update the document. >> And thanks for pointing it out. >> >> The file you pointed is already deleted. >> >> So I'm going to update the document as soon as possible. >> >> Would you please wait a moment? >> >> Best Regards >> Kazumasa Mitsunari >> >> >> >> On 2018?02?26? 20:30, ??? wrote: >> >> Hi everyone, >> >> >> I am studying AGL Windowmanager.(AGL 5.0.0 on QEMU) >> >> So, I follow up http://docs.automotivelinux.or >> g/docs/apis_services/en/dev/reference/hmi-framework/3_2-Wind >> owManager-Guide.html >> >> When I read "Binding code generation" part In upper website, I saw "generate-binding-glue.py" >> In order to simplify development. >> I download windowmager sourcefile https://download.automotivelin >> ux.org/AGL/release/eel/5.0.0/qemux86-64/deploy/sources/x86_ >> 64-agl-linux/agl-service-windowmanager-2017-1.0+gitAUTOINC+12c8934465-r0/ >> . >> But there were not python file. >> >> Where Can I find that file? >> >> Please help me in this regard. >> >> >> >> Thanks & Regards, >> Josh. >> >> >> -- >> *Jung Young Moon DrimAES Inc.* >> >> *Address* *#803, Ace Twin Tower 2-cha, 273, Digital-ro, Guro-gu, Seoul, >> Korea >> * >> *Mobile* *+82 (0)10 - 4907 - 2117* >> *Mail* jung at drimaes.com >> >> >> >> >> _______________________________________________ >> automotive-discussions mailing listautomotive-discussions at lists.linuxfoundation.orghttps://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions >> >> >> -- >> ******************************* >> WITZ Corporation >> ??????? ??????? >> Base Technology Development Dept. >> ?Advanced Basic Technology Sect. >> ?Kazumasa Mitsunari >> Mail:knimitz at witz-inc.co.jp >> ******************************* >> >> >> _______________________________________________ >> automotive-discussions mailing list >> automotive-discussions at lists.linuxfoundation.org >> https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions >> >> > > > -- > *Jung Young Moon DrimAES Inc.* > > *Address* *#803, Ace Twin Tower 2-cha, 273, Digital-ro, Guro-gu, Seoul, > Korea > * > *Mobile* *+82 (0)10 - 4907 - 2117* > *Mail* jung at drimaes.com > > > > -- > ******************************* > WITZ Corporation > ??????? ??????? > Base Technology Development Dept. > ?Advanced Basic Technology Sect. > ?Kazumasa Mitsunari > Mail:knimitz at witz-inc.co.jp > ******************************* > > -- *Jung Young Moon DrimAES Inc.* *Address* *#803, Ace Twin Tower 2-cha, 273, Digital-ro, Guro-gu, Seoul, Korea * *Mobile* *+82 (0)10 - 4907 - 2117* *Mail* jung at drimaes.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jung at drimaes.com Tue Feb 27 03:06:39 2018 From: jung at drimaes.com (=?UTF-8?B?7KCV7JiB66y4?=) Date: Tue, 27 Feb 2018 12:06:39 +0900 Subject: [agl-discussions] how to build only agl-service-windowmanager-2017 using yocto? Message-ID: Hello AGL, I am studying AGL Windowmanager.(AGL 5.0.0 on QEMU) I just want to build only agl-service-windowmanager-2017 using yocto. So, I tried like bellow. step - 1) modifiy source code : AGL_QEMU_EE/build/tmp/work/corei7-64-agl-linux/agl-service-windowmanager-2017/1.0+gitAUTOINC+12c8934465-r0/git/src/main.cpp step - 2) use bitbake command : bitbake agl-service-windowmanager-2017 But, nothing to change. I wonder is it right directory for qemu windowmanager source at step - 1? And is it right command for build agl-service-windowmanager-2017 ? Please help me in this regard. Thanks & Regards, Josh. -- *Jung Young Moon DrimAES Inc.* *Address* *#803, Ace Twin Tower 2-cha, 273, Digital-ro, Guro-gu, Seoul, Korea * *Mobile* *+82 (0)10 - 4907 - 2117* *Mail* jung at drimaes.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From knimitz at witz-inc.co.jp Tue Feb 27 03:20:30 2018 From: knimitz at witz-inc.co.jp (Kazumasa Mitsunari) Date: Tue, 27 Feb 2018 12:20:30 +0900 Subject: [agl-discussions] how to build only agl-service-windowmanager-2017 using yocto? In-Reply-To: References: Message-ID: <9db60f5d-261d-a361-b675-d3ac13050edc@witz-inc.co.jp> Hi bitbake normally uses cache unless modifying recipe, so nothing happens however you edit source code in tmp directory. If you would like to re-compile compulsorily, please command the following bitbake -f -c compile bitbake ( if you need installing/packaging ... but for generating wgt file, this is necessary) or if you use SDK source cd mkdir build; cd build cmake .. make make package Please try:) Best Regards ?Kazumasa Mitsunari On 2018?02?27? 12:06, ??? wrote: > Hello AGL, > > > I am studying AGL Windowmanager.(AGL 5.0.0 on QEMU) > I just want to build only agl-service-windowmanager-2017 using yocto. > > > So, I tried like bellow. > > step - 1) modifiy source code : > AGL_QEMU_EE/build/tmp/work/corei7-64-agl-linux/agl-service-windowmanager-2017/1.0+gitAUTOINC+12c8934465-r0/git/src/main.cpp > > step - 2) use bitbake command : bitbake agl-service-windowmanager-2017 > > > But, nothing to change. I wonder is it right directory for qemu > windowmanager source at step - 1? > And is it right command for build agl-service-windowmanager-2017 ? > > > Please help me in this regard. > > > Thanks & Regards, > Josh. > > > > > > -- > *Jung Young Moon DrimAES Inc.* > * > **Address* *#803, Ace Twin Tower 2-cha, 273, Digital-ro, Guro-gu, > Seoul, Korea > * > *Mobile* *+82 (0)10 - 4907 - 2117* > *Mail* jung at drimaes.com > > > > > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions -- ******************************* WITZ Corporation ??????? ??????? Base Technology Development Dept. ?Advanced Basic Technology Sect. ?Kazumasa Mitsunari Mail:knimitz at witz-inc.co.jp ******************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: From jung at drimaes.com Tue Feb 27 03:38:34 2018 From: jung at drimaes.com (=?UTF-8?B?7KCV7JiB66y4?=) Date: Tue, 27 Feb 2018 12:38:34 +0900 Subject: [agl-discussions] how to build only agl-service-windowmanager-2017 using yocto? In-Reply-To: <9db60f5d-261d-a361-b675-d3ac13050edc@witz-inc.co.jp> References: <9db60f5d-261d-a361-b675-d3ac13050edc@witz-inc.co.jp> Message-ID: Oh Thank you your fask reply!! Thanks, both way working well. If use first way, result file is created {AGL_Build_Dir}/build/tmp/work/corei7-64-agl-linux/agl-service-windowmanager-2017/1.0+gitAUTOINC+12c8934465-r0/build/package in my case. thanks again. Thanks & Regards, Josh. 2018-02-27 12:20 GMT+09:00 Kazumasa Mitsunari : > Hi > > bitbake normally uses cache unless modifying recipe, so nothing happens > however you edit source code in tmp directory. > > If you would like to re-compile compulsorily, please command the following > > bitbake -f -c compile > bitbake ( if you need installing/packaging ... > but for generating wgt file, this is necessary) > > or if you use SDK > > source > cd > mkdir build; cd build > cmake .. > make > make package > > Please try:) > > Best Regards > Kazumasa Mitsunari > > > On 2018?02?27? 12:06, ??? wrote: > > Hello AGL, > > > I am studying AGL Windowmanager.(AGL 5.0.0 on QEMU) > I just want to build only agl-service-windowmanager-2017 using yocto. > > > So, I tried like bellow. > > step - 1) modifiy source code : AGL_QEMU_EE/build/tmp/work/ > corei7-64-agl-linux/agl-service-windowmanager-2017/1. > 0+gitAUTOINC+12c8934465-r0/git/src/main.cpp > > step - 2) use bitbake command : bitbake agl-service-windowmanager-2017 > > > But, nothing to change. I wonder is it right directory for qemu > windowmanager source at step - 1? > And is it right command for build agl-service-windowmanager-2017 ? > > > Please help me in this regard. > > > Thanks & Regards, > Josh. > > > > > > -- > *Jung Young Moon DrimAES Inc.* > > *Address* *#803, Ace Twin Tower 2-cha, 273, Digital-ro, Guro-gu, Seoul, > Korea > * > *Mobile* *+82 (0)10 - 4907 - 2117* > *Mail* jung at drimaes.com > > > > > _______________________________________________ > automotive-discussions mailing listautomotive-discussions at lists.linuxfoundation.orghttps://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions > > > -- > ******************************* > WITZ Corporation > ??????? ??????? > Base Technology Development Dept. > ?Advanced Basic Technology Sect. > ?Kazumasa Mitsunari > Mail:knimitz at witz-inc.co.jp > ******************************* > > -- *Jung Young Moon DrimAES Inc.* *Address* *#803, Ace Twin Tower 2-cha, 273, Digital-ro, Guro-gu, Seoul, Korea * *Mobile* *+82 (0)10 - 4907 - 2117* *Mail* jung at drimaes.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dohoon.kim at drimaes.com Tue Feb 27 08:41:30 2018 From: dohoon.kim at drimaes.com (=?UTF-8?B?6rmA64+E7ZuI?=) Date: Tue, 27 Feb 2018 17:41:30 +0900 Subject: [agl-discussions] How to upload blue-tooth services Message-ID: Dear ALL AGL members, I am checking AGL 5.0.0 to play media via Bluetooth connection with NXP i.MX6 Quad (imx6qsabreauto). When I checked bluetooth services like below, there are no Audio Sink, Audio Source service. What I would like to ask is how to upload Audio Sink, Audio Source service. The result of the show command in the bluetoothctl terminal. UUID: Generic Attribute Profile (00001801-0000-1000-8000- 00805f9b34fb) UUID: A / V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb) UUID: A / V Remote Control Target (0000110c-0000-1000-8000- 00805f9b34fb) Can I upload services at the command level? Or do I need to modify the kernel source? Please help me in this regard. Thanks & Regards, Ciervo. -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.eggleton at linux.intel.com Tue Feb 27 20:25:17 2018 From: paul.eggleton at linux.intel.com (Paul Eggleton) Date: Wed, 28 Feb 2018 09:25:17 +1300 Subject: [agl-discussions] how to build only agl-service-windowmanager-2017 using yocto? In-Reply-To: <9db60f5d-261d-a361-b675-d3ac13050edc@witz-inc.co.jp> References: <9db60f5d-261d-a361-b675-d3ac13050edc@witz-inc.co.jp> Message-ID: <11693270.iBFJ5ux645@peggleto-mobl.ger.corp.intel.com> On Tuesday, 27 February 2018 4:20:30 PM NZDT Kazumasa Mitsunari wrote: > bitbake normally uses cache unless modifying recipe, so nothing happens > however you edit source code in tmp directory. > > If you would like to re-compile compulsorily, please command the following > > bitbake -f -c compile > bitbake ( if you need installing/packaging ... > but for generating wgt file, this is necessary) >From a pure build system perspective I'd recommend using "devtool modify" instead of touching the source under the tmp directory and using bitbake -f. There is some documentation for devtool here (just ignore the fact that it mentions the SDK, we have some structural issues in the manual that need to be worked out): http://www.yoctoproject.org/docs/2.5/sdk-manual/sdk-manual.html#sdk-devtool-use-devtool-modify-to-modify-the-source-of-an-existing-component If you do try this, let me know if you have any further questions / issues. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre From tmatsuzawa at xevo.com Wed Feb 28 01:20:37 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Wed, 28 Feb 2018 01:20:37 +0000 Subject: [agl-discussions] How to upload blue-tooth services In-Reply-To: References: Message-ID: Hello. I have not tried with the latest builds, but the below is before you pair your BT device (e.g. smartphone) to the SABRE board, or after? ________________________________________ From: automotive-discussions-bounces at lists.linuxfoundation.org on behalf of ??? Sent: Tuesday, February 27, 2018 5:41:30 PM To: automotive-discussions at lists.linuxfoundation.org Subject: [agl-discussions] How to upload blue-tooth services Dear ALL AGL members, I am checking AGL 5.0.0 to play media via Bluetooth connection with NXP i.MX6 Quad (imx6qsabreauto). When I checked bluetooth services like below, there are no Audio Sink, Audio Source service. What I would like to ask is how to upload Audio Sink, Audio Source service. The result of the show command in the bluetoothctl terminal. UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: A / V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb) UUID: A / V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) Can I upload services at the command level? Or do I need to modify the kernel source? Please help me in this regard. Thanks & Regards, Ciervo. From dohoon.kim at drimaes.com Wed Feb 28 02:41:16 2018 From: dohoon.kim at drimaes.com (=?UTF-8?B?6rmA64+E7ZuI?=) Date: Wed, 28 Feb 2018 11:41:16 +0900 Subject: [agl-discussions] How to upload blue-tooth services In-Reply-To: References: Message-ID: The results of the show command were not in a paired state with any device. I have now finished connecting to the smartphone. However, when connecting to a smartphone, music is not output to the SABER board even if music is played on the smartphone because only the Handsfree profile is captured. So I am looking for a way to upload Audio Sink and Audio Source service by applying A2DP profile in AGL. 2018-02-28 10:20 GMT+09:00 Takashi Matsuzawa : > Hello. > I have not tried with the latest builds, but the below is before you pair > your BT device (e.g. smartphone) to the SABRE board, or after? > > ________________________________________ > From: automotive-discussions-bounces at lists.linuxfoundation.org < > automotive-discussions-bounces at lists.linuxfoundation.org> on behalf of > ??? > Sent: Tuesday, February 27, 2018 5:41:30 PM > To: automotive-discussions at lists.linuxfoundation.org > Subject: [agl-discussions] How to upload blue-tooth services > > Dear ALL AGL members, > > I am checking AGL 5.0.0 to play media via Bluetooth connection with NXP > i.MX6 Quad (imx6qsabreauto). > > When I checked bluetooth services like below, there are no Audio Sink, > Audio Source service. > > What I would like to ask is how to upload Audio Sink, Audio Source service. > The result of the show command in the bluetoothctl terminal. > > UUID: Generic Attribute Profile (00001801-0000-1000-8000- > 00805f9b34fb) > UUID: A / V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) > UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) > UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) > UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb) > UUID: A / V Remote Control Target (0000110c-0000-1000-8000- > 00805f9b34fb) > > > Can I upload services at the command level? Or do I need to modify the > kernel source? > > > Please help me in this regard. > > > Thanks & Regards, > Ciervo. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tmatsuzawa at xevo.com Wed Feb 28 03:23:40 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Wed, 28 Feb 2018 03:23:40 +0000 Subject: [agl-discussions] How to upload blue-tooth services In-Reply-To: References: , Message-ID: OK, I looked back my notes and confirmed that you do not need pair a device to Audio Sink to be listed on bluetoothctl show list. I cannot immediately reproduce or try on actual board, but I remember you may need to check: 1) Is pulseaudio running? I think you can check ps output to see if it is running or not. 2) I remember at least you need following plugins for pulseaudio so that audio sink is enabled. pulseaudio-module-bluetooth-discover pulseaudio-module-bluetooth-policy pulseaudio-module-bluez5-discover pulseaudio-module-bluez5-device pulseaudio-module-switch-on-connect pulseaudio-module-loopback ________________________________________ From: ??? Sent: Wednesday, February 28, 2018 11:41 AM To: Takashi Matsuzawa Cc: automotive-discussions at lists.linuxfoundation.org Subject: Re: [agl-discussions] How to upload blue-tooth services The results of the show command were not in a paired state with any device. I have now finished connecting to the smartphone. However, when connecting to a smartphone, music is not output to the SABER board even if music is played on the smartphone because only the Handsfree profile is captured. So I am looking for a way to upload Audio Sink and Audio Source service by applying A2DP profile in AGL. 2018-02-28 10:20 GMT+09:00 Takashi Matsuzawa >: Hello. I have not tried with the latest builds, but the below is before you pair your BT device (e.g. smartphone) to the SABRE board, or after? ________________________________________ From: automotive-discussions-bounces at lists.linuxfoundation.org > on behalf of ??? > Sent: Tuesday, February 27, 2018 5:41:30 PM To: automotive-discussions at lists.linuxfoundation.org Subject: [agl-discussions] How to upload blue-tooth services Dear ALL AGL members, I am checking AGL 5.0.0 to play media via Bluetooth connection with NXP i.MX6 Quad (imx6qsabreauto). When I checked bluetooth services like below, there are no Audio Sink, Audio Source service. What I would like to ask is how to upload Audio Sink, Audio Source service. The result of the show command in the bluetoothctl terminal. UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: A / V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb) UUID: A / V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) Can I upload services at the command level? Or do I need to modify the kernel source? Please help me in this regard. Thanks & Regards, Ciervo. From ligzligz at gmail.com Wed Feb 28 04:40:36 2018 From: ligzligz at gmail.com (Guozhen Li) Date: Tue, 27 Feb 2018 20:40:36 -0800 Subject: [agl-discussions] =?utf-8?q?Error_when_building_AGL_for_Raspberry?= =?utf-8?q?_Pi_2=3A_=E2=80=8B=22qtxmlpatterns-5=2E8=2E0+gitAUTOINC+?= =?utf-8?q?9f7e01b582-r0_do=5Fpackage=3A_QA_Issue=22?= Message-ID: Hello AGL members, I am a computer science student I just got started with AGL. I was attempting to build AGL to run on a Raspberry Pi 2, following this documentation page from AGL Wiki: https://wiki.automotivelinux.org/agl-distro/agl-raspberrypi However I receive this error: > ERROR: > ?? > qtxmlpatterns-5.8.0+gitAUTOINC+9f7e01b582-r0 do_package: QA Issue: > qtxmlpatterns: Files/directories were installed but not shipped in any > package: ?...? during the final command bitbake agl-demo-platform Has someone experienced this issue and know how to fix it? Or can I get some directions on how to get help? Thank you! I'll append the system info and error messages at the end. ============================== My system information: Ubuntu 16.04 LTS on a VirtualBox virtual machine with 8GB memory and 160GB disk. Error message: (starting from running the bitbake command) ~/AGL/build$ bitbake agl-demo-platform Loading cache: 100% |############################################| Time: 0:00:01 Loaded 2922 entries from dependency cache. WARNING: No bb files matched BBFILE_PATTERN_agl-distro '^/home/guozhen/AGL/meta-agl/meta-agl-distro/' NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.32.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "arm-agl-linux-gnueabi" MACHINE = "raspberrypi2" DISTRO = "poky-agl" DISTRO_VERSION = "4.0.3" TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard" TARGET_FPU = "hard" meta-raspberrypi = "HEAD:28d4404f89eb59d406b4976c0e3f5ca19137ba74" meta-netboot = "HEAD:1b2addabaa24897db6beb1c5627d7f283e57f2a3" meta-security-smack meta-security-framework = "HEAD:20bbb97f6d5400b126ae96ef446c3e60c7e16285" meta-app-framework = "HEAD:1b2addabaa24897db6beb1c5627d7f283e57f2a3" meta-qt5 = "HEAD:5f837b47f5c3e462f24cd5abf58ff6ef1dd04932" meta-agl-demo = "HEAD:65619655cb3f373a1b15da7a4d91191a2867464b" meta-oe meta-multimedia meta-efl meta-networking meta-python meta-filesystems = "HEAD:b40116cf457b88a2db14b86fda9627fb34d56ae6" meta-ivi-common meta-agl meta-agl-distro meta-agl-bsp = "HEAD:1b2addabaa24897db6beb1c5627d7f283e57f2a3" meta meta-poky = "HEAD:1f5effb6a650c1c7007faf41c91e5cbfdf907a21" Initialising tasks: 100% |#######################################| Time: 0:00:09 NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: qtxmlpatterns-5.8.0+gitAUTOINC+9f7e01b582-r0 do_package: QA Issue: qtxmlpatterns: Files/directories were installed but not shipped in any package: /home/guozhen/AGL/build/tmp/sysroots/raspberrypi3/usr/include /home/guozhen/AGL/build/tmp/sysroots/raspberrypi3/usr/bin/qt5/xmlpatterns /home/guozhen/AGL/build/tmp/sysroots/raspberrypi3/usr/bin/qt5/xmlpatternsvalidator /home/guozhen/AGL/build/tmp/sysroots/raspberrypi3/usr/include/qt5 /home/guozhen/AGL/build/tmp/sysroots/raspberrypi3/usr/include/qt5/QtXmlPatterns /home/guozhen/AGL/build/tmp/sysroots/raspberrypi3/usr/include/qt5/QtXmlPatterns/QAbstractXmlReceiver /home/guozhen/AGL/build/tmp/sysroots/raspberrypi3/usr/include/qt5/QtXmlPatterns/QXmlResultItems /home/guozhen/AGL/build/tmp/sysroots/raspberrypi3/usr/include/qt5/QtXmlPatterns/qxmlnamepool.h (omitting many similar lines of paths) /home/guozhen/AGL/build/tmp/sysroots/raspberrypi3/usr/lib/qt5/mkspecs /home/guozhen/AGL/build/tmp/sysroots/raspberrypi3/usr/lib/qt5/mkspecs/modules /home/guozhen/AGL/build/tmp/sysroots/raspberrypi3/usr/lib/qt5/mkspecs/modules/qt_lib_xmlpatterns_private.pri /home/guozhen/AGL/build/tmp/sysroots/raspberrypi3/usr/lib/qt5/mkspecs/modules/qt_lib_xmlpatterns.pri /home/guozhen/AGL/build/tmp/sysroots/raspberrypi3/usr/lib/pkgconfig/Qt5XmlPatterns.pc Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install. qtxmlpatterns: 429 installed and not shipped files. [installed-vs-shipped] ERROR: qtxmlpatterns-5.8.0+gitAUTOINC+9f7e01b582-r0 do_package: Fatal QA errors found, failing task. ERROR: qtxmlpatterns-5.8.0+gitAUTOINC+9f7e01b582-r0 do_package: Function failed: do_package ERROR: Logfile of failure stored in: /home/guozhen/AGL/build/tmp/work/armv7vehf-neon-vfpv4-agl-linux-gnueabi/qtxmlpatterns/5.8.0+gitAUTOINC+9f7e01b582-r0/temp/log.do_package.4377 ERROR: Task (/home/guozhen/AGL/meta-qt5/recipes-qt/qt5/qtxmlpatterns_git.bb:do_package) failed with exit code '1' NOTE: Tasks Summary: Attempted 2311 tasks of which 2303 didn't need to be rerun and 1 failed. Summary: 1 task failed: /home/guozhen/AGL/meta-qt5/recipes-qt/qt5/qtxmlpatterns_git.bb:do_package Summary: There was 1 WARNING message shown. Summary: There were 3 ERROR messages shown, returning a non-zero exit code. -- ??? Guozhen Li -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.farrugia at fiberdyne.com.au Wed Feb 28 08:14:48 2018 From: mark.farrugia at fiberdyne.com.au (Mark Farrugia) Date: Wed, 28 Feb 2018 08:14:48 +0000 Subject: [agl-discussions] Fiberdyne DSP 4A HAL Message-ID: Hi all, Our team here at Fiberdyne Systems have just concluded our 2 day workshop regarding the AGL 4A HAL, in conjunction with Fulup Le Foll of IoT.bzh. We have formulated a JSON configuration specification from which we will implement a newly designed 4A HAL targeting the AGL FF release in mid-year. The HAL will contain the capabilities to include the Fiberdyne HiFi2 DSP on the Renesas Gen 3 platform. The source for the configuration file is currently located here: https://github.com/fiberdyne/agl-4a-hal Any and all feedback is welcome! Cheers, Mark Farrugia, Fiberdyne Systems [image: 0.jpeg] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0.jpeg Type: image/jpeg Size: 72200 bytes Desc: not available URL: From tmatsuzawa at xevo.com Wed Feb 28 09:56:30 2018 From: tmatsuzawa at xevo.com (Takashi Matsuzawa) Date: Wed, 28 Feb 2018 09:56:30 +0000 Subject: [agl-discussions] A few questions on ivi-shell behavior Message-ID: Hello. I started trying multiple display configuration for my spare time. Maybe basic questions around ivi-shell, but I wanted to confirm. 1) How screen ids are assigned? 0, 1, 2, ... are assigned without reason? can I predict to which display screen #0 is assigned? 2) how to identify screens(displays)? Assuming I cannot predict how screen #s are assigned to physical displays, how can I identify screens<->displays? Only by their diensions? 3) Who should be assigning layers/surfaces? It is assumed to be the task of window manager to assign layers to screens? (i.e. Window manager need to know which layers go to which screens) From wmizuno at jp.adit-jv.com Wed Feb 28 11:52:18 2018 From: wmizuno at jp.adit-jv.com (Mizuno, Wataru (ADITJ/SWG)) Date: Wed, 28 Feb 2018 11:52:18 +0000 Subject: [agl-discussions] A few questions on ivi-shell behavior In-Reply-To: References: Message-ID: <3AF4192FBB4D2C458558336708E909930500FE8A@ky0exch01.adit-jv.com> Hi, >1) How screen ids are assigned? >0, 1, 2, ... are assigned without reason? can I predict to which display screen #0 is assigned? This is assigned the order that output is identified by weston. >2) how to identify screens(displays)? Weston maintains display by unit of "weston_output". AGL case this is initialized in drm-backend initialization time at "create_output_for_connector". >3) Who should be assigning layers/surfaces? > It is assumed to be the task of window manager to assign layers to screens? I think so too. Best regards, Wataru Mizuno ADITJ / SWG +81-(0)566-56-0946 -----Original Message----- From: automotive-discussions-bounces at lists.linuxfoundation.org [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On Behalf Of Takashi Matsuzawa Sent: Wednesday, February 28, 2018 6:57 PM To: automotive-discussions at lists.linuxfoundation.org Subject: [agl-discussions] A few questions on ivi-shell behavior Hello. I started trying multiple display configuration for my spare time. Maybe basic questions around ivi-shell, but I wanted to confirm. 1) How screen ids are assigned? 0, 1, 2, ... are assigned without reason? can I predict to which display screen #0 is assigned? 2) how to identify screens(displays)? Assuming I cannot predict how screen #s are assigned to physical displays, how can I identify screens<->displays? Only by their diensions? 3) Who should be assigning layers/surfaces? It is assumed to be the task of window manager to assign layers to screens? (i.e. Window manager need to know which layers go to which screens) _______________________________________________ automotive-discussions mailing list automotive-discussions at lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From eucan at de.adit-jv.com Wed Feb 28 14:19:49 2018 From: eucan at de.adit-jv.com (Ucan, Emre (ADITG/ESB)) Date: Wed, 28 Feb 2018 14:19:49 +0000 Subject: [agl-discussions] A few questions on ivi-shell behavior In-Reply-To: References: Message-ID: Hi, You can get name of the connector (e.g. HDMI-A-1, LVDS1) from ilm_getPropertiesOfScreen API. Best regards Emre Ucan Engineering Software Base (ADITG/ESB) Tel. +49 5121 49 6937 > -----Original Message----- > From: automotive-discussions-bounces at lists.linuxfoundation.org > [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On > Behalf Of Takashi Matsuzawa > Sent: Mittwoch, 28. Februar 2018 10:57 > To: automotive-discussions at lists.linuxfoundation.org > Subject: [agl-discussions] A few questions on ivi-shell behavior > > Hello. > I started trying multiple display configuration for my spare time. > Maybe basic questions around ivi-shell, but I wanted to confirm. > > 1) How screen ids are assigned? > > 0, 1, 2, ... are assigned without reason? can I predict to which display screen > #0 is assigned? > > 2) how to identify screens(displays)? > > Assuming I cannot predict how screen #s are assigned to physical displays, > how can I identify screens<->displays? Only by their diensions? > > 3) Who should be assigning layers/surfaces? > > It is assumed to be the task of window manager to assign layers to screens? > (i.e. Window manager need to know which layers go to which screens) > _______________________________________________ > automotive-discussions mailing list > automotive-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions From 4mekki4 at gmail.com Wed Feb 28 15:03:39 2018 From: 4mekki4 at gmail.com (Abdellah EL MEKKI) Date: Wed, 28 Feb 2018 15:03:39 +0000 Subject: [agl-discussions] How to build an app on AGL ( HTML5) Message-ID: Hello , I'm new in the AGL OS . My objective is to build or make a simple hello world HTML5 app that i can run on AGL . When i've followed the tutorial on the documentation . they said that they're building the app for Renesas . I want to build the app for Raspberry . Okay , the second thing , is there a simple method to run an html5 app ? Finally , Is there a video tutorial about that . Thank you & best regards ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From jose.bollo at iot.bzh Wed Feb 28 16:06:01 2018 From: jose.bollo at iot.bzh (=?UTF-8?B?Sm9zw6k=?= Bollo) Date: Wed, 28 Feb 2018 17:06:01 +0100 Subject: [agl-discussions] How to build an app on AGL ( HTML5) In-Reply-To: References: Message-ID: <20180228170601.059a21a4@d-jobol.iot.bzh> On Wed, 28 Feb 2018 15:03:39 +0000 Abdellah EL MEKKI <4mekki4 at gmail.com> wrote: > Hello , Hello Abdellah, > I'm new in the AGL OS . My objective is to build or make a simple > hello world HTML5 app that i can run on AGL . > When i've followed the tutorial on the documentation . they said that > they're building the app for Renesas . I want to build the app for > Raspberry . I think it is only a matter of availability of the web-runtime-engine (WRT). There are in progress effort to brings it in AGL. At this time, a kind of WRT is available in agl-demo-platform by using qtwebengine. It should be available for rasperry but I'm not 100% sure cause I don't usually run on that board. > Okay , the second thing , is there a simple method to run an html5 > app ? In few words: put the files in a sub-directory named 'htdocs' then create the config.xml file according to [1]. zip all that as a widget that you can install using 'afm-util install X' [1] http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/af-main/2.2-config.xml.html Actually the problem is that your app will not be shown because it is not integrated with the homescreen and the window manager. To bypass this restriction, we usually replace the app POI (point of interest). To do so just set the id to "poi" and the version to "0.1". > Finally , Is there a video tutorial about that . I don't think so. But it is a good idea. Best regards Jos? Bollo > > Thank you & best regards > > > ?