From: Jean Delvare <jdelvare@suse.de>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Michal Marek <mmarek@suse.cz>,
linux-input@vger.kernel.org,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: Dependencies in the HID subsystem
Date: Thu, 13 Jun 2013 09:11:46 +0200 [thread overview]
Message-ID: <1371107506.4289.25.camel@chaos.site> (raw)
In-Reply-To: <alpine.LNX.2.00.1305292245090.30576@pobox.suse.cz>
Hi Jiri,
Sorry for the late reply.
Le Wednesday 29 May 2013 à 22:52 +0200, Jiri Kosina a écrit :
> On Wed, 29 May 2013, Jean Delvare wrote:
>
> > I am worried and confused by some Kconfig dependencies in the HID
> > subsystem.
> >
> > There are 11 HID device drivers which are defined in drivers/hid/Kconfig
> > with:
> >
> > tristate "..." if EXPERT
> > default !EXPERT
> >
> > Unless EXPERT is enabled (and that's not the default), these driver
> > entries are hidden and automatically selected. If CONFIG_HID=m, they are
> > selected as modules. If CONFIG_HID=y, they are built into the kernel. So
> > it is impossible to have CONFIG_HID=y and build these device drivers as
> > modules - as device drivers typically are.
> >
> > I would like to understand the reasoning behind this complexity. What is
> > so special about these 11 drivers, that we can't just let the (kernel
> > configuring) user chose if he/she wants them and in what form?
>
> That's quite a old story with some history behind. Linus himself
> originally requested it, then much later asked the same question you did.
> See some background here:
>
> https://lkml.org/lkml/2010/5/20/227
This explains it all, thank you.
>> (...)
> > Put in short, I don't like the way things are today and would welcome
> > changes in this area.
>
> As things have changed a lot since 2.6.28, we can try to put things more
> in line now for 3.11 or so.
This is great news. Will it just happen, or is some contribution
expected from me? That's not my area, but if you want me to write some
patches or test things, just ask and I'll do my best.
Thanks,
--
Jean Delvare
Suse L3
--
To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-06-13 7:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 19:19 Dependencies in the HID subsystem Jean Delvare
2013-05-29 20:52 ` Jiri Kosina
2013-05-29 22:23 ` David Herrmann
2013-06-13 6:58 ` Jean Delvare
2013-06-13 7:11 ` Jean Delvare [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=1371107506.4289.25.camel@chaos.site \
--to=jdelvare@suse.de \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.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;
as well as URLs for NNTP newsgroup(s).