From: "Michel Dänzer" <daenzer@debian.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: maximilian attems <maks@sternwelten.at>,
"Antonino A. Daplas" <adaplas@pol.net>,
347186@bugs.debian.org
Subject: Bug#347186: [Linux-fbdev-devel] Re: Bug#347186: linux-image-2.6.14-2-alpha-generic: garbled Matrox framebuffer
Date: Thu, 12 Jan 2006 11:13:22 +0100 [thread overview]
Message-ID: <1137060802.3941.92.camel@localhost> (raw)
In-Reply-To: <20060112051522.GP11974@tennyson.dodds.net>
On Wed, 2006-01-11 at 21:15 -0800, Steve Langasek wrote:
> On Wed, Jan 11, 2006 at 07:24:04PM +0800, Antonino A. Daplas wrote:
>
> > The "UseFBDev" option was added to X so it can cooperate with fbcon (ie, allows
> > X to restore the console state by using the fbdev API ). In 2.6, fbcon has its
> > own way of restoring its own state so the "UseFBDev" option is not needed, and in
> > your case, is counterproductive.
>
> Aha, didn't know that. It had been my impression that this option meant
> using the fbdev API for all vidcard access;
It does, for the things the fbdev API provides.
--
Earthling Michel Dänzer | Debian (powerpc), X and DRI developer
Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer
prev parent reply other threads:[~2006-01-12 10:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060109090849.GB3481@tennyson.dodds.net>
[not found] ` <20060109093517.GA23253@localhost.localdomain>
[not found] ` <20060109105146.GE3481@tennyson.dodds.net>
2006-01-11 10:28 ` Bug#347186: linux-image-2.6.14-2-alpha-generic: garbled Matrox framebuffer maximilian attems
2006-01-11 11:24 ` Antonino A. Daplas
2006-01-11 11:48 ` Sven Luther
2006-01-11 12:36 ` Antonino A. Daplas
2006-01-11 12:51 ` Bug#347186: [Linux-fbdev-devel] " Sven Luther
2006-01-12 5:15 ` Steve Langasek
2006-01-12 10:13 ` Michel Dänzer [this message]
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=1137060802.3941.92.camel@localhost \
--to=daenzer@debian.org \
--cc=347186@bugs.debian.org \
--cc=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=maks@sternwelten.at \
/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).