From: Matthias Schniedermeyer <ms@citd.de>
To: Jaswinder Singh <jaswinderrajput@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Support 2.4 modules features in 2.6
Date: Wed, 13 Dec 2006 00:51:23 +0100 [thread overview]
Message-ID: <457F407B.4030602@citd.de> (raw)
In-Reply-To: <aa5953d60612120606g8c59542seaa440b7b0404ff5@mail.gmail.com>
Jaswinder Singh wrote:
> Hello,
>
> I want to support old 2.4 modules features in 2.6 kernel modules:-
> 1. no kernel source tree is required to build modules.
I don't think that is possible.
There are a few "questions" that are quite fundamental when you want to
build a module that can be loaded by a given kernel.
About the most important fundamental "questions" i can think of ATM:
- UP/SMP
- Preempt yes/no
- RegParm yes/no
(x86)- High Memory off/4g/64G(IOW PAE yes/no)
And maybe a few more "not so fundamental" points.
AFAIK there is no way to build a module that would work in all of the
8/16 possible "kernel-types" you get with these 3/4 fundamental options
alone.
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
next prev parent reply other threads:[~2006-12-13 0:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 14:06 Support 2.4 modules features in 2.6 Jaswinder Singh
2006-12-12 14:11 ` Arjan van de Ven
2006-12-12 15:11 ` Jaswinder Singh
2006-12-12 15:37 ` Arjan van de Ven
2006-12-12 16:48 ` Jaswinder Singh
2006-12-13 8:06 ` Arjan van de Ven
2006-12-12 23:51 ` Matthias Schniedermeyer [this message]
[not found] <fa.49G5lweS8py4hisexsfl1zRqB3Y@ifi.uio.no>
[not found] ` <fa.o58YYFf0KmJCYaGfzWFQYvWvWqw@ifi.uio.no>
[not found] ` <fa.LL4m3y1d6ywMNgGlDl6zW5gCaRA@ifi.uio.no>
[not found] ` <fa.uN/dXUaQFfxu97P18c1QPZodm1A@ifi.uio.no>
[not found] ` <fa.eHbXg8xrK/U8MrbcE6JMfwHCb1k@ifi.uio.no>
2006-12-12 23:31 ` Robert Hancock
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=457F407B.4030602@citd.de \
--to=ms@citd.de \
--cc=jaswinderrajput@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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