[interfacekit] [Fwd: Graphics Drivers]

What I'd like to be doing is just using the existing drivers.  Of course
that just cops out of the question "How do I use the existing drivers?",
but I'm afraid I'm going to have to do that for the moment.  The online
BeBook no longer has the section on writing graphics drivers --
fortunately, I have the "Advanced Developers Guide" in dead tree format;
I'll try to find some time to throw that into at least a text document.

I was reading this section the other night and there is a specific entry
function for graphics drivers that we would use to get at the frame
buffer and any accelerated functions (not the same thing as the
accelerant, I'm afraid).  You hand the function opcodes and data
buffers.  I'll get the docs up ASAP and we'll go from there.

In other news, I subscribed both you and Fred to the interface kit
mailing list; you should be getting notifications, and this mail should
be coming to you via that route anyway.  Yuri is already subscribed, and
there is another guy who is interested in working with the team that may
be joining us soon.

I still haven't dug through all of my vacation mail; I'll try to get
through it all tonight. =P

e

-------- Original Message --------
Subject: Graphics Drivers
Date: Mon, 10 Sep 2001 19:57:45 -0400
From: DarkWyrm <bpmagic@xxxxxxxxxxxxxxx>
Reply-To: DarkWyrm <bpmagic@xxxxxxxxxxxxxxx>
To: erik@xxxxxxxxxxxxxx
References: <999790877_PM_BeOS.mphipps1@xxxxxxxxxxxxxxxx>

Erik,

    I feel like I've been butting my head against a wall with a problem
- 
I've never done driver work before, and I can't seem to figure out 
specifically what graphics-related stuff the app_server handles. From
looking 
at some of the source docs, a graphics driver has both a kernel space
section 
and a user space accelerant. What stuff are we going to need to do? I
think I 
can actually plenty working if I can figure out how to draw the basic 
desktop!

--DW

Other related posts: