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

On Thu, 20 May 2004, Jinu M. wrote:

> 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.

Kernel-space software that is not open source is a problems source. There
are many example around.

> 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.

It's simple. Just create the devint.o object file for all the supported
architectures multiplied by two or three different gcc revisions
(because of ABI changes, which are arch-dependent). Then the Makefile
has to compile osint.c and link it to the .o . The only difference is
that the Makefile skips the compilation of devint.c .

Out of curiosity, why the driver code must be top secret ?


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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-20 13:21 Jinu M.
2004-05-20 14:08 ` Sam Ravnborg
2004-05-20 14:08 ` Giuliano Pochini [this message]
     [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
  -- strict thread matches above, loose matches on Subject: below --
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

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).