From: Rusty Russell <rusty@rustcorp.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Christoph Hellwig <hch@infradead.org>,
Jon Smirl <jonsmirl@gmail.com>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: getting rid of inter_module_xx
Date: Mon, 29 Nov 2004 09:06:57 +1100 [thread overview]
Message-ID: <1101679617.25347.17.camel@localhost.localdomain> (raw)
In-Reply-To: <1098635275.24241.7.camel@localhost.localdomain>
On Sun, 2004-10-24 at 17:27 +0100, Alan Cox wrote:
> On Sad, 2004-10-23 at 10:44, Christoph Hellwig wrote:
> > not at all. Everything else in the kernel is compile-time depencies.
> > Just make the agp backend module mandatory if CONFIG_AGP is set, you'll
> > lose tons of complexity at a minimum amount of used memory, and as an
> > added benefit look like the rest of the kernel.
>
> Thats completely stupid
>
> CONFIG_AGP enables the building of AGP modules, it does not disable the
> ability to run that kernel on non AGP setups, or to use non AGP video
> cards.
>
> The relationship is dynamic and you'd need to fix the various drivers
> that support both PCI and AGP mode by compiling them twice so you can
> load them with or without agp support.
>
> Yuck yuck yuck. It would instead be much saner to fix the module loader
> to support weak symbols.
Well, we do support weak symbols, and we also support dynamic symbol
resolution using symbol_get (or symbol_request which probes for the
module if CONFIG_KMOD) and symbol_put.
It's just the inter_module* mechanism which I dislike.
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
prev parent reply other threads:[~2004-11-28 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 17:08 getting rid of inter_module_xx Jon Smirl
2004-10-23 9:44 ` Christoph Hellwig
2004-10-24 16:27 ` Alan Cox
2004-11-28 22:06 ` Rusty Russell [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=1101679617.25347.17.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hch@infradead.org \
--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