Skip to:
Gather requirements for creating a Telematics device profile.
a. What is a profile?
b. By choosing a profile what does that define?
A profile includes a subset of available BSPs within AGL.
c. Package selection and building versus delivery of binaries and file systems.
We envision four specific device profiles:
1) IVI - Includes AGL App FW and full graphics subsystem. Does not include Qt.
2) Headless or Telematics system - AGL App FW without graphics subsystem. Optional telephony.
3) AGL IVI Demo - Includes demo applications
Can close and let V2C EG work out the three POC.
Telematics profile created in git. Need to add use cases from Connectivity EG to Confluence then can close this issue.
Requirements/Use-cases needed.
The folders for the profiles
meta-agl-profile-telematics
and
meta-agl-profile-hud
exist now as (empty) shells
We need the requriements to start populating the layers/profiles.
Major
MajorMajor
Gather requirements for creating a Telematics device profile.
a. What is a profile?
b. By choosing a profile what does that define?
A profile includes a subset of available BSPs within AGL.
c. Package selection and building versus delivery of binaries and file systems.
We envision four specific device profiles:
1) IVI - Includes AGL App FW and full graphics subsystem. Does not include Qt.
2) Headless or Telematics system - AGL App FW without graphics subsystem. Optional telephony.
3) AGL IVI Demo - Includes demo applications