RidgeRun Linux Camera Drivers - Available Camera Drivers - Custom Driver Development

From RidgeRun Developer Wiki
Revision as of 13:53, 30 September 2024 by Ofallas (talk | contribs) (→‎Hiring Process)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)





Need a driver not listed? RidgeRun can help!

RidgeRun has broad experience in the development of kernel drivers, if the driver you are looking for is not on the list, it is most likely because we haven't received a request for it yet, but we can develop the new driver for you.

Since 2006, RidgeRun has specialized in developing custom Linux V4L2 drivers for embedded systems. Our process begins with the customer's selection of a hardware sensor or chip, followed by our creation of a tailored V4L2 driver. This service encompasses the essential steps for implementing a V4L2 capture driver for your system, assuming no hardware complications. Each package includes support for one camera at a specific resolution, with options to integrate additional configurations through our engineering services.

Hiring Process

Image describing how to hire RidgeRun services
Hiring process followed by the RidgeRun team


1. Contact RidgeRun: Provide the details of your project to see how RidgeRun can help you with your project.

Note
RidgeRun contact details are provided in the Contact Us section at the end of this wiki for requesting a new driver development.

2. NDA: Provide NDA if needed.

3. Statement of Work: Once you and RidgeRun have verified that the project is a good match, the customer will provide a Statement of Work or similar documentation.

4. Task List: RidgeRun then creates task list and provides rough estimate for it. The customer will then have a call with RidgeRun engineers to explain each of the tasks. The effort to complete the task list is Time and Materials (T&M).

5. PO: You can get our minimum PO directly from our Products & Downloads page. For new customers, you need to pre-purchase the professional support hours. Once we have established a working relationship, RidgeRun bills at the end of each month for the services provided.

6. Hardware: Once the PO is set up, you can send hardware to the RidgeRun R&D Lab, if needed. RidgeRun has access to several EVM boards that could be used for your project. Hardware is sent back once RidgeRun is done with the project.

7. Weekly Call & Start Date: Next, we will schedule a weekly call and start date. During the weekly call the customer will be informed about partial deliveries to verify that the work that RidgeRun is doing is accurate and meet their needs.

8. Ongoing Service: At the end of the month, a report generated by our hour tracking system is provided. You will be notified when your project reaches 95% of the approved budget, at which point you may decide how to proceed according to the existing task list.

Important
Engineering Support Hours Note: Engineering Support Hours not used 6 months after the first support is provided will expire.