gsoc:2018-gsoc-agl
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
gsoc:2018-gsoc-agl [2018/01/29 11:30] jsmoeller |
gsoc:2018-gsoc-agl [2018/01/29 22:02] (current) jsmoeller |
||
|---|---|---|---|
| Line 17: | Line 17: | ||
| Git - gerrit.automotivelinux.org | Git - gerrit.automotivelinux.org | ||
| - | Mailing Lists - http://lists.linuxfoundation.org.org/mailman/listinfo/automotive-discussions | + | Mailing Lists - http://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions |
| IRC channel - #automotive on freenode | IRC channel - #automotive on freenode | ||
| Line 41: | Line 41: | ||
| * Task #2: Middleware and Application development | * Task #2: Middleware and Application development | ||
| * Automotive Grade Linux us a whole platform abstracting the hardware layer from the application layer by a middleware. This middleware framework handles access rights and security as well as the abstraction of the specific hardware from the upper layers. | * Automotive Grade Linux us a whole platform abstracting the hardware layer from the application layer by a middleware. This middleware framework handles access rights and security as well as the abstraction of the specific hardware from the upper layers. | ||
| - | * Your task will be to write a full stack example application from driver abstraction (low-level API) to middleware (high-level API) to Application. Example is a laser-scanner frontend UI which gathers the sensor over the high-level API and displays the data gathered from the lower layers in an intuitive UI. | + | * Your task will be to write a full stack example application from driver abstraction (low-level API) to middleware (high-level API) to Application. Example is a laser-scanner frontend UI which gathers the sensor over the high-level API and displays the data gathered from the lower layers in an intuitive UI. Your work should also be demonstrated during a conference. |
| * Mentors: Jan-Simon Möller, AGL Release Manager + TBD | * Mentors: Jan-Simon Möller, AGL Release Manager + TBD | ||
| * Desired Knowledge: C/C++, QML | * Desired Knowledge: C/C++, QML | ||
| Line 50: | Line 50: | ||
| * Task #3: Platform Development | * Task #3: Platform Development | ||
| * Realtime capabilities are an important part of the requirements of automotive systems. One approach is to partition your CPU using a partitioning hypervisor and run an independent RTOS with the time-sensitive code. | * Realtime capabilities are an important part of the requirements of automotive systems. One approach is to partition your CPU using a partitioning hypervisor and run an independent RTOS with the time-sensitive code. | ||
| - | * Your task will be to port the partitioning hypervisor 'jailhouse' to an AGL reference platform (e.g. Minnowboard) and demonstrate that the 'zephyr' rtos can be a running in a 'cell'. Extra kudos for writing an extension to zephyr to communicate with AGL middleware over websocket. | + | * Your task will be to port the partitioning hypervisor 'jailhouse' to an AGL reference platform (e.g. Minnowboard) and demonstrate that the 'zephyr' rtos can be a running in a 'cell'. You should also write an extension to zephyr to communicate with AGL middleware over websocket. Your work should also be demonstrated during a conference. |
| * Mentors: Jan-Simon Möller, AGL Release Manager + TBD | * Mentors: Jan-Simon Möller, AGL Release Manager + TBD | ||
| * Desired Knowledge: C/C++, realtime, RTOS, zephyr | * Desired Knowledge: C/C++, realtime, RTOS, zephyr | ||
gsoc/2018-gsoc-agl.1517225405.txt.gz · Last modified: 2018/01/29 11:30 by jsmoeller
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
