Attendees

  • David Rusling
  • Patrik Ryd
  • Loïc Minier
  • Steve McIntyre

  • Grant Likely
  • Roger Teague (ARM)
  • Oliver Hartfuß (Genivi)
  • Nicola Magustro (ST Ericsson, software application manager)
  • Paul McKenny (IBM)

Agenda

  • Discussion with Genivi about their requirements

Minutes

  • Round of introductions
  • Boot time
    • We have countries where OEMs have to show review cameras in 2s or less after system start up
      • There are legal implications
      • Have to prove performance
      • Includes getting video up, participating in the CAN bus
      • Systems are booting fast enough, typical set up of today
        • Automotive I/O controller + CPU
        • Automotive I/O really low power, powers on the main CPU, provides a reason for waking
        • Current systems load CPU 100% doing the most important stuff first
      • Over time, I/0 and CAN controller will move into the SoC
      • Boot time is an issue in Linaro
        • Beagle booted to running applications in 200 milliseconds (barebox)
    • Other realtime hardware contstraints
      • Two levels of communication on the CAN bus, network management (e.g. initialize/shut down the bus) + application messages (e.g. ignition on/off), plus when the system can process messages etc
    • Does Genivi specify / adhere any software development standards (standards, dual redundancy, etc)
      • Not for IVI
  • Kernel
    • Automotive specific subsystems, such as CAN bus
      • Many discussions going on in Linux
      • Today most devices have several buses, I/O controller controls the bus, CPU just a client (based on message passing)
      • Tomorrow's SoCs may include CAN

      • Current Linux CAN drivers may not hit message latency constraints
  • Automototive specific applications and libraries
    • How to use standard applications on the market and improve them with automotive systems
    • Trying to make use of available components
    • Also special automotive applications, such as lifecycle management (monitoring the health of the system)
    • Update is a desirable feature (controlled, avoid updates randomly, keep system sane after an update)
      • Automotive community very nervous of software updates
      • Currently releases of software versions is approx. 1 year, updates are only done within the dealer ship (this is completely different to consumer devices)
      • Today the IVI systems are updated by replacing the complete image, no partials/package based updates. This might change since it is causing problems and is expensive (update time at the dealer ship)
  • Graphics stack
    • Currently avoiding this discussion (political and emotional)
    • Look and feel is a key OEM differentiator
    • OpenGLES 2.0 must be available
    • Qt core being used
  • Multimedia stack
    • Currently gstreamer is mandated, but not which codecs
    • Most Tier 1's feel that they cannot rely on gstreamer, so use a proprietary stack
  • Build system?
    • Have a good solution that allows the use of several input distributions to build the development baseline (which is used within GENIVI for further development)
    • OBS
  • The main output of Genivi is a compliance document
    • Want to make this document available
      • Will it be published openly?
        • Not for the first release, discussion still open
  • Do companies such as BMW have requirements that are stronger than Genivi's?
    • In general GENIVI is meant to cover commodity features that are common to many/all OEMs. This means that OEMs will have additional/stronger requirements than GENIVI.
  • Genivi questions
    • Audio management - control, processing (mix, convert, process audio within the CPU, mostly DSP)
    • Efficient sharing of media (buffer management, video, multimedia, graphics)
  • Any tool chain requirements (gcc, gdb etc)?
    • Are interested in supporting ARM as well as possible
    • If we use an Ubuntu distribution, then get the latest and best
  • Any interest in Android?
    • Not at the moment
    • What use case? Can't influence the look and feel for Android.

OfficeofCTO/2011-03-31 (last modified 2011-03-31 17:29:34)