mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Q: use of new modules in old kernel
Date: Tue, 19 Feb 2002 04:19:52 -0700	[thread overview]
Message-ID: <20020219041952.K24428@lynx.adilger.int> (raw)
In-Reply-To: <20020219090253.CD89D67ED@penelope.materna.de> <1014116037.2019.7.camel@stinky.pussy>
In-Reply-To: <1014116037.2019.7.camel@stinky.pussy>; from NyQuist@ntlworld.com on Tue, Feb 19, 2002 at 10:53:57AM +0000

On Tue, 2002-02-19 at 09:02, Tobias Wollgam wrote:
> how is it possible to use modules of newer kernels in an old kernel 
> system?
> 
> To use new drivers, we want not recompile the kernel.
> 
> I tried to load the module 8139too from 2.4.17 into a 2.4.9 kernel with 
> modprobe, but there are many unresolved symbols. 
> 
> The flag "Set version information on all module symbols" is set.

Note that you will basically never be able to just move the compiled module
from one kernel version to another and expect it to work.  At the very
minimum you should copy the needed files from the new kernel source into
the old kernel source and recompile.  Practically, this may also not work
(depending on the driver and the kernel) because while there is often
backwards compatibility in newer kernels, the newer driver code may not
compile (properly) with the older kernel (it depends on what part of the
kernel the driver is in, though).

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


      reply	other threads:[~2002-02-19 11:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-19  9:02 Tobias Wollgam
2002-02-19 10:53 ` NyQuist
2002-02-19 11:19   ` Andreas Dilger [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=20020219041952.K24428@lynx.adilger.int \
    --to=adilger@turbolabs.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

all inboxes | Powered by JetHome®