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 21:57:56 +0400 [thread overview]
Message-ID: <446CB5A4.7090603@aknet.ru> (raw)
In-Reply-To: <20060518122944.66148.qmail@web81114.mail.mud.yahoo.com>
Dmitry Torokhov wrote:
> Yes, you are right. INPUT_DEVICE_ID_MATCH_BUS will not likely
> benefit anyone.
And according to the impression I've got, it should
therefore be removed, sure? :)
> Consider this: pcspkr is broken at the moment as it does not
> handle several simultaneous events well. If you fix it do behave
> properly with SND_TONE and SND_BELL arriving at the same time
> then adding hooks to the speaker code for snd-pcsp should be
> pretty easy. See?
I see the point but not the practicle solution. request_region()
won't work as the ports are already claimed by other drivers.
Resolving this inside pcspkr.c won't help snd-pcsp, as it will
add the dependancy if some internal API is used.
The real problem is that whereever I'll solve that, this will be
a hack, because normally two drivers should not compete for the
IO resourses, disable each other, race etc.
So I give it up. I'll just disable pcspkr in the Kconfig and
whoever wants both snd-pcsp and the beeps, will need to install
the user-space daemon which uses uinput. I have yet to find such
a daemon...
next prev parent reply other threads:[~2006-05-18 17:58 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
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 [this message]
[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=446CB5A4.7090603@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.