From: Jon Smirl <jonsmirl@gmail.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Accelerated frame buffer functions
Date: Wed, 2 Feb 2005 11:25:29 -0500 [thread overview]
Message-ID: <9e4733910502020825434a477@mail.gmail.com> (raw)
In-Reply-To: <20050202154139.GA3267@s>
On Wed, 2 Feb 2005 16:41:39 +0100, Haakon Riiser
<haakon.riiser@fys.uio.no> wrote:
> 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?
You should look at writing a DRM driver. DRM implements the kernel
interface to get 3D hardware running. It is a fully accelerated driver
interface. They are located in drivers/char/drm
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2005-02-02 16:38 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 [this message]
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=9e4733910502020825434a477@mail.gmail.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.