9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: paurea@plan9.escet.urjc.es
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ati radeon support
Date: Fri,  3 Oct 2003 14:53:23 +0200	[thread overview]
Message-ID: <caf1c2a92241cb70179ed83979a7005d@plan9.escet.urjc.es> (raw)
In-Reply-To: <3F7CA907.8C9F61@null.net>

> Of course the ironic thing is that Plan 9 really doesn't need more
> than VESA provides; all those 3D graphics features of today's cards
> are being wasted under Plan 9.  A single VESA driver would have
> prevented having to keep hacking drivers for each new card.

On last discussion I understood that there is a problem with hw cursor
(noone supports it even if the standard VESA does). Before using VESA,
someone has to write support for software cursor. Another issue may be
that VESA may not be as standard as one might expect (for example BIOS
bugs are card dependant). Take a look at the vesa X driver for example.


								Gorka



  reply	other threads:[~2003-10-03 12:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-01 21:23 Hugo Santos
2003-10-01 22:01 ` mirtchov
2003-10-02  0:55   ` okamoto
2003-10-02  8:11   ` Christian Grothaus
2003-10-02  8:31     ` Christian Grothaus
2003-10-02 18:56     ` Hugo Santos
2003-10-02 19:07       ` mirtchov
2003-10-03  8:43         ` Douglas A. Gwyn
2003-10-03 12:53           ` paurea [this message]
2003-10-03 13:12             ` rog
2003-10-03 13:16               ` Charles Forsyth
2003-10-03 14:34               ` jmk
2003-10-03 14:46                 ` rog
2003-10-03 17:59                 ` C H Forsyth
2003-10-03 18:28                   ` jmk
2003-10-03 19:22                     ` Charles Forsyth
2003-10-03 23:41                       ` Charles Forsyth
2003-10-03  9:07 Tiit Lankots
2003-10-03  9:17 ` Atanas Bachvaroff
2003-10-03  9:27   ` Charles Forsyth
2003-10-03 11:42     ` C H Forsyth

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=caf1c2a92241cb70179ed83979a7005d@plan9.escet.urjc.es \
    --to=paurea@plan9.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).