protecting source code in 2.6

From: Jinu M. (jinum_at_esntechnologies.co.in)
Date: 05/20/04

  • Next message: Raghavan: "Re: [PATCH] dentry and inode cache hash algorithm performance changes." 
    Date:	Thu, 20 May 2004 18:51:17 +0530
To: <linux-kernel@vger.kernel.org>

    Hi All,

    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.

    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.

    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: Raghavan: "Re: [PATCH] dentry and inode cache hash algorithm performance changes."

    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)
    • 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: 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: 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
      ... > source code and the device interface module as object code or library. ... You just need to distribute it as an external module, ... Where KERNELSRC is a kernel with 'make module_prepare' executed. ...
      (Linux-Kernel)