Re: protecting source code in 2.6

From: Matthias Andree (matthias.andree_at_gmx.de)
Date: 05/21/04

  • Next message: Andi Kleen: "Re: [PATCH][2.6-mm] Make i386 boot not so chatty" 
    Date:	Fri, 21 May 2004 10:29:49 +0200
To: linux-kernel@vger.kernel.org, "Surendra I." <surendrai@esntechnologies.co.in>

    On Thu, 20 May 2004, Jinu M. wrote:

    > The device interface module is proprietary source and we don't intend
    > to distribute it with source code on GPL license.

    Why is there a reason to lock down the source of the actual driver?

    Can we assume the hardware is so cheap that all the smartness is in the
    software? Why would anyone buy the hardware then? What performance could
    we expect?

    What kind of device is yours that users would not have an alternative to
    buy something with open-source driver that has the same function?

    Plus, are you committing to:

    - compile and re-compile (after kernel changes) your module over and
      over again, to keep it working?

    - provide the module for any platform that accepts the hardware
      (ix86, AMD64, PowerPC, sparc, sparc64, ...)

    - guarantee the users of your hardware a support period, say, three years
      at least, during which you will continue to provide updated binary
      modules, if need be, for particular distributions?

    - support and pre-filter all bug reports, whether the problem originates
      in your closed source driver

    - why are _you_ trying to profit from open source without contributing
      back?

    - the next item I cannot conceive right now but someone will bring up?

    I wonder why anyone would be motivated to help, for free, with a
    closed-source driver.

    The situation for you will likely change completely should you decide to
    open-source the driver - vendors who have chosen that path have usually
    received support, often their drivers have ultimately become part of the
    kernel, so the users won't have to go search for the driver themselves,
    hassling with nonstandard installation procedures and all that, and your
    visibility in hardware data bases may help the sales of your hardware. 

    -- 
Matthias Andree
Encrypted mail welcome: my GnuPG key ID is 0x052E7D95
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
  • Next message: Andi Kleen: "Re: [PATCH][2.6-mm] Make i386 boot not so chatty"

    Relevant Pages

    • [opensuse] openSUSE 10.3 not detecting SATA HD
      ... the sata_sis driver. ... I've tried turning off ACPI in bios and acpi=off which ... openSUSE 10.2 and all my hardware is working fine. ... info.product = 'USB Raw Device Access' ...
      (SuSE)
    • Re: [PATCH] tracing/ftrace: stop {irqs,preempt}soff tracers when tracing is stopped
      ... Hardware name: System Product Name ... # IPVS transport protocol load balancing support ... # AX.25 network device drivers ... # Generic Driver Options ...
      (Linux-Kernel)
    • Re: Binary Drivers
      ... "Thank you for requesting a driver to support our hardware on ... Linux market is not big enough to justify the work, ...
      (Linux-Kernel)
    • Re: DVI output, ATI or nVidia
      ... complaining that a vendor refuses to give full documentation for a piece ... of hardware do its work a mater of trace secrets. ... were no OSS 3d driver. ... Support for operating systems not supported by NVidia (any PowerPC ...
      (Fedora)
    • Re: 2008 SBS no longer boots
      ... driver issue initially, the fact that it seems to happen randomly now ... weird with a hardware problem that consistently doesn't get through boot ... other customer, even a 2 week old one, the problem immediately returned. ... There was a time when a server was fired up with a specialized OS and had a battery of tests run against each component to purposefully stress it. ...
      (microsoft.public.windows.server.sbs)