From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <9e103fd1a1d109673ba2d676e8950368@plan9.bell-labs.com> From: "Russ Cox" To: 9fans@cse.psu.edu Subject: Re: [9fans] /sys/src/^(9 boot)^/pc/memory.c MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Tue, 17 Sep 2002 21:26:58 -0400 Topicbox-Message-UUID: ede6f756-eaca-11e9-9e20-41e7f4b1d025 > 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?. 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. > 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?. Full-screen VMware is another thing I'd forgotten about. But yes, most modern cards have hardware cursors. Russ