From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Rafael Costa dos Santos <rafael@thinkfreak.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Module Programming
Date: Tue, 5 Aug 2003 08:14:46 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0308050808350.4731@chaos> (raw)
In-Reply-To: <200308050838.49544.rafael@thinkfreak.com.br>
On Tue, 5 Aug 2003, Rafael Costa dos Santos wrote:
> Where can I follow the modifications under the main functions of linux kernel
> programming between versions of kernerl?
>
> I am asking that because I have some work on that area and I want it to be
> portable to every kernel versions.
>
Well you can't be "portable to every kernel version", but you
can design your modules so that they will compile and run on
every version that supports modules.
The easiest thing is to try to compile your module, designed for
an older version, using a newer version of kernel headers. You
can then "fix" things that don't compile. You fix them inside
some compiler conditionals so they are not "fixed", hense broken,
for previous versions.
If you have a lot of modules, then you probably should make a
'configure' program or script that sets the proper conditionals
in some dynamic header file, based upon the kernel version.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
prev parent reply other threads:[~2003-08-05 12:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 8:38 Rafael Costa dos Santos
2003-08-05 12:00 ` Tommy Reynolds
2003-08-05 12:14 ` Richard B. Johnson [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.53.0308050808350.4731@chaos \
--to=root@chaos.analogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@thinkfreak.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®