Skip to contentSkip to conversation

In-kernel graphics subsystem

DISCUSSION rep stsb 4 participants 5 messages Sep 22, 2005

lore
Share & tools
lore

rep stsb

author
#0 lore raw
Quoted 4 lines · Athar Hameed

We are a group of three undergrad CS students, almost ready to start our senior project. We have this idea of integrating a graphics subsystem with the kernel

A thread about getting vertical synchronization
interrupts from a video card is available at,

http://groups.google.ca/group/alt.lang.asm/browse_frm/thread/d1057c825a7933f0/f7239ffb484587d9

I have started a project to write a windowing program on svgalib at,

http://sourceforge.net/projects/svgalib-windows

My idea is,

1. Convert svgalib drivers into kernel modules to get v-sync interrupts.

2. Write a windowing program on svgalib.

Everyone can join.

Quoted 2 lines

P.S. We are not subscribed to the lklm. Kindly CC your replies to [email protected]

http://groups.google.ca/group/fa.linux.kernel

__________________________________________________________
Find your next car at http://autos.yahoo.ca

#1 lore raw
Quoted 4 lines · rep stsb

1. Convert svgalib drivers into kernel modules to get v-sync interrupts.

2. Write a windowing program on svgalib.

Wouldn't it make more sense to extend the current framebuffer driver support to support v-sync? (framebuffers are already in the kernel, and there were so many security holes with svgalib-based programs that it left a bad taste in a lot of people's mouths)

And having gotten a v-sync interrupt, what would you *do* with it? You'll need an API here....

#2 lore raw
Quoted 11 lines · [email protected] wrote:
Quoted 6 lines · rep stsb

1. Convert svgalib drivers into kernel modules to get v-sync interrupts.

2. Write a windowing program on svgalib.

Quoted 9 lines

Wouldn't it make more sense to extend the current framebuffer driver support to support v-sync? (framebuffers are already in the kernel, and there were so many security holes with svgalib-based programs that it left a bad taste in a lot of people's mouths)

And having gotten a v-sync interrupt, what would you *do* with it? You'll need an API here....

Simple. What we want from such interrupts, is to wait for them, no? So lets use one of the existing structures made for waiting. One example is a file descriptor. Do a blocking read, which the kernel unblocks when the interrupt comes in. A file descriptor also supports things like select() if need be.

Helge Hafting

author
#3 lore raw
In reply to [email protected]
Quoted 7 lines · --- [email protected] wrote:

Wouldn't it make more sense to extend the current framebuffer driver
support to support v-sync? (framebuffers are already in the kernel, and
there were so many security holes with svgalib-based programs that it left
a bad taste in a lot of people's mouths)

I am presently wounded and cannot do either until I heal.

Quoted 3 lines

And having gotten a v-sync interrupt, what would you *do* with it?
You'll need an API here....

svgalib has a vga_waitrefresh() function. It can be implemented as a block on, either a ioctl or a read, on a kernel-space driver, or by polling.

mihai cartoaje

__________________________________________________________
Find your next car at http://autos.yahoo.ca

#4 lore raw
In reply to rep stsb

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 9 lines · rep stsb
Quoted 4 lines · Athar Hameed

We are a group of three undergrad CS students, almost ready to start our senior project. We have this idea of integrating a graphics subsystem with the kernel

A thread about getting vertical synchronization
interrupts from a video card is available at,

This functionality is already exposed by the DRM for several cards. Since work is happening on the X side of things (i.e., EXA) that will make having a DRM for even non-3D cards desireable, this is probably a better route to go.

Either that or extend the existing fb drivers.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDMlVoX1gOwKyEAw8RAgvzAJ41K9u5LQ7GTNe7qfBrWY61+bI32wCeMHIH z4f5g5uzAIgYixVRpQAqZJI=
=CYVB
-----END PGP SIGNATURE-----