On Mon, Jan 20, 2003 at 09:29:38AM +0800, Antonino Daplas wrote:
fb_pan_display() does not test for YWRAP. Can you try this?
This doesn't appear to solve the ywrap problem - I still get
places where the screen doesn't scroll. I decided to write a
small program to dump out the contents of fb_var_screeninfo, and
where stuff goes horribly wrong:
bash-2.04# ./tst
Visible: 1280x1024
Virtual: 1280x1632
BPP : 8
Offset : +0+2352
bash-2.04# ./tst
Visible: 1280x1024
Virtual: 1280x1632
BPP : 8
Offset : +0+2392
Up to the point where it goes wrong:
bash-2.04# ./tst
Visible: 1280x1024
Virtual: 1280x1632
BPP : 8
Offset : +0+528
bash-2.04# ./tst
Visible: 1280x1024
Virtual: 1280x1632
BPP : 8
Offset : +0+568
bash-2.04# ./tst
Visible: 1280x1024 <--- this is the last line on the screen
Virtual: 1280x1632
BPP : 8
Offset : +0+608
bash-2.04#
So it looks like something isn't limiting the yoffset in the generic
console layer; an xoffset of 2392 when the maximum virtual Y is 1632
is just nonsense.
I also noticed an additional problem with fbcon: if I change the
resolution using fbset, the change occurs, except I end up with
corrupted mess on the screen (the reminents of the original display.)
The shell prompt is nowhere to be seen.
Hitting ^L clears the screen and then the shell prompt is visiable.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
On Mon, 2003-02-03 at 03:57, Russell King wrote:
On Mon, Jan 20, 2003 at 09:29:38AM +0800, Antonino Daplas wrote:
quoted
fb_pan_display() does not test for YWRAP. Can you try this?
This doesn't appear to solve the ywrap problem - I still get
places where the screen doesn't scroll. I decided to write a
small program to dump out the contents of fb_var_screeninfo, and
where stuff goes horribly wrong:
bash-2.04# ./tst
Visible: 1280x1024
Virtual: 1280x1632
BPP : 8
Offset : +0+2352
bash-2.04# ./tst
Visible: 1280x1024
Virtual: 1280x1632
BPP : 8
Offset : +0+2392
Up to the point where it goes wrong:
bash-2.04# ./tst
Visible: 1280x1024
Virtual: 1280x1632
BPP : 8
Offset : +0+528
bash-2.04# ./tst
Visible: 1280x1024
Virtual: 1280x1632
BPP : 8
Offset : +0+568
bash-2.04# ./tst
Visible: 1280x1024 <--- this is the last line on the screen
Virtual: 1280x1632
BPP : 8
Offset : +0+608
bash-2.04#
So it looks like something isn't limiting the yoffset in the generic
console layer; an xoffset of 2392 when the maximum virtual Y is 1632
is just nonsense.
It might be a problem with display.vrows not being updated during
fbcon_resize(). I think I sent James some patches before that added
that.
Can you try adding this at the end of fbcon_resize() in
drivers/video/fbcon.c?
p->vrows = info->var.yres_virtual/vc->vc_font.height;
Tony
PS: I never encountered your problem, but I don't have hardware that's
capable of ywrap.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
So it looks like something isn't limiting the yoffset in the generic
console layer; an xoffset of 2392 when the maximum virtual Y is 1632
is just nonsense.
I'm going to need to do some heavy cleaning in the next few days.
I also noticed an additional problem with fbcon: if I change the
resolution using fbset, the change occurs, except I end up with
corrupted mess on the screen (the reminents of the original display.)
The shell prompt is nowhere to be seen.
Hitting ^L clears the screen and then the shell prompt is visiable.
The method to use now is stty to change the console mode. It works :-)
fbset is used to change the variable the vt terminals are not familiar
with such as bpp.