From: Jurriaan <thunder7@xs4all.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: Matrox Acceleration Probably_Just_Cosmetic Bug
Date: Mon, 17 Nov 2003 21:35:33 +0100 [thread overview]
Message-ID: <20031117203533.GA6727@middle.of.nowhere> (raw)
In-Reply-To: <20031117194845.GC18448@vana.vc.cvut.cz>
From: Petr Vandrovec <vandrove@vc.cvut.cz>
Date: Mon, Nov 17, 2003 at 08:48:45PM +0100
> On Sun, Nov 16, 2003 at 09:46:01PM +1100, Tudor wrote:
> > If you select "Matrox Acceleration" either built in or as module there
> > are two options:
> > - G100/G200/G400/G450/G500 support
> > and
> > - G100/G200/G400 support
> >
> > If you select the first, the second disappears.
> > If you select the second, the first stays.
>
> It is feature, so you can "extend" your driver later when you decide. Both
> config options points to the same sources. In the past there was option
> "G100-G550 support" with "Secondary head on G450/G550". Unfortunately
> G450 and G550 users were connecting monitor to the secondary output,
> and then complaining that they do not see anything on the monitor.
> So now this option is implicitly enabled when you select first choice,
> and disabled when you select second one.
>
> Unless you cannot afford about 16KB for secondary CRTC driver, you should
> select first choice, as it gives you better upgrade path.
> Petr Vandrovec
>
I've always found this confusing as well, as I use a G450 but never use
the secondary output.
How about
- G100-550 support (including secondary output)
- G100-400 support (single head only)
then mention in the help-text that secondary output is only usable after
running program %%%% ?
Jurriaan
--
She opened her eyes and gazed bleakly at him. "And is it your idea that
discussing this interesting subject will make us friends?"
Guy Gavriel Kay - Tigana
Debian (Unstable) GNU/Linux 2.6.0-test9-mm3 4259 bogomips 0.16 0.11
prev parent reply other threads:[~2003-11-17 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-16 10:46 Matrox Acceleration Probably_Just_Cosmetic Bug Tudor
2003-11-17 19:48 ` Petr Vandrovec
2003-11-17 20:35 ` Jurriaan [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=20031117203533.GA6727@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
/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.