From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Dave Airlie <airlied@linux.ie>, Jean Delvare <jdelvare@suse.de>
Cc: Jeff Mahoney <jeffm@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fb/intelfb: Do not depend on EMBEDDED
Date: Sat, 12 Dec 2009 13:55:40 -0800 [thread overview]
Message-ID: <aa541tsbrtanvarunansa3uh.1260654940760@email.android.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 2413 bytes --]
Right, the logic is that the driver really is for embedded (i.e. very special purpose) use. It should not be selected unless you really know what you're doing or are building a very particular product.
If you can think of a better way of preventing users and distros from accidentally selecting this, then please send a patch.
Jesse
Dave Airlie <airlied@linux.ie> wrote:
>>> I am worried that the intelfb driver depends on EMBEDDED. I consider>> this an abuse of the EMBEDDED configuration option, which as I>> understand it was originally meant to expose fine-tuning options,>> rather than to arbitrarily disable drivers when not selected.>>Since we merged a kms driver for Intel hw that supports all intel chipsets>and more importantly all the outputs on Intel chipsets, intelfb should>be considered legacy at the least and broken on > 50% of intel hw.>>We left it in in that most ppl who wanted it were using it in embedded >configs, whereas for most users it just doesn't work, like I don't thinkit>supports LVDS which means loading it on a laptop will trash it.>>Dave>>>> >> So I suggest that we drop this dependency now.>> >> Signed-off-by: Jean Delvare <jdelvare@suse.de>>> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>>> Cc: Dave Airlie <airlied@linux.ie>>> --->> Jesse, in the original commit, you wrote that intelfb was "really a>> special purpose embedded driver". It looks like a perfectly standard>> framebuffer driver to me, which means that it may have users beyond>> embedded. For example I always prefer framebuffer over X for my>> servers. Or am I missing something and intelfb is really special?>> >> drivers/video/Kconfig | 2 +->> 1 file changed, 1 insertion(+), 1 deletion(-)>> >> --- linux-2.6.32.orig/drivers/video/Kconfig 2009-12-03 08:48:34.000000000 +0100>> +++ linux-2.6.32/drivers/video/Kconfig 2009-12-11 10:57:43.000000000 +0100>> @@ -1121,7 +1121,7 @@ config FB_CARILLO_RANCH>> >> config FB_INTEL>> tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)">> - depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EMBEDDED>> + depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL>> select FB_MODE_HELPERS>> select FB_CFB_FILLRECT>> select FB_CFB_COPYAREA>> >> >ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next reply other threads:[~2009-12-13 1:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-12 21:55 Jesse Barnes [this message]
2009-12-13 11:50 ` Jean Delvare
2009-12-13 21:53 ` Dave Airlie
2009-12-16 13:37 ` Jean Delvare
2009-12-16 18:00 ` Jesse Barnes
2009-12-16 22:38 ` Krzysztof Halasa
2009-12-16 22:57 ` Dave Airlie
2009-12-16 23:19 ` Krzysztof Halasa
2009-12-14 18:36 ` Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2009-12-12 13:19 Jean Delvare
2009-12-12 20:10 ` Dave Airlie
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=aa541tsbrtanvarunansa3uh.1260654940760@email.android.com \
--to=jbarnes@virtuousgeek.org \
--cc=airlied@linux.ie \
--cc=jdelvare@suse.de \
--cc=jeffm@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®