V4L2 Open Source Projects: Looking for Volunteers: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
This page lists open source projects related to the V4L2 subsystem that are in need of volunteers. |
This page lists open source projects related to the V4L2 subsystem that are in need of volunteers. |
||
Each project has a short description and an indication of the difficulty and guesstimated time in days (assume around 7-8 hours per day). Projects marked ' |
Each project has a short description and an indication of the difficulty and guesstimated time in days (assume around 7-8 hours per day). Projects marked 'Easy' are suitable for those with little experience with C and kernel development. Projects marked 'Medium' require C experience and at least some knowledge about kernel driver development. Projects marked 'Hard' require a solid amount of kernel development experience and ideally at least some knowledge about media subsystem development. |
||
If you are interested in one of these projects, then please contact the linux-media mailinglist. |
If you are interested in one of these projects, then please contact the linux-media mailinglist. |
||
Line 9: | Line 9: | ||
* VIMC: Add S-Video emulation support. The vimc (Virtual Media Controller) driver supports sensors, but it does not have a sub-device driver for S-Video receivers. It would be nice to have this for prototyping purposes. Difficulty: medium. Time: 10 days. |
* VIMC: Add S-Video emulation support. The vimc (Virtual Media Controller) driver supports sensors, but it does not have a sub-device driver for S-Video receivers. It would be nice to have this for prototyping purposes. Difficulty: medium. Time: 10 days. |
||
* VIMC: Add frame rate control. The vimc (Virtual Media Controller) driver support different frame resolutions, but it does not support different frame rates. Add support for this. Difficulty: |
* VIMC: Add frame rate control. The vimc (Virtual Media Controller) driver support different frame resolutions, but it does not support different frame rates. Add support for this. Difficulty: Easy/Medium. Time: 5 days. |
||
* VIMC: Add support for cropping/composing. The vimc (Virtual Media Controller) driver does not have any support for the cropping and composing API (aka selection API). Add support for this. Difficulty: Medium. Time: 10-15 days. |
* VIMC: Add support for cropping/composing. The vimc (Virtual Media Controller) driver does not have any support for the cropping and composing API (aka selection API). Add support for this. Difficulty: Medium. Time: 10-15 days. |
||
* V4L2 Documentation: the [https://www.linuxtv.org/downloads/v4l-dvb-apis-new/uapi/v4l/extended-controls.html Extended Controls] documentation should be split up into sub-sections, one for each class of controls. |
* V4L2 Documentation: the [https://www.linuxtv.org/downloads/v4l-dvb-apis-new/uapi/v4l/extended-controls.html Extended Controls] documentation should be split up into sub-sections, one for each class of controls. Difficulty: Easy. Time: 1 day. |
||
* V4L2 Documentation: re-organize the [https://www.linuxtv.org/downloads/v4l-dvb-apis-new/uapi/v4l/vidioc-g-selection.html Selection] API documentation. It's messy and the information is spread over too many pages. Difficulty: Easy/Medium. Time: 2-4 days. |
Revision as of 07:32, 30 March 2018
This page lists open source projects related to the V4L2 subsystem that are in need of volunteers.
Each project has a short description and an indication of the difficulty and guesstimated time in days (assume around 7-8 hours per day). Projects marked 'Easy' are suitable for those with little experience with C and kernel development. Projects marked 'Medium' require C experience and at least some knowledge about kernel driver development. Projects marked 'Hard' require a solid amount of kernel development experience and ideally at least some knowledge about media subsystem development.
If you are interested in one of these projects, then please contact the linux-media mailinglist.
- VIMC: Add HDMI emulation support. The vimc (Virtual Media Controller) driver supports sensors, but it does not have a sub-device driver for HDMI receivers. It would be nice to have this for prototyping purposes. Difficulty: medium. Time: 10 days.
- VIMC: Add S-Video emulation support. The vimc (Virtual Media Controller) driver supports sensors, but it does not have a sub-device driver for S-Video receivers. It would be nice to have this for prototyping purposes. Difficulty: medium. Time: 10 days.
- VIMC: Add frame rate control. The vimc (Virtual Media Controller) driver support different frame resolutions, but it does not support different frame rates. Add support for this. Difficulty: Easy/Medium. Time: 5 days.
- VIMC: Add support for cropping/composing. The vimc (Virtual Media Controller) driver does not have any support for the cropping and composing API (aka selection API). Add support for this. Difficulty: Medium. Time: 10-15 days.
- V4L2 Documentation: the Extended Controls documentation should be split up into sub-sections, one for each class of controls. Difficulty: Easy. Time: 1 day.
- V4L2 Documentation: re-organize the Selection API documentation. It's messy and the information is spread over too many pages. Difficulty: Easy/Medium. Time: 2-4 days.