public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: nick@linicks.net
Cc: Antonio <tritemio@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: : unclean backward scrolling
Date: Fri, 26 May 2006 08:43:59 +0800	[thread overview]
Message-ID: <44764F4F.5000102@gmail.com> (raw)
In-Reply-To: <7c3341450605211155i3674a27bob6213b449e2d1a3a@mail.gmail.com>

Nick Warne wrote:
> Hmmmph.
> 
> I get this problem, and always have, but I always put it down to my system.
> 
> I run Slackware 10, and this has always happened to me from 2.6.2
> upwards on CRT 1024x768 and later TFT 1280x1024 dvi.
> 
> I use[d] in lilo:
> 
> # VESA framebuffer console @ 1280x1024x?k
> vga=794
> # VESA framebuffer console @ 1024x768x64k
> #vga=791
> 
> So you are not alone.
> 
> Nick
> 
> On 21/05/06, Antonio <tritemio@gmail.com> wrote:
>> Hi,
>>
>> I'm using the radeonfb driver with a radeon 7000 with the frambuffer
>> at 1280x1024 on a i386 system, with a 2.6.16.17 kernel. At boot time,
>> if I stop the messages with CTRL+s and try look the previous messages
>> with CTRL+PagUp (backward scrolling) the screen become unreadable. In
>> fact some lengthier lines are not erased scrolling backward and some
>> random characters a overwritten instead. So it's very difficult to
>> read the messages.
>>
>> I don't have such problem with the frambuffer at 1024x768.
>>
>> All the previous kernels I've tried have this problem (at least up to
>> 2.6.15).
>>
>> If someone can look at this issue I can provide further information.
>>
>> Many Thanks.
>>
>> Cheers,
>>

Can you try this patch and let me know if this fixes the problem?

Tony

PATCH: Fix scrollback with logo issue immediately after boot.

From: David Hollister <david.hollister@amd.com>

After the system boots with the logo, if the first action is a
scrollback, the screen may become garbled.  This patch ensures
that the softback_curr value is updated along with softback_in
following the scrollback.

Signed-off-by: David Hollister <david.hollister@amd.com>
Signed-off-by: Jordan Crouse <jordan.crouse@amd.com>
---

 drivers/video/console/fbcon.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/video/console/fbcon.c b/drivers/video/console/fbcon.c
index ca02071..953eb8c 100644
--- a/drivers/video/console/fbcon.c
+++ b/drivers/video/console/fbcon.c
@@ -2631,7 +2631,7 @@ static int fbcon_scrolldelta(struct vc_d
 					scr_memcpyw((u16 *) q, (u16 *) p,
 						    vc->vc_size_row);
 				}
-				softback_in = p;
+				softback_in = softback_curr = p;
 				update_region(vc, vc->vc_origin,
 					      logo_lines * vc->vc_cols);
 			}


  reply	other threads:[~2006-05-26  0:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-21 13:38 [radeonfb]: unclean backward scrolling Antonio
2006-05-21 18:55 ` : " Nick Warne
2006-05-26  0:43   ` Antonino A. Daplas [this message]
2006-05-26 12:00     ` Antonio
2006-05-26 16:11       ` Nick Warne
2006-05-23 18:38 ` [radeonfb]: " Ondrej Zary
2006-05-26 17:40   ` Pavel Machek
2006-05-29  8:09     ` Antonio
2006-05-31 20:29       ` Nick Warne

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=44764F4F.5000102@gmail.com \
    --to=adaplas@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@linicks.net \
    --cc=tritemio@gmail.com \
    /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