All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Weber <weber@nyc.rr.com>
To: James Simmons <jsimmons@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [FBDEV updates] Newest framebuffer fixes.
Date: Thu, 10 Apr 2003 17:16:58 -0400	[thread overview]
Message-ID: <3E95DF4A.7060203@nyc.rr.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0304102005330.23030-100000@phoenix.infradead.org>

James Simmons wrote:
> Hi!
> 
>   Here are the latest framebuffer changes. Some driver updates and a 
> massive cleanup of teh cursor code. Tony please test it on the i810 
> chipset. I tested it on the Riva but there is one bug I can't seem to 
> find. Please test this patch. It is against 2.5.67 BK. It shoudl work 
> against 2.5.67 as well. 
> 
> Please test. 

I get an oops on boot in function fb_set_var (called from 
radeon_init_disp).  This might simply be because I don't have the same 
version of fbmem.c (I had to apply that hunk of the patch by hand) 
although I have source of 2.5.67.

Anyone else not able to apply all parts of the patch cleanly?
Anyone else seeing this problem?


-- 
(o- j o h n  e  w e b e r
//\  weber@sixbit.org
v_/_  http://weber.sixbit.org/
=====  aim/yahoo/msn: worldwidwebers


  parent reply	other threads:[~2003-04-10 21:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-10 19:09 [FBDEV updates] Newest framebuffer fixes James Simmons
2003-04-10 19:09 ` James Simmons
2003-04-10 21:14 ` Paweł Gołaszewski
2003-04-10 21:14   ` Paweł Gołaszewski
2003-04-10 21:37   ` James Simmons
2003-04-10 21:37     ` James Simmons
2003-04-10 21:16 ` John Weber [this message]
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
2003-04-15 19:02         ` James Simmons
2003-04-11 18:20   ` James Simmons
  -- strict thread matches above, loose matches on Subject: below --
2003-04-13  8:17 Antonino Daplas

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=3E95DF4A.7060203@nyc.rr.com \
    --to=weber@nyc.rr.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.