From: Roger Luethi <rl@hellgate.ch>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Matrox Kconfig
Date: Sat, 5 Jun 2004 13:40:52 +0200 [thread overview]
Message-ID: <20040605114052.GA20401@k3.hellgate.ch> (raw)
The descriptions for CONFIG_FB_MATROX_G450 and CONFIG_FB_MATROX_G100A
in drivers/video/Kconfig (current 2.6) are confusing: Both want to be
selected for Matrox G100, G200, G400 based video cards.
In the menu, it's
# G100/G200/G400/G450/G550 support (sets FB_MATROX_G100, FB_MATROX_G450)
# G100/G200/G400 support (sets FB_MATROX_G100)
# G400 second head support
where the second depends on the first _not_ being selected.
How about this instead?
# Gxxx (generic) (sets FB_MATROX_G100)
# G400 second head (depends FB_MATROX_GXXX, FB_MATROX_I2C)
(sets FB_MATROX_G450)
# G450/550 support (depends on FB_MATROX_GXXX)
Roger
next reply other threads:[~2004-06-05 11:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-05 11:40 Roger Luethi [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-07 17:43 Matrox Kconfig Petr Vandrovec
2004-06-07 17:59 ` Roger Luethi
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=20040605114052.GA20401@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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