Date: Thu, 28 Mar 2024 22:24:04 +0000 (UTC)
Message-ID: <1456710193.20334.1711664644885@aws-us-west-2-agl-confluence-1.web.codeaurora.org>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_20333_2077137946.1711664644882"
------=_Part_20333_2077137946.1711664644882
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
AGL Production Readiness
AGL Production Readiness
- Repeatable builds
- License traceability and formal distribution of required source code&nb=
sp;
- Use "GPLv2 only" version of OE and Poky?
- Is Yocto's built in license manifest support sufficient for AGL deliver=
y or do we need to run FOSSology on our releases? The OEM and/or Tier=
One will need to run their own scanners anyway since they are responsible =
for the final product release that is delivered to their customer.
- Test reports available for releases at a component level
- Long-term support of AGL releases available
- SDK with IDE/GUI for application developers.
- Documentation about how to use AGL to create a production system
- Complete documentation of AGL components and APIs
- What functionality is required by OEMs? Is there a gap we need to cover=
that is not in our current roadmap?
- What patent information would we need to provide? Is providing a =
list of components to OIN sufficient or it there some other work members ex=
pect AGL to provide? BSP should be OSS with support provided by the SOC ven=
dor. Production BSPs provided to device creators by SOC vendors need to be =
shared with AGL to enable validation against the AGL software.
To do
- Ideally each OEM and/or Tier One provides an analysis of the AGL compon=
ents they are considering using in their mass production systems. The analy=
sis would include whether they plan to include the component and the curren=
t status of the component with respect to their product plan. If there are =
gaps that need to be filled AGL can than consider how to fill those gaps.=
li>
- Current Toyota products using AGL do not use AGL directly, but they tak=
e in AGL and modify it. What lessons has Toyota learned that we can apply t=
o AGL that would allow them more directly use AGL.
- Denso Ten has performed a comparison of the current AGL API available (=
200+) to their current production platform (1000+). Denso Ten will pr=
ovide this analysis later this year once it has been translated from Japane=
se.
APIGapAnalysis_20190704.pdf
AGL_RadioAPI.pdf=
------=_Part_20333_2077137946.1711664644882--