From: Stas Sergeev <stsp@aknet.ru>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] add input_enable_device()
Date: Thu, 18 May 2006 08:10:00 +0400 [thread overview]
Message-ID: <446BF398.80507@aknet.ru> (raw)
In-Reply-To: <20060517194757.6566.qmail@web81101.mail.mud.yahoo.com>
Dmitry Torokhov wrote:
>> Why does it have the INPUT_DEVICE_ID_MATCH_BUS after all?
> For userspace benefits.
How exactly does the userspace benefit from the
INPUT_DEVICE_ID_MATCH_BUS thing?
And, by the way, why doesn't the input have the
capability of disabling/enabling the device?
> While you are fine with
> disabling beeps while music is playing otherpeoplr might still want
> to hear them.
The only possibility to do this, was to have the grabbing
capability *in input layer*, which you already rejected too.
With this, it was possible to have such a behaviour run-time
configurable, but now my best bet would be to resort to the
Kconfig games, making a note for users that the uinput is now
an only possibility to route the terminal beeps to the snd-pcsp.
next prev parent reply other threads:[~2006-05-18 4:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060517124450.84547.qmail@web81111.mail.mud.yahoo.com>
2006-05-17 17:10 ` [patch] add input_enable_device() Stas Sergeev
2006-05-17 19:47 ` Dmitry Torokhov
2006-05-18 4:10 ` Stas Sergeev [this message]
2006-05-18 4:31 ` Dmitry Torokhov
2006-05-18 4:54 ` Stas Sergeev
2006-05-18 12:29 ` Dmitry Torokhov
2006-05-18 17:57 ` Stas Sergeev
[not found] <44670446.7080409@aknet.ru>
[not found] ` <20060515143119.54b5aff8.akpm@osdl.org>
2006-05-16 16:00 ` Stas Sergeev
2006-05-16 16:03 ` Andrew Morton
2006-05-16 16:29 ` Stas Sergeev
2006-05-16 16:44 ` Chase Venters
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=446BF398.80507@aknet.ru \
--to=stsp@aknet.ru \
--cc=dtor_core@ameritech.net \
--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