From: Keith Owens <kaos@ocs.com.au>
To: davidm@hpl.hp.com
Cc: bgerst@didntduck.org, Terence Ripperda <tripperda@nvidia.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: inter_module_get and __symbol_get
Date: Tue, 25 Jan 2005 09:54:36 +1100 [thread overview]
Message-ID: <31189.1106607276@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Mon, 24 Jan 2005 14:52:06 -0800." <16885.31766.730042.408639@napali.hpl.hp.com>
On Mon, 24 Jan 2005 14:52:06 -0800,
David Mosberger <davidm@napali.hpl.hp.com> wrote:
>>>>>> On Tue, 25 Jan 2005 09:44:18 +1100, Keith Owens <kaos@ocs.com.au> said:
>
> Keith> Does the kernel code really need optional dynamic references
> Keith> between modules or kernel -> modules? That depends on how
> Keith> people code their modules. If the rest of the kernel no
> Keith> longer needs dynamic symbol reference then drop
> Keith> inter_module_* and __symbol_*.
>
>Well, the only place that I know of where I (have to) care about
>inter_module*() is because of the DRM/AGP dependency. I can't imagine
>DRM being overly happy if an AGP device suddenly disappeared, so I
>think static is fine (in fact, probably preferable).
Does DRM support this model?
* Start DRM without AGP.
* AGP is loaded.
* DRM continues but now using AGP.
If yes then it needs dynamic symbol resolution.
next prev parent reply other threads:[~2005-01-25 0:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 21:32 inter_module_get and __symbol_get Terence Ripperda
2005-01-06 21:57 ` Brian Gerst
2005-01-06 22:51 ` Terence Ripperda
2005-01-08 4:00 ` Jon Smirl
2005-01-12 19:37 ` Terence Ripperda
2005-01-12 22:21 ` Brian Gerst
2005-01-08 3:10 ` Keith Owens
2005-01-24 22:36 ` David Mosberger
2005-01-24 22:44 ` Keith Owens
2005-01-24 22:52 ` David Mosberger
2005-01-24 22:54 ` Keith Owens [this message]
2005-01-24 22:58 ` David Mosberger
2005-01-24 23:03 ` Keith Owens
2005-01-25 0:51 ` patch to enable Nvidia v5336 on v2.6.11 kernel (was Re: inter_module_get and __symbol_get) David Mosberger
2005-01-25 12:56 ` J.A. Magallon
2005-01-25 20:50 ` Zephaniah E. Hull
2005-01-26 0:02 ` J.A. Magallon
2005-01-26 0:25 ` Zephaniah E. Hull
2005-01-26 0:25 ` J.A. Magallon
2005-01-25 1:01 ` inter_module_get and __symbol_get Jon Smirl
2005-01-24 23:19 ` Jon Smirl
2005-01-24 23:23 ` David Mosberger
2005-01-25 5:31 ` Terence Ripperda
2005-01-25 5:59 ` Chris Wedgwood
-- strict thread matches above, loose matches on Subject: below --
2005-07-31 4:27 D. ShadowWolf
2005-08-01 1:04 ` Alan Cox
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=31189.1106607276@ocs3.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=bgerst@didntduck.org \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tripperda@nvidia.com \
/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