From: Peter Samuelson <peter@cadcamlab.org>
To: Jamie Manley <jamie@homebrewcomputing.com>
Cc: John Levon <moz@compsoc.man.ac.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.2.18pre24 and drm/agpgart static?
Date: Fri, 1 Dec 2000 21:22:22 -0600 [thread overview]
Message-ID: <20001201212222.D25464@wire.cadcamlab.org> (raw)
In-Reply-To: <20001129203752.A15218@homebrewcomputing.com> <Pine.LNX.4.21.0012011450270.1317-100000@mrworry.compsoc.man.ac.uk> <20001201175153.B11780@homebrewcomputing.com>
In-Reply-To: <20001201175153.B11780@homebrewcomputing.com>; from jamie@homebrewcomputing.com on Fri, Dec 01, 2000 at 05:51:53PM -0800
[Jamie Manley]
> Yes, modversions was enabled. Should that be affecting the build of
> the kernel proper?
The bug you ran into is that MODVERSIONS messes up the
'get_module_symbol' function, which is a sort of "optional dependency"
mechanism used by a few modules such as DRI (in this case: DRI needs to
be able to use the facilities of agpgart, but should also work
*without* agpgart present, since many systems have PCI video cards).
MODVERSIONS is ugly and gross for any number of reasons, but the
get_module_symbol problem is quite localized -- AGP/DRI, MTD and maybe
one or two other subsystems. In any case it has been replaced by a
much better inter-module registration system in 2.4.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-02 3:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 4:37 2.2.18pre24 and drm/agpgart static? Jamie Manley
2000-12-01 14:52 ` John Levon
2000-12-01 22:59 ` Keith Owens
2000-12-02 1:51 ` Jamie Manley
2000-12-02 3:22 ` Peter Samuelson [this message]
2000-12-02 4:18 ` Jamie Manley
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=20001201212222.D25464@wire.cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=jamie@homebrewcomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moz@compsoc.man.ac.uk \
/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