From: "Jason Dravet" <dravet@hotmail.com>
To: samuel.thibault@ens-lyon.org
Cc: 7eggert@gmx.de, adaplas@gmail.com, torvalds@osdl.org,
akpm@osdl.org, davej@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vgacon: Workaround for resize bug in some chipsets
Date: Tue, 15 Nov 2005 19:50:39 -0600 [thread overview]
Message-ID: <BAY103-F149222EE61B1B5CD0FBE86DF5C0@phx.gbl> (raw)
In-Reply-To: <20051116000549.GC5080@bouh.residence.ens-lyon.fr>
>From: Samuel Thibault <samuel.thibault@ens-lyon.org>
>To: Jason Dravet <dravet@hotmail.com>
>CC: 7eggert@gmx.de, adaplas@gmail.com, torvalds@osdl.org,
>akpm@osdl.org,davej@redhat.com, linux-kernel@vger.kernel.org
>Subject: Re: [PATCH] vgacon: Workaround for resize bug in some chipsets
>Date: Wed, 16 Nov 2005 01:05:49 +0100
>
>Hi,
>
>Jason Dravet, le Mon 14 Nov 2005 09:27:51 -0600, a écrit :
> > >Jason Dravet <dravet@hotmail.com> wrote:
> > >
> > >> When I run stty rows 20 I get a screen of 80x20. I can see the top
>10
> > >rows
> > >> and the bottom 10 rows are invisible.
> > >
> > >I asume your VGA indicates that it'll divide it's scanline counter by
>2.
> > >Please add a printk("vgacon: mode=%2.2x\n", mode) before line 512 and
> > >report
> > >the value. A real fix will depend on this value. In the meantime,
>removing
> > >the lines 512 and 513 from the original file should be a temporary fix.
> >
> > Here is the result from the printk you requested:
> > vgacon: mode=a3
> >
> > I commented out lines 512 and 513 and the problem remains.
>
>Really strange...
>
>At that same line, could you try adding this:
>
>printk("vgacon: y=%d fonth=%d deffh=%d vidfh=%d scanl=%d\n", height,
>c->vc_font.height, vga_default_font_height, vga_video_font_height,
>vga_scan_lines);
>outb_p(VGA_CRTC_OVERFLOW, vga_video_port_reg);
>printk("vgacon: overflow %02x\n",inb_p(vga_video_port_val));
>outb_p(VGA_CRTC_V_SYNC_END, vga_video_port_reg);
>printk("vgacon: vsync_end %02x\n",inb_p(vga_video_port_val));
>outb_p(VGA_CRTC_V_DISP_END, vga_video_port_reg);
>printk("vgacon: vdisp_end %02x\n",inb_p(vga_video_port_val));
>
>Regards,
>Samuel
Here are the results:
y=25 fonth=16 deffh=16 vidfh=16 scanl=400
overflow=ff
vsync_end=8f
vdisp_end=1f
Thanks,
Jason
next prev parent reply other threads:[~2005-11-16 1:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58DvZ-6en-1@gated-at.bofh.it>
2005-11-14 9:24 ` Bodo Eggert
2005-11-14 15:27 ` Jason Dravet
2005-11-14 16:32 ` Bodo Eggert
2005-11-16 0:05 ` Samuel Thibault
2005-11-16 1:50 ` Jason Dravet [this message]
2005-11-16 2:25 ` Samuel Thibault
2005-11-16 17:58 Jason Dravet
2005-11-16 23:52 ` Samuel Thibault
2005-11-17 1:37 ` Jason Dravet
-- strict thread matches above, loose matches on Subject: below --
2005-11-14 3:46 Jason Dravet
[not found] <58c2Z-8jG-23@gated-at.bofh.it>
2005-11-13 19:41 ` Bodo Eggert
2005-11-13 22:11 ` Antonino A. Daplas
2005-11-13 22:26 ` Mika Penttilä
2005-11-13 23:35 ` Antonino A. Daplas
2005-11-14 3:32 ` H. Peter Anvin
2005-11-13 22:24 ` Samuel Thibault
2005-11-12 22:20 Antonino A. Daplas
2005-11-13 10:23 ` Martin Mares
2005-11-13 11:06 ` Samuel Thibault
2005-11-13 14:33 ` Antonino A. Daplas
2005-11-13 22:25 ` Samuel Thibault
2005-11-13 23:37 ` 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=BAY103-F149222EE61B1B5CD0FBE86DF5C0@phx.gbl \
--to=dravet@hotmail.com \
--cc=7eggert@gmx.de \
--cc=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®