Proposals

Developing Out-of-Tree Drivers alongside In-Kernel Drivers

This proposal has been rejected.

*

One Line Summary

A description of the process, pitfalls and current way that Intel's Wired Ethernet team ships both in-kernel and out-of-tree drivers.

Abstract

Getting your driver released with a GPL license into the kernel is promoted as the holy grail of Linux hardware enabling, and I agree. That said, producing a quality GPL driver for use in the entire Linux ecosystem is not a task for the faint of heart. Releasing an Ethernet driver through kernel.org is one delivery method, but many users still want a driver that will support the latest or newest hardware on older kernels.

To meet our users’ requirements for more than just hardware support in the latest kernel.org kernel, we in Intel’s LAN Access Division (LAD) developed a set of coping strategies, processes, code, tools, and testing methods that are worth sharing. These learnings help us reuse code, maintain quality, and maximize our testing resources in order to get the best quality product in the shortest amount of time to the most customers. While not the most popular topic with core kernel developers, out-of-tree drivers are a necessary business solution for hardware vendors with many users, and this paper describes how we do it. Our Open Source drivers generally work with all kernel releases 2.4 and later, and I’ll explain many of the details about how we get there.

Tags

kernel, intel, drivers, ethernet

Speaker

  • Jessehead

    Biography

    Jesse Brandeburg is a Senior Linux developer in the Intel LAN Access Division, producing the Intel Wired Ethernet products. He has worked on the Linux e100, e1000, e1000e, igb, ixgb, ixgbe linux drivers since 2002. Jesse’s current focus is on performance tuning and bug fixing, as well as helping lead LAD’s linux efforts. Jesse has worked for Intel since 1994.

Leave a private comment to organizers about this proposal