public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joshua Kwan <joshk@triplehelix.org>
To: James Simmons <jsimmons@infradead.org>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [FBDEV updates] Newest framebuffer fixes.
Date: Sun, 13 Apr 2003 00:41:56 -0700	[thread overview]
Message-ID: <20030413074156.GA2536@triplehelix.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0304111921040.26995-100000@phoenix.infradead.org>

[-- Attachment #1: Type: text/plain, Size: 759 bytes --]

On Fri, Apr 11, 2003 at 07:21:16PM +0100, James Simmons wrote:
> 
> > Thanks to James, I finally got radeonfb working, but I had to use the 
> > attached driver instead.  Any word on whether this driver will be 
> > included in the kernel seeing as the current one is so broken?
> 
> Yes :-) 

But this looks like the driver from when it was broken... it has all the
on-screen garbage when I boot. however, that cursor erraticness is gone
thanks to the old driver :)

I don't think going back to old stuff is the right way to think about
stuff like this :/

Kernel 2.5.66-mm3 contained a radeonfb.c which had the cursor issues but
fixed the problem with the bootup junk on the screen.

Regards,
Josh

-- 
New PGP public key: 0x27AFC3EE

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-04-13  7:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-10 19:09 [FBDEV updates] Newest framebuffer fixes James Simmons
2003-04-10 21:14 ` Paweł Gołaszewski
2003-04-10 21:37   ` James Simmons
2003-04-10 21:16 ` John Weber
2003-04-10 21:36   ` James Simmons
2003-04-10 23:06     ` John Weber
2003-04-11  3:34 ` Joshua Kwan
2003-04-11  5:13   ` John Weber
2003-04-11 18:21     ` James Simmons
2003-04-13  7:41       ` Joshua Kwan [this message]
2003-04-15 19:02         ` James Simmons
2003-04-11 18:20   ` 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=20030413074156.GA2536@triplehelix.org \
    --to=joshk@triplehelix.org \
    --cc=jsimmons@infradead.org \
    --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