9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: paurea@gsyc.escet.urjc.es
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /sys/src/^(9 boot)^/pc/memory.c
Date: Wed, 18 Sep 2002 07:31:23 +0200	[thread overview]
Message-ID: <15752.4011.805533.87501@nanonic.hilbert.space> (raw)
In-Reply-To: <9e103fd1a1d109673ba2d676e8950368@plan9.bell-labs.com>:Russ Cox's message of 21:26:58 Tuesday,17 September 2002

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"


  reply	other threads:[~2002-09-18  5:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-18  1:26 Russ Cox
2002-09-18  5:31 ` paurea [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-18 16:46 Charles Forsyth
2002-09-18 11:38 Russ Cox
2002-09-18 23:21 ` paurea
2002-09-18  4:49 Russ Cox
2002-09-18  5:02 ` Lucio De Re
2002-09-17 23:13 rob pike, esq.
2002-09-18  4:18 ` Lucio De Re
2002-09-18 16:42   ` rob pike, esq.
2002-09-18 12:08     ` Lucio De Re
2002-09-17 22:58 Russ Cox
2002-09-17 23:41 ` paurea
2002-09-17 22:56 rob pike, esq.
     [not found] <dhog@plan9.bell-labs.com>
2002-09-17 22:04 ` David Gordon Hogan
2002-09-17 22:08   ` Scott Schwartz
2002-09-17  7:57 Charles Forsyth
2002-09-17 15:13 ` Axel Belinfante
2002-09-17 20:08   ` Axel Belinfante
2002-09-17 20:37     ` Axel Belinfante
2002-09-17  4:19 YAMANASHI Takeshi
2002-09-17  2:58 Russ Cox
2002-09-17  2:40 YAMANASHI Takeshi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15752.4011.805533.87501@nanonic.hilbert.space \
    --to=paurea@gsyc.escet.urjc.es \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).