LKML Archive on
help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <>
To: "Jinu M." <>, <>
Cc: <>,
	"Surendra I." <>
Subject: Re: protecting source code in 2.6
Date: Thu, 20 May 2004 16:05:34 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thursday 20 of May 2004 15:18, 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.

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,

> Thanks in advance,
> -Jinu

  parent reply	other threads:[~2004-05-20 14:04 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 [this message]
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
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).