From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: Krzysztof Helt <krzysztof.h1@wp.pl>,
<linux-fbdev@vger.kernel.org>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] [resend #2] tridentfb: Add DDC support
Date: Thu, 24 Sep 2015 14:00:13 +0300 [thread overview]
Message-ID: <5603D7BD.2050901@ti.com> (raw)
In-Reply-To: <201509021404.37885.linux@rainbow-software.org>
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
On 02/09/15 15:04, Ondrej Zary wrote:
>>> +config FB_TRIDENT_DDC
>>> + bool "DDC for Trident support"
>>> + depends on FB_TRIDENT
>>> + select FB_DDC
>>> + select FB_MODE_HELPERS
>>> + default y
>>> + help
>>> + Say Y here if you want DDC support for your Trident graphics card.
>>> +
>>
>> Why would somebody not want this enabled? Is there some drawback if it's
>> enabled?
>
> It's probably an useless config option but many fbdev drivers have it. I have
> no problem removing it.
Yes, I'd rather see it removed, if no one sees any use for the option.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-09-24 11:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 19:37 [PATCH 1/4] [resend #2] tridentfb: fix hang on Blade3D with CONFIG_CC_OPTIMIZE_FOR_SIZE Ondrej Zary
2015-08-24 19:37 ` [PATCH 2/4] [resend #2] tridentfb: Fix set_lwidth on TGUI9440 and CYBER9320 Ondrej Zary
2015-09-24 11:07 ` Tomi Valkeinen
2015-08-24 19:37 ` [PATCH 3/4] [resend #2] fb_ddc: Allow I2C adapters without SCL read capability Ondrej Zary
2015-09-02 11:33 ` Tomi Valkeinen
2015-09-02 12:04 ` Ondrej Zary
2015-09-24 11:04 ` Tomi Valkeinen
2015-08-24 19:37 ` [PATCH 4/4] [resend #2] tridentfb: Add DDC support Ondrej Zary
2015-09-02 11:30 ` Tomi Valkeinen
2015-09-02 12:04 ` Ondrej Zary
2015-09-24 11:00 ` Tomi Valkeinen [this message]
2015-09-24 11:06 ` [PATCH 1/4] [resend #2] tridentfb: fix hang on Blade3D with CONFIG_CC_OPTIMIZE_FOR_SIZE Tomi Valkeinen
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=5603D7BD.2050901@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=krzysztof.h1@wp.pl \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox