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: <15751.48554.242935.391048@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: <50a10e3a67a87a1a71444a583268d38a@plan9.bell-labs.com>:Russ Cox's message of 18:58:06 Tuesday,17 September 2002
References: <50a10e3a67a87a1a71444a583268d38a@plan9.bell-labs.com>
Date: Wed, 18 Sep 2002 01:41:30 +0200
Topicbox-Message-UUID: ede092b2-eaca-11e9-9e20-41e7f4b1d025

Russ Cox writes:
 > Usually the code also complicates lots of other
 > aspects of the system, so it's been easier just to
 > implement the hardware cursor drivers.  If I ever
 > really want VESA-based drivers, I'll need a software
 > cursor implementation.

Isn't always there the possibility to add a hwcursor also?. I think hw
cursors are directly supported by VESA standards, but I think one
thing is independant from another. Isn't it possible to use VESA for
mode switching or whatever and reduce the code you have to write for
the card to write the hwcursor support?.

 >I have some ideas about
 > doing it without complicating everything else,
 > but they're not particularly well formed.

Another question. What is the software cursor really necessary for?
(other than in vmware). Do there really exist modern cards
which don't support hardware cursor?.
--
                 Saludos,
                         Gorka

"Curiosity sKilled the cat"