From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: James Simmons <jsimmons@suse.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
FrameBuffer List <linux-fbdev@vuser.vu.union.edu>,
Linux console project <linuxconsole-dev@lists.sourceforge.net>
Subject: Re: [linux-fbdev] [PATCH] fbcon->vgacon->fbcon
Date: Sun, 29 Oct 2000 04:22:28 +0100 [thread overview]
Message-ID: <20001029042228.B379@ppc.vc.cvut.cz> (raw)
In-Reply-To: <Pine.LNX.4.21.0010272217090.410-101000@euclid.oak.suse.com>
In-Reply-To: <Pine.LNX.4.21.0010272217090.410-101000@euclid.oak.suse.com>; from jsimmons@suse.com on Fri, Oct 27, 2000 at 10:28:02PM -0700
On Fri, Oct 27, 2000 at 10:28:02PM -0700, James Simmons wrote:
>
> Hi!
>
> Here is a new version of my vga patch. I now have it where you go from
> vgacon to fbcon to vgacon again. I have tried this with the vga16fb
> driver and it works very well. It needs a little work for a better
> vgacon restore mode. Vgacon can even restore the fonts itself :-)
> I tested it with the matrox framebufer with less luck. I assume I'm not
> freeing resources properly. I will test it with other fbdev drivers next
> week. Thank you.
Matroxfb does not switch hardware to VGA mode on exit. Try doing
'fbset -depth 0 -a' before quitting from matroxfb.
Petr Vandrovec
vandrove@vc.cvut.cz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-10-29 3:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-28 5:28 [PATCH] fbcon->vgacon->fbcon James Simmons
2000-10-29 3:22 ` Petr Vandrovec [this message]
2000-11-03 7:42 ` [linux-fbdev] " James Simmons
2000-11-03 14:14 ` Geert Uytterhoeven
2000-11-04 1:20 ` James Simmons
-- strict thread matches above, loose matches on Subject: below --
2000-11-03 19:48 Petr Vandrovec
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=20001029042228.B379@ppc.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=jsimmons@suse.com \
--cc=linux-fbdev@vuser.vu.union.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxconsole-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox