Slashdot Mirror


Novell Makes Linux Driver Project a Reality

apokryphos writes "Novell have relaunched the Linux Driver Project by dedicating well-known kernel developer Greg KH to work on the project full-time. Greg KH writes: 'My employer, Novell, has modified my position to now allow me to work full time on this project. Namely getting more new Linux kernel drivers written, for free, for any company that so desires. And to help manage all of the developers and project managers who want to help out...They really care about helping make Linux support as many devices as possible, with fully open-source drivers.'"

3 of 200 comments (clear)

  1. Re:Cool by deek · · Score: 5, Informative

    I'm not sure how much just one developer can do, but props to Novell nonetheless.

    Never fear, because he's not doing all the coding himself. According to the link in the article, he's had over 100 volunteers to help him out. If he's good at managing them, then 100 talented coders could certainly make a large impact!
  2. Re:Still not the Right(TM) way by Eivind+Eklund · · Score: 5, Informative
    Having worked both directly with hardware developers (as an embedded systems developer) and with kernel development, this is not quite that clear to me. In some cases, the hardware knowledge side is the most important; in others, the kernel side. Mostly, the kernel side of things is harder to learn than the hardware side, though, so the kernel development skills is the important side. Also, kernel developers often have more experience with working with different kinds of hardware, so they will know how to trick around the particular piece.

    And, importantly: For a LOT of the hardware on the market, what's important is the chipset used, not wiring around it. And the "hardware manufacturer" has often only done the wiring.

    Eivind.

    --
    Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
  3. not the case by free+space · · Score: 5, Informative
    If that is indeed what worries the original poster then he can res assured, from the project's FAQ:

    Q: How are you going to write a GPL driver by signing an NDA? Is it going to require a binary blob or some other way of obfuscating the code?

    A: No, not at all. I have written many drivers after signing NDAs with companies. They are usually signed either to keep information about the device private until it is announced at a specific date, or to just keep the actual specification documents from being released to the public directly. All code created by this NDA program is to be released under the GPL for inclusion in the main kernel tree, nothing will be obfuscated at all.