linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gaël Deest" <GUtopiste@free.fr>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Extending vesafb for modes switching ?
Date: Sun, 01 Feb 2004 18:54:27 +0000	[thread overview]
Message-ID: <401D4B63.1080203@free.fr> (raw)

Ok, this may be a silly question. I am not a kernel/fbdev hacker, so I 
may ignore some relevant issues. But after many researches, I can't see 
why it would be impossible for the vesafb driver to handle modes switching.

According to my understanding of this stuff, vesafb mode setting is 
possible only during real mode, via a boot argument,  set by bios 
interrupts, which prevent from changing it later (if I said something 
wrong, please correct me.) But what about the xfree86 driver ? It seems 
to do its job via the VBE bios of the card. What would prevent vesafb 
from doing the same ? I know vesafb only supports VBE 2.0, not 3.0. I 
couldn't find the VBE 2.0 documentation, but in VBE 3.0 one, protected 
mode is supported.

I would see this as a great improvement, because of the really little 
number of cards actually supported by vesafb.

Regards,

Gaël D.


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

             reply	other threads:[~2004-02-01 17:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-01 18:54 Gaël Deest [this message]
2004-02-01 19:00 ` Extending vesafb for modes switching ? Gaël Deest
2004-02-03 17:54 ` James Simmons
2004-02-04 23:50   ` Antonino A. Daplas
  -- strict thread matches above, loose matches on Subject: below --
2004-02-03 18:27 Jak

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=401D4B63.1080203@free.fr \
    --to=gutopiste@free.fr \
    --cc=linux-fbdev-devel@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;
as well as URLs for NNTP newsgroup(s).