LKML Archive on
help / color / mirror / Atom feed
From: Bill Davidsen <>
To: "Jinu M." <>
	"Surendra I." <>
Subject: Re: protecting source code in 2.6
Date: Fri, 21 May 2004 15:49:24 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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 (
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  parent reply	other threads:[~2004-05-21 22:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-20 13:18 Jinu M.
2004-05-20 13:44 ` John Bradford
2004-05-20 14:05 ` Bartlomiej Zolnierkiewicz
2004-05-20 15:43 ` Richard B. Johnson
2004-05-21  8:29 ` Matthias Andree
2004-05-21 16:05 ` Rik van Riel
2004-05-21 19:49 ` Bill Davidsen [this message]
2004-05-20 13:21 Jinu M.
2004-05-20 14:08 ` Sam Ravnborg
2004-05-20 14:08 ` Giuliano Pochini
     [not found] <>
     [not found] ` <>
2004-05-22 14:54   ` Vincent C Jones
2004-05-22 23:24     ` Benjamin Herrenschmidt
2004-05-23  0:56       ` Vincent C Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \
    --subject='Re: protecting source code in 2.6' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).