mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: Richard Kennedy <richard@rsk.demon.co.uk>
Cc: lkml <linux-kernel@vger.kernel.org>,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	linux-input@vger.kernel.org
Subject: Re: special HID & Kconfig: odd behavior in gconfig
Date: Sun, 13 Sep 2009 17:59:14 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.0909131758280.17028@wotan.suse.de> (raw)
In-Reply-To: <1252681027.2282.23.camel@castor>

On Fri, 11 Sep 2009, Richard Kennedy wrote:

> I use gconfig & and cannot turn off any of the special HID devices.
> 
> the Kconfig for them all have the same pattern e.g.
> 
> config HID_DRAGONRISE
> 	tristate "DragonRise Inc. support" if EMBEDDED
> 	depends on USB_HID
> 	default !EMBEDDED
> 
> The 'if EMBEDDED' on the tristate line seems to confuse gconfig and it
> sets them all to m & does not let me set them to N. I'm building this on
> a standard desktop machine.
> 
> Any idea what the intention of this was? or can we just remove the if
> embedded part?

Hi Richard,

actually this question has been raised by several people in the past
already. Copy/pasting the latest reply I have sent on this topic

===

mostly this is because we don't want to bother users with asking for every 
single quirky device/vendor, as there are unfortunately a lot of them. 
Usually compiling everything in doesn't waste runtime footprint (the 
modules don't get loaded unless needed), and they don't cost too much disk 
space either. And if you really want to disable them, CONFIG_EMBEDDED 
allows you to do that.

Please see last paragraph on

        http://lkml.org/lkml/2008/10/14/284

===

-- 
Jiri Kosina
SUSE Labs, Novell Inc.

      reply	other threads:[~2009-09-13 15:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11 14:57 Richard Kennedy
2009-09-13 15:59 ` Jiri Kosina [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=alpine.LNX.2.00.0909131758280.17028@wotan.suse.de \
    --to=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard@rsk.demon.co.uk \
    /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®