All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	Dave Jones <davej@redhat.com>, Jason <dravet@hotmail.com>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] vgacon: Workaround for resize bug in some chipsets
Date: Mon, 14 Nov 2005 07:37:17 +0800	[thread overview]
Message-ID: <4377CE2D.2070304@gmail.com> (raw)
In-Reply-To: <20051113222514.GK4972@bouh.residence.ens-lyon.fr>

Samuel Thibault wrote:
> Antonino A. Daplas, le Sun 13 Nov 2005 22:33:18 +0800, a écrit :
>> Samuel Thibault wrote:
>>> Antonino A. Daplas, le Sun 13 Nov 2005 06:20:53 +0800, a écrit :
>>>> "I updated to the development kernel and now during boot only the top of the
>>>> text is visable. For example the monitor screen the is the lines and I can
>>>> only  see text in the asterik area.
>>>> ---------------------
>>>> | ****************  |
>>>> | *              *  |
>>>> | *              *  |
>>>> | ****************  |
>>>> |                   |
>>>> |                   |
>>>> |                   |
>>>> ---------------------
>>> Are you missing some left and right part too? What are the dimensions of
>>> the text screen at bootup? What bootloader are you using? (It could be a
>>> bug in the boot up text screen dimension discovery).
>> It was just the height.  All numbers (done with printk's) look okay from
>> bootup. He gets 80 and 25 for ORIG_VIDEO_NUM_COLS and ORIG_VIDEO_NUM_LINES
>> respectively.
> 
> And you got less than 25 lines? How many exactly?

If the original size was at 80x25, and vgacon_doresize() was called, the
the resulting screen is only 80x12.5. The 13th line has its bottom half
chopped off, and the rest of the lines (14-25) is invisible.

If he sets it at < 25, he gets a window much smaller than 12.5, but he did
not specify. So my guess is his chipset programs the screen height by 1/2
of the value of the requested rows.

Tony

  reply	other threads:[~2005-11-13 23:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-12 22:20 [PATCH] vgacon: Workaround for resize bug in some chipsets 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 [this message]
     [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
  -- strict thread matches above, loose matches on Subject: below --
2005-11-14  3:46 Jason Dravet
     [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
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

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=4377CE2D.2070304@gmail.com \
    --to=adaplas@gmail.com \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=dravet@hotmail.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 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.