From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Krzysztof Helt <krzysztof.h1@poczta.fm>
Cc: Linux-fbdev-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Error in fbcon_switch ?
Date: Thu, 22 May 2008 22:57:46 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0805222246130.8919@anakin> (raw)
In-Reply-To: <20080522184750.a3513914.krzysztof.h1@poczta.fm>
On Thu, 22 May 2008, Krzysztof Helt wrote:
> On Wed, 21 May 2008 09:17:45 +0200 (CEST)
> Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > On Tue, 20 May 2008, Krzysztof Helt wrote:
>
> > > I found that root of the problem is that fbcon_switch copies the var.vmode
> > > field from the previous console. If this copy is removed everything is alright, ie.
> > >
> > > tty1 (lace) -> tty2 (non-lace) -> tty1 (lace) -> tty2 (non-lace)
I could easily reproduce it on my Amiga. Haven't tried on the PS3 yet.
Seems to be introduced by
commit e4fc27618b75234b721c4a13d0e0d9d07e75e641
Author: Antonino A. Daplas <adaplas@gmail.com>
Date: Tue Nov 8 21:39:09 2005 -0800
[PATCH] fbcon: Console Rotation - Prepare fbcon for console rotation
Strange I never noticed it before... Oh well, interlace doesn't seem to
be popular anymore.
> > > Is this a correct solution to the problem? What is a purpose of copying vmode field?
> > >
> (...)
> > > IMO, at least the first three should not be copied. I am not sure about YWRAP and
> > > CONUPDATE/SMOOTH_XPAN.
> >
> > As it copies [xy]offset, it probably needs YWRAP/SMOOTH_XPAN/CONUPDATE.
>
> As I thought more about it, the copy of [xy]offset is also wrong. What if I have
> one console with 4096 vyres and another with only 1024 vyres. Copying offsets
> between them does not make any sense. Setting offsets to zero makes more sense
> (there is no scrollback buffer available anyway).
>
> > So I guess it should keep the bits under FB_VMODE_MASK.
>
> Actually, the opposite. Bits under FB_VMODE_MASK should be cleared
> for old console, the remaining ones (YWRAP/SMOOTH_XPAN/CONUPDATE)
> can be copied (or-ed with new ones).
Sorry, that's what I meant (`keep' means do not copy).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2008-05-22 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 21:11 Error in fbcon_switch ? Krzysztof Helt
2008-05-21 7:17 ` Geert Uytterhoeven
2008-05-22 16:47 ` Krzysztof Helt
2008-05-22 20:57 ` Geert Uytterhoeven [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=Pine.LNX.4.64.0805222246130.8919@anakin \
--to=geert@linux-m68k.org \
--cc=krzysztof.h1@poczta.fm \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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