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

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

Not a popolar topic on this mailing list..

>From a technical point of view what you need to do is simple.

You just need to distribute it as an external module, and provide the
dev.o file as part of this.
The dev.o file must be named 'dev.o_shipped'

Then you need a makefile like this:
obj-m := jinu.o
jinu-y := dev.o osinit.o

You can add a few more trick to enable use of plain make - see
article about external modules on the kernel page on a few weeks ago.

What you need to compile the external module is simply:

Where KERNELSRC is a kernel with 'make module_prepare' executed.


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