Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Warren Turkal <wturkal@cbu.edu>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: radeon framebuffer
Date: 26 Jun 2003 10:15:20 +0200	[thread overview]
Message-ID: <1056615320.13642.74.camel@gaston> (raw)
In-Reply-To: <200306251342.31473.wturkal@cbu.edu>

On Wed, 2003-06-25 at 20:42, Warren Turkal wrote:

> Radeon Mobility 7500 in a laptop. Apparently, the monitor is connected through 
> DVI. BTW, there was a fix for radeon screen blanking on DVI in the XFree86 
> bugzilla at http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=26. I 
> think you could probably use it to fix console blanking for the radeon.
> 
> BTW, I am not on the list.

If it's a laptop, it's probably LVDS. I indeed changed the code to retreive
the EDID from BIOS for laptops based on recent XFree driver, though I haven't
updated the 2.5 codebase with that change yet.

Thanks for the URL for the blanking fix.

Ben.



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php

      reply	other threads:[~2003-06-26  8:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-24  2:45 radeon framebuffer Warren Turkal
2003-06-25 14:38 ` Benjamin Herrenschmidt
2003-06-25 18:42   ` Warren Turkal
2003-06-26  8:15     ` Benjamin Herrenschmidt [this message]

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=1056615320.13642.74.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=wturkal@cbu.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