All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Pozsar Balazs <pozsy@sch.bme.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FBdev remains in unusable state
Date: Wed, 12 Dec 2001 20:13:59 MET-1	[thread overview]
Message-ID: <BCDCADB4194@vcnet.vc.cvut.cz> (raw)

On 12 Dec 01 at 19:49, Pozsar Balazs wrote:
> 
> The video card is a matrox G450, and I am using the vesa framebuffer.
> (I know there's a seperate mga fb driver, but this should work for this
> combination)

No. vesafb does not work together with mga driver in X (although
I believe that vesafb works with XFree mga driver, only Matrox driver
is binary bad citizen).
 
> Is this a bug in the kernel fb code, or in X? Are there any workarounds?
> How could I restore textmode?

Neither. X restore R/W registers to their previous values, while write-only
registers to their values for normal text mode. Yes, there is a 
'workaround'. Use (much faster) matroxfb.
                                                    Best regards,
                                                        Petr Vandrovec
                                                        vandrove@vc.cvut.cz
                                                        
                                                        

             reply	other threads:[~2001-12-12 19:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-12 20:13 Petr Vandrovec [this message]
2001-12-12 20:14 ` FBdev remains in unusable state Pozsar Balazs
  -- strict thread matches above, loose matches on Subject: below --
2001-12-13 18:00 Petr Vandrovec
2001-12-13 17:03 ` David Woodhouse
2001-12-12 21:55 Petr Vandrovec
2001-12-13 11:35 ` David Woodhouse
2001-12-13 13:29   ` Pozsar Balazs
2001-12-13 16:11     ` David Woodhouse
2001-12-12 21:32 Petr Vandrovec
2001-12-12 20:42 ` Pozsar Balazs
2001-12-12 18:49 Pozsar Balazs

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=BCDCADB4194@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pozsy@sch.bme.hu \
    /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.