From: Dave Airlie <airlied@gmail.com>
To: Yuri Vilmanis <vilmanis@internode.on.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: EXPORT_SYMBOL_GPL for __symbol_get replacing EXPORT_SYMBOL for deprecated inter_module_get
Date: Wed, 13 Apr 2005 23:34:39 +1000 [thread overview]
Message-ID: <21d7e997050413063441d83f49@mail.gmail.com> (raw)
In-Reply-To: <200504131855.00806.vilmanis@internode.on.net>
> The case in point for me is ATI's binary openGL accelerated drivers (fglrx) -
> these used inter_module_get() to communicate with the agp gart module, for
> obvious reasons - this AGP communication is essential to the functionality of
> the driver. No, I don't like ATI only having closed-source drivers any more
> than you, but given the extremely competetive nature of high end video card
> sales, I can see why they want to do it this way. The point is that now, as
> of 2.6.11-? or 2.6.12-? (not sure of the exact revision), the
> inter_module_get() functions has been removed, and the functionality can only
> be got (as far as I can tell) through use of the symbol_get() function.
>
you might have done some research on what happened before ranting away
like a crazy.....
AGP dropped the drm_agp interface in favour of the DRM modules calling
the AGP backend directly, a patch for the ATI drivers has been sailing
around for ages I even wrote one myself for someone I think but I've
lost it now ... all the AGP symbols needed are exported with
EXPORT_SYMBOL.
you might have noticed no-one else complaining around here which is
usually a good sign that there is nothing worth complaining about :-)
Dave.
next prev parent reply other threads:[~2005-04-13 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 9:25 EXPORT_SYMBOL_GPL for __symbol_get replacing EXPORT_SYMBOL for deprecated inter_module_get Yuri Vilmanis
2005-04-13 9:56 ` Arjan van de Ven
2005-04-13 13:34 ` Dave Airlie [this message]
2005-04-13 14:54 ` Dave Jones
2005-04-13 15:57 ` Richard B. Johnson
2005-04-13 16:01 ` Sean
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=21d7e997050413063441d83f49@mail.gmail.com \
--to=airlied@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vilmanis@internode.on.net \
/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