From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15752.4011.805533.87501@nanonic.hilbert.space>
From: paurea@gsyc.escet.urjc.es
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /sys/src/^(9 boot)^/pc/memory.c
In-Reply-To: <9e103fd1a1d109673ba2d676e8950368@plan9.bell-labs.com>:Russ Cox's message of 21:26:58 Tuesday,17 September 2002
References: <9e103fd1a1d109673ba2d676e8950368@plan9.bell-labs.com>
Date: Wed, 18 Sep 2002 07:31:23 +0200
Topicbox-Message-UUID: ee2265b6-eaca-11e9-9e20-41e7f4b1d025

Russ Cox writes:
 > VESA actually says nothing about hardware cursors
 > last I checked; if you're going the VESA route you
 > really want to reduce the necessary code to zero.
 > There's an important qualitative difference
 > between zero and non-zero.  Mainly, people who
 > don't write drivers are still up to the task of
 > writing zero lines of code.



Taken from www.vesa.org/standards.htm. this is the reason I thought VESA
standards supported hw cursors...

August
1996
VBE/AF Standard 1.0: The VBE/AF 1.0 defines the interface of a new operating system portable, loadable device driver architecture that will provide access to accelerated graphics hardware. Some of the accelerator functions supported include hardware cursors, multi buffering, solid and transparent off-screen bitmaps, rectangel filling, line drawing and polygon filling.


I found the part of writing the hw cursor support for the sis630 the easy part
of the driver, though. That is why I said that mode switching or whatever
could be done using VESA and add the specific code of the hw cursor appart.

By the way if you are writing a VESA driver and I can help in any way (even
with my lack of knowledge), tell me. I have given a lot of thought to it.
--
                 Saludos,
                         Gorka

"Curiosity sKilled the cat"