Merging device drivers to LK tree

alexhoppus alexhoppus111 at gmail.com
Tue Mar 14 15:54:37 EDT 2017


On 14.03.2017 00:45, Greg KH wrote:
> On Mon, Mar 13, 2017 at 11:21:24PM +0300, alexhoppus wrote:
>> Hello!
>>
>> I have several questions regarding how device drivers are merged into
>> linux-kernel. First of all, I have found some document regarding
>> submitting drivers to LK, but it  looks like pretty out-dated,
>> https://kernelnewbies.org/UpstreamMerge/SubmittingDrivers
>> is this info still relevant? Or there is a new one?
>
> Look in the kernel source tree at Documentation/SubmittingDrivers for
> the latest version.
>
>> Actually, I want to know more about the process. To start with this, I
>> would like to ask an example question. Surfing through the kernel source
>> I have found several ra-link usb wi-fi adapter drivers (rtl8188eu,
>> rtl8192e, rtl8712 ...). Suppose one have datasheet that gives the
>> possibility for writing a device driver for say rtlxxxxx based device.
>> Can third-party person write & submit this driver to LK or this must be
>> done explicitly by device vendor?
>
> Anyone can submit a driver.
>
>> What are the requirements from LK community side?
>
> It has to match our coding style rules and pass our code review.
>
>> Are there any license issues with this? (besides the author should
>> publish code under GPL)
>
> Nope, just has to be compatible with GPLv2.
>
> Do you have a specific driver you wish to get merged that isn't already
> in the tree?

No, I just try to understand the process. I don't fully understand what 
is the role of independent developer in the process of submitting new 
drivers to LK. What I mean is - hardware device vendors always ship 
device driver with their products. In this case several options are 
available:
1.) HW vendor ships only closed-source drivers and is not interested to 
open source this work.
2.) HW vendor publishes device drivers to the community by himself
3.) HW vendor put the device driver sources to their website ready for 
downloading and building, but make no effort for integrating them to LK.

Actually, I see that in this plot independent developer could only 
participate in case 3 - i.e. take the published sources, fix coding 
style, satisfy other community needs and integrate this driver to LK 
(By the way is this a real case? Or drivers aren't integrated in such 
way?). I see no other ways how independent person could participate. Am 
I wrong?

>
> thanks,
>
> greg k-h
>




More information about the Kernelnewbies mailing list