From: Warren Turkal <wturkal@cbu.edu>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: radeon framebuffer
Date: Wed, 25 Jun 2003 13:42:30 -0500 [thread overview]
Message-ID: <200306251342.31473.wturkal@cbu.edu> (raw)
In-Reply-To: <1056551922.13642.49.camel@gaston>
On Wednesday 25 June 2003 09:38 am, Benjamin Herrenschmidt wrote:
> On Tue, 2003-06-24 at 04:45, Warren Turkal wrote:
> > I just wanted to make sure that the developers of this list know that the
> > radeon framebuffer only works enough to completely white out my screen
> > when doing anything other than text mode stuff in 2.5.73
>
> radeonfb in current Linus tree doesn't have all of my latest fixes,
> though I can't say for sure those would help or not. What card & what
> monitor setup do you have ?
>
> Ben.
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.
Thanks, Warren
--
Treasurer, GOLUM, Inc.
http://www.golum.org
-------------------------------------------------------
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
next prev parent reply other threads:[~2003-06-25 18:42 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 [this message]
2003-06-26 8:15 ` Benjamin Herrenschmidt
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=200306251342.31473.wturkal@cbu.edu \
--to=wturkal@cbu.edu \
--cc=benh@kernel.crashing.org \
--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).