From: Haakon Riiser <haakon.riiser@fys.uio.no>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Accelerated frame buffer functions
Date: Wed, 2 Feb 2005 21:08:10 +0100 [thread overview]
Message-ID: <20050202200810.GA2100@s> (raw)
In-Reply-To: <Pine.GSO.4.61.0502022037440.2069@waterleaf.sonytel.be>
[Geert Uytterhoeven]
> mmap() the MMIO registers to userspace, and program the
> acceleration engine from userspace, like DirectFB (and XF*_FBDev
> 3.x for Matrox and Mach64) does.
Right, this was how I originally intended to do it. The reason
why I started to obsess about the accelerated fb_ops functions was
that I hoped that, by creating a driver that registered accelerated
versions of these functions, other frame buffer-using applications
would instantly take advantage of it, requiring no changes in those
applications. I thought the frame buffer device was supposed to
serve as an an abstraction layer between the graphics card and
the application, allowing for 2D acceleration without having to
know anything about the underlying hardware. But if no one uses the
frame buffer device in this way, I might as well do as you suggest
and mmap() the registers to userspace.
Anyway, thanks to everyone who participated in this thread. Even if
I didn't get the answers I was hoping for, at least now I can put the
matter to rest.
--
Haakon
next prev parent reply other threads:[~2005-02-02 20:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 13:31 Accelerated frame buffer functions Haakon Riiser
2005-02-02 14:04 ` linux-os
2005-02-02 14:21 ` Haakon Riiser
2005-02-02 15:11 ` Xavier Bestel
2005-02-02 15:41 ` Haakon Riiser
2005-02-02 16:25 ` Jon Smirl
2005-02-02 17:45 ` Haakon Riiser
2005-02-02 19:35 ` James Simmons
2005-02-02 19:38 ` Geert Uytterhoeven
2005-02-02 20:08 ` Haakon Riiser [this message]
2005-02-03 8:36 ` Helge Hafting
2005-02-02 19:31 ` James Simmons
2005-02-02 15:50 ` Gábor Lénárt
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=20050202200810.GA2100@s \
--to=haakon.riiser@fys.uio.no \
--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