linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: "Antonino A. Daplas" <adaplas@hotpop.com>
Subject: Re: Rivafb won't work with DVI connector
Date: Sat, 27 Nov 2004 13:29:02 -0500	[thread overview]
Message-ID: <1101580142.4725.177.camel@admin.tel.thor.asgaard.local> (raw)
In-Reply-To: <200411271240.13475.andrew@walrond.org>

On Sat, 2004-11-27 at 12:40 +0000, Andrew Walrond wrote:
> 
> So, not only is this not going to work, but the vesa driver also seems broken 
> when used with dvi.

s/vesa driver/on-card video BIOS/


-- 
Earthling Michel Dänzer      |     Debian (powerpc), X and DRI developer
Libre software enthusiast    |   http://svcs.affero.net/rm.php?r=daenzer


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-11-27 18:29 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-25  0:07 Rivafb won't work with DVI connector Antonino A. Daplas
2004-11-25 15:27 ` Andrew Walrond
2004-11-25 21:16   ` Antonino A. Daplas
2004-11-26 14:09   ` Antonino A. Daplas
2004-11-27 12:40     ` Andrew Walrond
2004-11-27 18:29       ` Michel Dänzer [this message]
2004-11-27 22:35         ` Andrew Walrond
2004-11-27 22:43       ` Antonino A. Daplas
  -- strict thread matches above, loose matches on Subject: below --
2004-11-19 11:37 Andrew Walrond
2004-11-19 22:08 ` Antonino A. Daplas
2004-11-20 15:52   ` Andrew Walrond
2004-11-22  0:11     ` Antonino A. Daplas
2004-11-22  9:23       ` Andrew Walrond
2004-11-22  9:43         ` Andrew Walrond
2004-11-22 22:13           ` Antonino A. Daplas
2004-11-22 23:47             ` Andrew Walrond
2004-11-22 23:54               ` Andrew Walrond
2004-11-23  1:50               ` Antonino A. Daplas
2004-11-23 12:32                 ` Andrew Walrond
2004-11-23 14:28                   ` Antonino A. Daplas
2004-11-23 15:09                     ` Andrew Walrond
2004-11-23 15:18                       ` Antonino A. Daplas
2004-11-23 16:08                         ` Andrew Walrond
2004-11-23 17:07                           ` Antonino A. Daplas
2004-11-23 18:01                             ` Andrew Walrond
2004-11-23 18:26                               ` Antonino A. Daplas
2004-11-23 19:00                                 ` Andrew Walrond
2004-11-23 19:07                                   ` Andrew Walrond
2004-11-23 19:23                                 ` Andrew Walrond
2004-11-23 19:59                                   ` Geert Uytterhoeven
2004-11-23 20:53                                     ` Andrew Walrond
2004-11-23 22:44                                       ` Antonino A. Daplas
2004-11-23 23:59                                         ` Andrew Walrond
2004-11-24 22:38                                         ` Andrew Walrond
2004-11-23 20:21                                   ` Chad Daelhousen
2004-11-24 23:01                                 ` Andrew Walrond

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=1101580142.4725.177.camel@admin.tel.thor.asgaard.local \
    --to=michel@daenzer.net \
    --cc=adaplas@hotpop.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).