Re: protecting source code in 2.6

From: Bill Davidsen (davidsen_at_tmr.com)
Date: 05/21/04

  • Next message: Richard B. Johnson: "Re: x86_64 and ioctls from 32 bit userland" 
    Date:	Fri, 21 May 2004 15:49:24 -0400
To: "Jinu M." <jinum@esntechnologies.co.in>

    Jinu M. wrote:
    > 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.

    Thye approved way to do this is to write your own proprietary operating
    system to go with your proprietary driver, then you won't have to
    pretend to be open source. 

    -- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me
-
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: Richard B. Johnson: "Re: x86_64 and ioctls from 32 bit userland"

    Relevant Pages

    • 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)
    • Re: protecting source code in 2.6 (fwd)
      ... protecting source code in 2.6 ... > to distribute our driver as sum of source code and librabry/object code. ... If it executes INSIDE the kernel, i.e., becomes part of a module, ...
      (Linux-Kernel)
    • Re: need proprietary alternative to GPL-licensed functions in linux/drivers/base/class.c
      ... So there's no community linux support either. ... There is no need to make the source code available to the community at ... one driver in the kernel for which only one device exists in the world. ...
      (comp.os.linux.development.system)
    • Re: Need help trying to patch a driver
      ... I haven't a clue how to "patch" a driver. ... certain parts of a particular driver, you'll need the source code for ... If the device driver is one that is built into the kernel, ...
      (Ubuntu)