Re: protecting source code in 2.6

From: Bartlomiej Zolnierkiewicz (B.Zolnierkiewicz_at_elka.pw.edu.pl)
Date: 05/20/04

  • Next message: John Bradford: "Re: protecting source code in 2.6"
    To: "Jinu M." <jinum@esntechnologies.co.in>, <linux-kernel@vger.kernel.org>
    Date:	Thu, 20 May 2004 16:05:34 +0200
    
    

    On Thursday 20 of May 2004 15:18, Jinu M. wrote:
    > Hi All,

    Hi,

    > We are developing a block device driver on linux-2.6.x kernel. We want
    > to distribute our driver as sum of source code and librabry/object code.
    >
    > We have divided the source code into two parts. The os interface module
    > and the device interface module. The os interface module (osint.c) has
    > all the os interface functions (init, exit, open, close, ioctl, request
    > queue handling etc). The device interface module (devint.c) on the other
    > hand has all the device interface functions (initialize device, read,
    > write etc), these don't use system calls or kernel APIs.
    >
    > The device interface module is proprietary source and we don't intend
    > to distribute it with source code on GPL license.

    You may want to reconsider your decision.

    - by providing non-GPL driver your driver is very likely
      to not work with future kernel versions due to the fact that
      Linux driver API is not stable (it changes *very* frequently)

    - nobody is going to provide support for kernels with your driver
      loaded - you have to deal with bugreports about *all* Linux kernel
      issues from users of your driver

    > What we intend to do is, distribute the os interface module (osint.c)
    > with
    > source code and the device interface module as object code or library.
    > The
    > user will compile the os interface module on the target box and link it
    > with the device interface module to generate the .ko (loadable module).
    >
    > We are not very sure of how to achieve this.
    > Please help us address this issue.

    Please be aware of the fact that without 'giving source back'
    nobody is going to help you on kernel issues here.

    Kind regards,
    Bartlomiej

    > Thanks in advance,
    > -Jinu

    -
    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: John Bradford: "Re: protecting source code in 2.6"

    Relevant Pages

    • protecting source code in 2.6
      ... We are developing a block device driver on linux-2.6.x kernel. ... We have divided the source code into two parts. ... and the device interface module. ... The device interface module on the other ...
      (Linux-Kernel)
    • protecting source code in 2.6
      ... We are developing a block device driver on linux-2.6.x kernel. ... We have divided the source code into two parts. ... and the device interface module. ... The device interface module on the other ...
      (Linux-Kernel)
    • Re: protecting source code in 2.6
      ... > We are developing a block device driver on linux-2.6.x kernel. ... > to distribute our driver as sum of source code and librabry/object code. ... > and the device interface module. ...
      (Linux-Kernel)
    • Re: protecting source code in 2.6
      ... > to distribute our driver as sum of source code and librabry/object code. ... > and the device interface module. ... The device interface module on the other ...
      (Linux-Kernel)
    • Re: Mirror Driver Architecture
      ... the various VNCs, which do exactly what you are asking, and come with ... we can't use them unless we publish our own source code (this is a commercial ... You are right, of course, any kind of programming in the kernel seems to be ... driver sample code - specifically DrvBitBlt and DrvCopyBits - for sending ...
      (microsoft.public.win32.programmer.kernel)