From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Arjan van de Ven <arjan@infradead.org>, adaplas@pol.net
Cc: linux-fbdev-devel@lists.sourceforge.net,
Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@osdl.org>,
Dave Jones <davej@redhat.com>,
Sylvain Meyer <sylvain.meyer@worldonline.fr>,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-fbdev-devel] Re: 2.6.10-rc1-mm2: intelfb/AGP unknown symbols
Date: Sat, 30 Oct 2004 21:08:32 +0800 [thread overview]
Message-ID: <200410302108.32872.adaplas@hotpop.com> (raw)
In-Reply-To: <1099136087.3883.0.camel@laptop.fenrus.org>
On Saturday 30 October 2004 19:34, Arjan van de Ven wrote:
> > What's wrong with exporting the symbols back again?
>
> if they are the right api to use; nothing. If they aren't (and what you
> describe somehow suggests they aren't) it sounds better to make the
> frontend usable for the intelfb driver instead...
>
I think the functions are the right API to use for clients within the
kernel. The frontend is directed more for userspace clients.
The old interface was to do an inter_module_get/put, but this is to
be deprecated. And all it does is to provide all the backend functions
to the requestor.
Either a new interface is provided by agpgart, otherwise, not just intelfb
and i810fb will be affected, but also DRM (which currently uses
inter_module_get/put("drm_agp")).
If I remember correctly, the DRI people also have a new patch that removes
inter_module_get/put and they did it by calling the backend functions directly.
Tony
next prev parent reply other threads:[~2004-10-30 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041029014930.21ed5b9a.akpm@osdl.org>
2004-10-30 3:24 ` 2.6.10-rc1-mm2: intelfb/AGP unknown symbols Adrian Bunk
2004-10-30 8:28 ` Arjan van de Ven
2004-10-30 11:21 ` Antonino A. Daplas
2004-10-30 11:34 ` [Linux-fbdev-devel] " Arjan van de Ven
2004-10-30 13:08 ` Antonino A. Daplas [this message]
2004-10-30 15:16 ` Christoph Hellwig
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=200410302108.32872.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=bunk@stusta.de \
--cc=davej@redhat.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sylvain.meyer@worldonline.fr \
/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;
as well as URLs for NNTP newsgroup(s).