[agl-discussions] 3.0 released features?

[Fulup Ar Foll]

How to allow or not someone to use AGL brand is a real question. 
Nevertheless as today they is no AGL compliance test, no plan to create 
one and thus no option to claim AGL compatibility. For CES and AGL/3.0, 
the main constrain was for projects to be integrated with the 
application framework, the homescreen and the security model.

Defining who and under which conditions a solution can claim to be 
"powered by AGL" is clearly something that need to be addressed. 
Supporting out of the box references/demo applications through the 
applications framework and with AGL security model active could be a 
first set of minimal requirements, nevertheless having a reference tests 
suite would also create a lot of value.

This being said, defining the right to use AGL brand for a given product 
is going far being technical only issues. This problem needs 1st to be 
address by the board before the architecture group may start working of 
how a technology could help in giving any form of approval.

Fulup



On 06/01/17 23:45, Takashi Matsuzawa wrote:
> Thank you , so list of changes (or link to them) will be there soon.
>
>
> What confuses me a bit is relationship with the released features list,
> UCB/BSP sources, and  what OEMs use in their products.
>
> My understanding is that we do not use BSP as it is, and
> re-configure/make changes to the configuration ro real products. And as
> long as it is 'based' on UCB, we are running AGL and can claim AGL
> compatible?
>
>
> ------------------------------------------------------------------------
> *From:* Jan-Simon Möller <dl9pf at gmx.de>
> *Sent:* Friday, January 6, 2017 8:07 PM
> *To:* automotive-discussions at lists.linuxfoundation.org
> *Cc:* Takashi Matsuzawa
> *Subject:* Re: [agl-discussions] 3.0 released features?
>
> https://wiki.automotivelinux.org/agl-distro/release-notes
> will contain the list.
>
> --
>
> Dipl.-Ing.
> Jan-Simon Möller
>
> jansimon.moeller at gmx.de
> On Friday 06 January 2017 04:37:00 Takashi Matsuzawa wrote:
>> Hello AGL.
>>
>> I am looking into the 3.0 Chinook release news statement:
>> >https://www.automotivelinux.org/news/announcement/2016/12/automotive-grade->
>>linux-releases-open-infotainment-platform-built
>> Is there easy way to map some of the following 3.0 features to jira tickets
>> or Yocto recipes so that I can know them preciesly (what are AGL specific
>> inventsions or integration).
>>
>> e.g.
>> I do not think there is no SmartDeviceLink recipe in AGL BSP but just sowed
>> by using external (meaning, not part of BSP/UCB) components, though it can
>> be referred in GENIVI code? Rear views and simultaneous display is
>> supported by particular components (may be added in AGL) and apps need to
>> take advantage of them?
>> >- A brand new home screen and window manager
>> >- An improved application framework and application launcher
>> >- A new SDK for rapid application development
>> >- Reference applications including media player, tuner, navigation,
>> >Bluetooth, WiFi, HVAC control, audio mixer and vehicle controls -
>> >Integration with simultaneous display on instrument cluster
>> >- Smart Device Link for mobile phone integration
>> >- Rear view camera and rear seat entertainment on MOST ring
>> >- Wide range of hardware board support including Renesas, Qualcomm
>> >Technologies, Intel, Texas Instrument, NXP and Raspberry Pi
>
>
>
> _______________________________________________
> automotive-discussions mailing list
> automotive-discussions at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions
>