public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: gene.heskett@verizon.net
Cc: torvalds@osdl.org, thomas@winischhofer.net,
	linux-kernel@vger.kernel.org, jsimmons@infradead.org
Subject: Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
Date: Sun, 11 Jan 2004 21:42:59 -0800	[thread overview]
Message-ID: <20040111214259.568cff35.akpm@osdl.org> (raw)
In-Reply-To: <200401112353.43282.gene.heskett@verizon.net>

Gene Heskett <gene.heskett@verizon.net> wrote:
>
> However, since I've been running 2.6.1-mm1 here, using the rivafb with 
>  an elderly gforce2-mx2 32 megger, I've noted that when running 
>  kde-3.1.1a with 8 windows, and a couple of them have multimegabyte 
>  backdrops, the biggest one being that famous deep space shot from 
>  hubble of about 4 or 5 months back.  In any other kernel, switching 
>  to that window took about 12 seconds for the backdrop to be converted 
>  to 1600x1200x32 and drawn the first time and about 8 seconds for the 
>  next time.  But with this 2.6.1-mm1 kernel, that repeat window switch 
>  is so close to instant that I cannot see it being drawn.
> 
>  So as far as I'm concerned, this particular set of fb patches to 
>  rivafb *need* to stay in mainline.  I'd sure appreciate it, a bunch.

There are no significant fbdev patches in 2.6.1-mm1.  There is a DRM
update.

  reply	other threads:[~2004-01-12  5:43 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09  9:40 2.6.1-mm1 Andrew Morton
2004-01-09 14:47 ` 2.6.1-mm1 Christoph Hellwig
2004-01-09 14:53 ` 2.6.1-mm1 Wojciech 'Sas' Cieciwa
2004-01-09 14:21   ` 2.6.1-mm1 Bartlomiej Zolnierkiewicz
2004-01-09 15:24 ` 2.6.1-mm1 (compile stats) John Cherry
2004-01-09 16:30 ` 2.6.1-mm1 Prakash K. Cheemplavam
2004-01-09 21:20   ` 2.6.1-mm1 Andrew Morton
2004-01-09 21:24     ` 2.6.1-mm1 Prakash K. Cheemplavam
2004-01-09 23:04     ` 2.6.1-mm1 - nforce2 timer patch sum up cheuche+lkml
2004-01-09 19:31 ` 2.6.1-mm1: sound/pci/cmipci.c compile error Adrian Bunk
2004-01-09 22:43   ` Andrew Morton
2004-01-09 23:37 ` 2.6.1-mm1: drivers/video/sis/sis_main.c link error Adrian Bunk
2004-01-10  4:04   ` Thomas Winischhofer
2004-01-12  2:58     ` Linus Torvalds
2004-01-12  4:53       ` Gene Heskett
2004-01-12  5:42         ` Andrew Morton [this message]
2004-01-12  6:11           ` Valdis.Kletnieks
2004-01-12  6:47             ` Gene Heskett
2004-01-12  7:05               ` Andrew Morton
2004-01-12  7:20                 ` Gene Heskett
2004-01-12 12:38                 ` Gene Heskett
2004-01-12  6:21           ` Gene Heskett
2004-01-12  6:34             ` Andrew Morton
2004-01-12  6:58               ` Gene Heskett
2004-01-12  7:03               ` Gene Heskett
2004-01-12 16:33             ` Dave Jones
2004-01-12 17:00               ` Gene Heskett
2004-01-12 17:04                 ` Dave Jones
2004-01-12  8:58       ` Thomas Winischhofer
2004-01-12 14:32         ` Moritz Muehlenhoff
2004-01-12 10:36       ` Andrew Walrond
2004-01-13 19:04     ` Adrian Bunk
2004-01-14  0:35       ` Thomas Winischhofer
2004-01-15 11:32         ` Adrian Bunk
2004-01-15 11:42           ` Thomas Winischhofer

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=20040111214259.568cff35.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=gene.heskett@verizon.net \
    --cc=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas@winischhofer.net \
    --cc=torvalds@osdl.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