From: Matt Mackall <mpm@selenic.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Radeon framebuffer weirdness in -mm2
Date: Fri, 21 Jan 2005 16:52:09 -0800 [thread overview]
Message-ID: <20050122005209.GN12076@waste.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0501211315010.6118@scrub.home>
On Fri, Jan 21, 2005 at 01:33:39PM +0100, Roman Zippel wrote:
> Hi,
>
> On Thu, 20 Jan 2005, Matt Mackall wrote:
>
> > On Thu, Jan 20, 2005 at 08:07:11PM -0800, Andrew Morton wrote:
> > > Andrew Morton <akpm@osdl.org> wrote:
> > > >
> > > > Next suspects would be:
> > > >
> > > > +cleanup-vc-array-access.patch
> > > > +remove-console_macrosh.patch
> > > > +merge-vt_struct-into-vc_data.patch
> > > >
> > > >
> > >
> > > Make that:
> > >
> > > +cleanup-vc-array-access.patch
> > > +remove-console_macrosh.patch
> > > +merge-vt_struct-into-vc_data.patch
> > > +vgacon-fixes-to-help-font-restauration-in-x11.patch
> >
> > It's something in this batch. Which is good, as I'd be a bit
> > disappointed if the "vt leakage" were somehow attributable to the fb
> > layer. More bisection after dinner.
>
> Could you try the patch below. I cleaned up the logic a little in
> redraw_screen() and the code below really wants to do a update_screen().
> The old switch_screen(fg_console) behaved like update_screen(fg_console).
Same behaviour.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2005-01-22 0:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 23:21 Radeon framebuffer weirdness in -mm2 Matt Mackall
2005-01-20 23:39 ` Andrew Morton
2005-01-20 23:48 ` Matt Mackall
2005-01-21 0:01 ` Andrew Morton
2005-01-21 3:57 ` Matt Mackall
2005-01-21 4:05 ` Andrew Morton
2005-01-21 4:07 ` Andrew Morton
2005-01-21 6:09 ` Matt Mackall
2005-01-21 12:33 ` Roman Zippel
2005-01-21 16:36 ` Antonino A. Daplas
2005-01-22 0:52 ` Matt Mackall [this message]
2005-01-24 4:00 ` Benjamin Herrenschmidt
2005-01-21 16:36 ` Antonino A. Daplas
2005-01-21 0:03 ` Benjamin Herrenschmidt
2005-01-21 0:24 ` James Simmons
2005-01-21 0:03 ` Benjamin Herrenschmidt
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=20050122005209.GN12076@waste.org \
--to=mpm@selenic.com \
--cc=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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).