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 16:41:39 +0100 [thread overview]
Message-ID: <20050202154139.GA3267@s> (raw)
In-Reply-To: <1107357093.6191.53.camel@gonzales>
[Xavier Bestel]
> Le mercredi 02 février 2005 à 15:21 +0100, Haakon Riiser a
> écrit :
>> How can I use a frame buffer driver's optimized copyarea,
>> fillrect, blit, etc. from userspace? The only way I've ever
>> seen anyone use the frame buffer device is by mmap()ing it
>> and doing everything manually in the mapped memory. I assume
>> there must be ioctls for accessing the accelerated functions,
>> but after several hours of grepping and googling, I give up. :-(
> Did you try DirectFB ?
Thanks for the tip, I hadn't heard about it. I will take a look,
but only to see if it can show me the user space API of /dev/fb.
I don't need a general library that supports a bunch of different
graphics cards. I'm writing my own frame buffer driver for the
GX2 CPU, and I just want to know how to call the various functions
registered in struct fb_ops, so that I can test my code. I mean,
all those functions registered in fb_ops must be accessible
somehow; if they weren't, what purpose would they serve?
--
Haakon
next prev parent reply other threads:[~2005-02-02 15:42 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 [this message]
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
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=20050202154139.GA3267@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