From: Joshua Kwan <joshk@triplehelix.org>
To: mk <mk@www0.org>
Cc: jsimmons@infradead.org,
linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Problematic Radeon fb on 2.5.63
Date: Sat, 1 Mar 2003 22:57:13 -0800 [thread overview]
Message-ID: <20030302065713.GA27809@triplehelix.org> (raw)
In-Reply-To: <20030301160909.GA1604@www0.org>
[-- Attachment #1.1: Type: text/plain, Size: 790 bytes --]
On Sat, Mar 01, 2003 at 04:09:09PM +0000, mk wrote:
> This is Radeon 7500 QW on a VT8363/8365 [KT133/KM133 AGP]
Cool.. I've got a:
radeonfb: ATI Radeon M6 LY DDR SGRAM 32 MB
> Cursor does not appear on console, fbset changes are most likely
> to cause screen corruption or just black screen and what must effect all
> fb graphics support, choosing an fbdriver and not fb console support, is
> an accepted option (at least on menuconfig) having as a result blank
> screen on boot.
Should an fbdriver depend on CONFIG_FRAMEBUFFER_CONSOLE then? It seems
wrong to me.
I have attached the fix for the cursor not appearing problem. James
already has it in his own tree, why isn't it getting pushed to
mainstream?
Regards
Josh
--
New PGP public key: 0x27AFC3EE
[-- Attachment #1.2: radeonfb.diff --]
[-- Type: text/plain, Size: 289 bytes --]
--- linux/drivers/video/radeonfb.c-2.5.62 2003-01-03 01:31:42.000000000 +0100
+++ linux/drivers/video/radeonfb.c 2003-02-18 12:13:07.000000000 +0100
@@ -2212,6 +2212,7 @@
.fb_copyarea = cfb_copyarea,
.fb_imageblit = cfb_imageblit,
#endif
+ .fb_cursor = soft_cursor,
};
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-03-02 6:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-01 16:09 Problematic Radeon fb on 2.5.63 mk
2003-03-02 6:57 ` Joshua Kwan [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=20030302065713.GA27809@triplehelix.org \
--to=joshk@triplehelix.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mk@www0.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