Download to read offline
Uploaded byCodecamp Romania
Eugen Constantinescu - Genivi - Codecamp 10 may 2014
Genivi is an open source project for in-vehicle infotainment systems. It was created to build trust, have a quick development cycle, save development effort, and improve security. The project uses open governance and communities to develop components like Bluetooth, media playback, and connectivity solutions. It has expert groups focused on different domains that host multiple projects. Genivi uses D-Bus for inter-process communication and plugins to extend functionality. Codecamps are held to further the goals of building trust, quick development, saving effort, and improving security through open source collaboration.
More Related Content
Similar to Eugen Constantinescu - Genivi - Codecamp 10 may 2014
Eugen Constantinescu - Genivi - Codecamp 10 may 2014
- 1. Genivi How and Why OpenSource
- 3.
- 4. Golden circles (SimonSinek, TED) Why? How? What?
- 5.
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14. What Problems GPL V3is virtually banned from cars. Who is fixing the problems? Who is responsible in front of customer? Who define the components interfaces? Lifecycle management (as seen in automotive) Anti-pattern mindset Corporation vs Open Source
- 15. What Solutions Communities Inter ProcessCommunication(D-BUS) Plug-ins
- 16.
- 17. Each developmentteam typically has its mailing list and holds weekly conference calls ◦ genivi-dev@mail.genivi.org Each team typically arranges several face-to- face meeting per year Two times a year all participants meet during GENIVI All Member Meetings SAT has sub-teams for security and compliance Each Expert Group hosts multiple projects Team Working Mode 17
- 18. 18 CE Connectivity EGScope Bluetooth • Hands-Free Profile (HFP) • Advanced Audio Distribution Profile (A2DP) • Audio/Video Remote Control Profile (AVRCP) • Device ID Profile (DID) • Dial-up Networking Profile (DUN) • File Transfer Profile (FTP) • Headset Profile (HSP) • Object Push Profile (OPP) • Personal Area Networking Profile (PAN) • Phone Book Access Profile (PBAP) • Message Access Profile (MAP) • Low Energy iPod • iPod Out • iAP Media Playback • Media Pipeline • Audio Management • Video Audio Sync • Phonetic Database Device management • Device Detection • Device Identification • Device Classification AV • HDMI inc Wireless • MHL • 3.5mm Jack • AV USB • Composite Video • MiraCast Thunderbolt SATA eSATA AV • DVI • LVDS • VGA 1394 Firewire WiFi DLNA/UPnP • WiFi NFC • NFC • ChargingMedia Playback • Media Indexing • Playback Control • Playlist management • Media Source Abstraction • Metadata Enhancement USB • Wireless Dongle • WiMax • Wifi Smart Device • Common APi • Mirrorlink • IVILink Digital Rights management = Active project USB • Mass Storage • Multimedia Portable Devices • MTP, PTP. = Not currently active TCP/IP • USB • Bluetooth • WiFi Wireless Charging
- 19. 19 CE Connectivity EGScope = Active project= Not currently active Bluetooth • Hands-Free Profile (HFP) • Advanced Audio Distribution Profile (A2DP) • Audio/Video Remote Control Profile (AVRCP) • Device ID Profile (DID) • Dial-up Networking Profile (DUN) • File Transfer Profile (FTP) • Headset Profile (HSP) • Object Push Profile (OPP) • Personal Area Networking Profile (PAN) • Phone Book Access Profile (PBAP) • Message Access Profile (MAP) • Low Energy iPod • iPod Out • iAP Device management • Device Detection • Device Identification • Device Classification AV • HDMI inc Wireless • MHL • 3.5mm Jack • AV USB • Composite Video • MiraCast DLNA/UPnP • WiFi NFC • NFC • Charging Media Playback • Media Indexing • Playback Control • Playlist management • Media Source Abstraction • Metadata Enhancement Smart Device • Common API • Mirrorlink • IVILink USB • Mass Storage • Multimedia Portable Devices • MTP, PTP. Wireless Charging
- 20.
- 21. Plug-ins typedef int (*PluginFunction)(int); void*plugin = dlopen("plugin.so", RTLD_NOW); PluginFunction *pFunction = dlsym(plugin, “FunctionNameAsDeclaredInInterface"); pFunction(10); dlclose(plugin);
- 22.
- 23.
- 25. Why and Howto do business with Open Source Genivi Eugen Constantinescu Continental 10th of May 2014 Please fill in your evaluation form
Editor's Notes
- #2 Ce este Genivi? IVI?
- #4 GEN (GENeral) & IVI (In Vehicle Infotainment) 2009 : Continental launches AutoLinQ – open platform leveraging Android OS 2012: Continental readies GENIVI multimedia head unit 2014: Open Infotainment Platform (Platform and products are available)
- #5 Simon Sinek credinte, crez comportament, proces, ce face diferenta ce produs, rezultat, serviciu
- #7 It’s a community
- #9 Consumer Electronic
- #10 Ce este o arhitectura deschisa? (open architecture) Una neterminata Open architecture is a type of computer architecture or software architecture that is designed to make adding, upgrading and swapping components easy.
- #11 Intrebare ptr premiu: Cand e un PC 100% sigur? Un PC 100% sigur este cand… e inchis
- #12 BMW, Munich – orasul cu administratie 100% open source
- #14 The majority of GENIVI’s work is conducted through the technical and marketing teams and groups. There are currently six topical “expert groups” – Automotive, CE Connectivity, Location-based Services, Media and Graphics, Networking, and System Infrastructure. The GENIVI compliance program is a key deliverable of the alliance, providing a specification for GENIVI member companies to measure their products. Those that meet the specification may be registered as GENIVI Compliant® and listed on the GENIVI website. Compliant platforms consist of Linux-based core services, middleware, and open application layer interfaces. These are the essential but non-differentiating core elements of the overall IVI solution set.
- #15 GNU General Public License (o licenta virala), LGPL, MIT - Using GPL V3 licensed code in devices in the car therefore requires that users are enabled to install modified software on them. Since the implications to liability and safety have not been fully evaluated - Munchen & BMW Community & Companies Agreements with customer about each component from Genivi Special workshops where architects and community representatives define interfaces (changes) Boot loader, lifecycle-ul din automotive are mai multe stari (un automat finit determinist cu mai multe stari) ex: vorbesti la telefon, opresti motorul, scoti cheia, ai iesit din masina Comunitatea OS a aparut ca o dorinta de a avea o alternativa la produsele comerciale, mai ales aplicatiile cele mai uzuale
- #16 Pentru fiecare arie functionala importanta (Expert Group) Magistrala de comunicare intre aplicatii si intre kernel si aplicatii (cu impact in lifecycle) Aplicatiile OS se pot inlocui cu alte aplicatii (vezi GPL, LGPL)
- #17 EGs drive the content, SAT coordinates and approves this work, BIT validates by building a Baseline EGs are primarily organized by functional domain, but also by region Members can implement compliance specification and apply for compliance certification; SAT reviews, provides comments and approves There are other groups not shown here including Project Management Organization (PMO), Board of Directors, Marketing Council and their sub-teams
- #19 The Digital Living Network Alliance (DLNA) is a nonprofit collaborative trade organization established by Sony in June 2003, that is responsible for defining interoperability guidelines to enable sharing of digital media between multimedia devices.
- #20 The Digital Living Network Alliance (DLNA) is a nonprofit collaborative trade organization established by Sony in June 2003, that is responsible for defining interoperability guidelines to enable sharing of digital media between multimedia devices.
- #21 D-Bus is a message bus system, a simple way for applications to talk to one another. In addition to inter-process communication, D-Bus helps coordinate process lifecycle; it makes it simple and reliable to code a "single instance" application or daemon, and to launch applications and daemons on demand when their services are needed. D-Bus supplies both a system daemon (for events such as "new hardware device added" or "printer queue changed") and a per-user-login-session daemon (for general IPC needs among user applications). Also, the message bus is built on top of a general one-to-one message passing framework, which can be used by any two apps to communicate directly (without going through the message bus daemon). Currently the communicating applications are on one computer, or through unencrypted TCP/IP suitable for use behind a firewall with shared NFS home directories. (Help wanted with better remote transports - the transport mechanism is well-abstracted and extensible.) Interceptor pattern
- #22 // A simple program that uses LoadLibrary and // GetProcAddress to access myPuts from Myputs.dll. #include <windows.h> #include <stdio.h> typedef int (__cdecl *MYPROC)(LPWSTR); int main( void ) { HINSTANCE hinstLib; MYPROC ProcAdd; BOOL fFreeResult, fRunTimeLinkSuccess = FALSE; // Get a handle to the DLL module. hinstLib = LoadLibrary(TEXT("MyPuts.dll")); // If the handle is valid, try to get the function address. if (hinstLib != NULL) { ProcAdd = (MYPROC) GetProcAddress(hinstLib, "myPuts"); // If the function address is valid, call the function. if (NULL != ProcAdd) { fRunTimeLinkSuccess = TRUE; (ProcAdd) (L"Message sent to the DLL function "); } // Free the DLL module. fFreeResult = FreeLibrary(hinstLib); } // If unable to call the DLL function, use an alternative. if (! fRunTimeLinkSuccess) printf("Message printed from executable "); return 0; }
- #23 It’s a community