From: Dave Airlie <airlied@linux.ie>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: dri-devel@lists.sf.net, linux-kernel@vger.kernel.org
Subject: Re: [RFC] [patch] drm core internal versioning..
Date: Sun, 10 Oct 2004 03:31:26 +0100 (IST) [thread overview]
Message-ID: <Pine.LNX.4.58.0410100328080.11219@skynet> (raw)
In-Reply-To: <9e47339104100917527993026d@mail.gmail.com>
> How strong of match requirement do we need? Note that this only
> impacts distribution of binary personality modules, if you have source
> there is no problem.
Not really I'm thinking more of someone building a module against one core
and insmodding it against another one.. so someone builds a kernel with
core/personality, then builds just a personality module from CVS and tries
to use it with the kernel core one...
personally I think binary distributors have the money to keep up with the
kernel releases....
I don't want to re-implement kernel modversions which is what we are close
to doing, you can't insmod a module built against a different kernel
anyways so it doesn't matter, kernel version, preempt, smp, compiler are
all checked on insmod in 2.6 if they don't match it doesn't load it is not
possible to distrib a binarry kernel independent module.. without at least
a portable stub source loader...
Dave.
--
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
pam_smb / Linux DECstation / Linux VAX / ILUG person
next prev parent reply other threads:[~2004-10-10 2:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-09 23:54 Dave Airlie
2004-10-10 0:52 ` Jon Smirl
2004-10-10 2:31 ` Dave Airlie [this message]
2004-10-10 4:29 ` Greg KH
2004-10-10 5:30 ` Dave Airlie
2004-10-10 6:44 ` Arjan van de Ven
2004-10-10 7:00 ` Dave Airlie
2004-10-12 1:46 ` Ian Romanick
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.58.0410100328080.11219@skynet \
--to=airlied@linux.ie \
--cc=dri-devel@lists.sf.net \
--cc=jonsmirl@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
all inboxes | Powered by JetHome®