From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: James Simmons <jsimmons@suse.com>
Cc: linux-kernel@vger.kernel.org, linux-fbdev@vuser.vu.union.edu,
linuxconsole-dev@lists.sourceforge.net, geert@linux-m68k.org
Subject: Re: [linux-fbdev] [PATCH] fbcon->vgacon->fbcon
Date: Fri, 3 Nov 2000 19:48:57 MET-1 [thread overview]
Message-ID: <BD211F66773@vcnet.vc.cvut.cz> (raw)
On 3 Nov 00 at 17:20, James Simmons wrote:
> > > I know. I wanted for vgacon to reset the video mode itself. This way ANY
> > > fbdev driver can go back top vgacon.
> >
> > That won't be possible because returning to VGA text mode is chip-specific.
>
> From what I see in the XF4.0 tree you can. I will find out today with me
> working on the tdfx driver.
Yes, you can for example run BIOS initialization. In sandbox with x86
emulator ;-) It is much easier, and much safer, require for 2.5 that
driver has to switch hardware to VGA mode on unload if hardware was
in VGA mode before start, and if it is primary device in the box.
For post-Millennium Matrox hardware, it is as simple as
'outw(0x0003, 0x03DE);' (if you did not ask for disable VGA I/O & disable
VGA BIOS in matroxfb params. And if you asked... you probably know why
better than driver).
Best regards,
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 reply other threads:[~2000-11-03 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-03 19:48 Petr Vandrovec [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-10-28 5:28 [PATCH] fbcon->vgacon->fbcon James Simmons
2000-10-29 3:22 ` [linux-fbdev] " Petr Vandrovec
2000-11-03 7:42 ` James Simmons
2000-11-03 14:14 ` Geert Uytterhoeven
2000-11-04 1:20 ` James Simmons
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=BD211F66773@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=geert@linux-m68k.org \
--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