From: Scott Robert Ladd <coyote@coyotegulch.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Framebuffer updates.
Date: Wed, 26 Mar 2003 09:03:03 -0500 [thread overview]
Message-ID: <3E81B317.3080504@coyotegulch.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0303251032320.4272-100000@maxwell.earthlink.net>
James Simmons wrote:
> As usually I have a patch avalaible at
> The patch has updates for the ATI Rage 128, Control, and Platnium
> framebuffer driver. The Radeon patch adds PLL times for the R* series of
> cards. Memory is now safe to allocate for the software cursor and inside
> fbcon. There still are issues with syncing which cause the cursor on some
> systems to become corrupt sometimes.
From your description, this doesn't sound like these patches solve the
problem with radeonfb not detecting a DFP connected to the DVI. I posted
a message about this bug a week ago, and am more than willing to look
into fixing it myself if it isn't on your schedule.
--
Scott Robert Ladd
Coyote Gulch Productions (http://www.coyotegulch.com)
-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
next prev parent reply other threads:[~2003-03-26 14:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 17:57 Framebuffer updates James Simmons
2003-03-25 18:20 ` Jens Axboe
2003-03-25 18:47 ` James Simmons
2003-03-25 18:27 ` Florin Iucha
2003-03-25 20:50 ` James Simmons
2003-03-26 13:16 ` Benjamin Herrenschmidt
2003-03-26 20:08 ` James Simmons
2003-03-26 14:03 ` Scott Robert Ladd [this message]
2003-03-26 20:07 ` James Simmons
-- strict thread matches above, loose matches on Subject: below --
2003-03-18 17:16 James Simmons
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=3E81B317.3080504@coyotegulch.com \
--to=coyote@coyotegulch.com \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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).