All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Knut Petersen <Knut_Petersen@t-online.de>
Cc: linux-fbdev-devel@lists.sourceforge.net,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: scroll modes
Date: Thu, 01 Dec 2005 08:01:42 +0800	[thread overview]
Message-ID: <438E3D66.8080601@gmail.com> (raw)
In-Reply-To: <438E2D8E.2040503@t-online.de>

Knut Petersen wrote:
> Antonino A. Daplas schrieb:
> 
>> Knut Petersen wrote:
>>  
>>
>>> Geert Uytterhoeven wrote:
>>>
>>>   
>>>> Ywrap has been working fine with amifb since ages (unless someone
>>>> broke it very
>>>> recently).     
>>> We are talking about scrollmode = SCROLL_WRAP_MOVE ?
>>>   
>>
>> Try this patch.
>>
>>  
>>
> It doesn´t help. I cecked the values for rows and vrows and believe that
> they are ok.
> To be sure that we are not talking about different things: How _should_
> this mode
> work? If I use ywrap, why is it called scroll_wrap_MOVE? It should not
> be necessary
> to move anything around  when using ywrap ...

You still have to, because the console can ask for a partial scroll.
For example, assume you have a screen of 20 lines, the console can, for
example, ask to scroll rows 5-10 up by 1 line to row 4-9, leave rows 0-3 and
11-19 in the same place. So fbcon will adjust the yoffset, but has to move
rows 0-3 and 11-19 so they appear stationary to the user.

However, if the request for scrolling is a screenful at at time (ie,
move entire screen contents up by 1 line), then I don't think any
bmoves will be called.  Here's a snippet from the fbcon_scroll
(comments are mine):

	if (t > 0) /* if top is at origin, do not move */
		fbcon_bmove(vc, 0, 0, count, 0, t,
			    vc->vc_cols);
	ywrap_up(vc, count); /* adjust yoffset */

	if (vc->vc_rows - b > 0) /* if bottom is at end, do not move */
		fbcon_bmove(vc, b - count, 0, b, 0,
			    vc->vc_rows - b,
			    vc->vc_cols);

Tony

P.S: Ywrapping is very old code, and I think Geert can explain the code
much better than I.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

  reply	other threads:[~2005-12-01  0:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-30 12:43 scroll modes Knut Petersen
2005-11-30 12:48 ` Geert Uytterhoeven
2005-11-30 17:32   ` Knut Petersen
2005-11-30 20:40     ` Antonino A. Daplas
2005-11-30 22:54       ` Knut Petersen
2005-12-01  0:01         ` Antonino A. Daplas [this message]
2005-12-01 23:03           ` Knut Petersen
2005-12-01 23:16             ` Antonino A. Daplas
2005-12-01 23:27             ` Antonino A. Daplas
2005-12-01 23:47               ` Knut Petersen
2005-12-02  1:16                 ` Antonino A. Daplas
2005-12-03 12:01                 ` Geert Uytterhoeven
2005-12-02 10:55       ` Knut Petersen
2005-12-08 20:57         ` Antonino A. 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=438E3D66.8080601@gmail.com \
    --to=adaplas@gmail.com \
    --cc=Knut_Petersen@t-online.de \
    --cc=geert@linux-m68k.org \
    --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 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.