linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Antonino Daplas <adaplas@pol.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH 1/3: FBDEV: VGA State Save/Restore module
Date: Thu, 5 Dec 2002 03:41:57 +0100	[thread overview]
Message-ID: <20021205024157.GA19706@vana> (raw)
In-Reply-To: <1039056748.1032.22.camel@localhost.localdomain>

On Thu, Dec 05, 2002 at 07:53:16AM +0500, Antonino Daplas wrote:
> On Thu, 2002-12-05 at 03:33, Petr Vandrovec wrote:
> > On  5 Dec 02 at 6:05, Antonino Daplas wrote:
> > planes 0 & 1.
> 
> Okay, then.  My approach was to be non-vgacon specific.  I'll do it to
> specifically target vgacon then.
> 
> To summarize:
> plane 0/1 save 8K at offset 0 and 8K at offset 16K;

I'm not sure about this one. AFAIK by default vgacon uses first 32KB
completely (every second byte...) from both 0/1, and can be configured
(by enabling VGA_CAN_DO_64KB) to use full 64KB.

> plane 2   save 32K at offset 0 (covers blocks 0-3),
> plane 3   same for plane 2
> 
> Drivers can set VGA_SAVE_TEXT | VGA_SAVE_FONT0 to save planes 0-2.  If
> there are no complaints, I'll  proceed doing it this way.

I have no other problems.
						Petr Vandrovec
						vandrove@vc.cvut.cz

  reply	other threads:[~2002-12-05  2:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-04 22:33 [PATCH 1/3: FBDEV: VGA State Save/Restore module Petr Vandrovec
2002-12-05  2:53 ` Antonino Daplas
2002-12-05  2:41   ` Petr Vandrovec [this message]
2002-12-05 17:39 ` James Simmons
  -- strict thread matches above, loose matches on Subject: below --
2002-12-04 18:41 Petr Vandrovec
2002-12-05  1:05 ` Antonino Daplas
2002-12-04 17:26 Antonino 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=20021205024157.GA19706@vana \
    --to=vandrove@vc.cvut.cz \
    --cc=adaplas@pol.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).