All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@aknet.ru>
To: Adrian Bunk <bunk@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: [patch] snd-pcsp: relax dependancy on CONFIG_INPUT
Date: Thu, 08 May 2008 21:53:25 +0400	[thread overview]
Message-ID: <48233E15.6000206@aknet.ru> (raw)
In-Reply-To: <20080508173552.GA22887@cs181133002.pp.htv.fi>

Hello.

Adrian Bunk wrote:
> Sorry for the silly question, but are there serious usecases where 
> people in very space limited environments and with CONFIG_INPUT=n
> want PC-Speaker support?
I don't know, but there might be
someone who wants the PCM support
from pc-speaker, and hates the beeps
at the same time. So they can disable
it forever. :)
I also want to resolve the conflict
with INPUT_PCSPKR somehow. Making the
input part of snd-pcsp optional looks
like the first step to me. It became
known to me that loading multiple
drivers for the same device will be
possible in the future. I want to get
everything ready for loading pcspkr
and snd-pcsp together.
And overall, having snd-pcsp to depend
on CONFIG_INPUT only because it can do
a console beeps as a bonus, looks ill-
behaved to me. So I just propose that
patch as a small logical correction
and cleanup, rather than a new feature.

  reply	other threads:[~2008-05-08 17:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <482316B8.5080200@aknet.ru>
     [not found] ` <s5h4p98yfof.wl%tiwai@suse.de>
2008-05-08 17:31   ` [patch] snd-pcsp: relax dependancy on CONFIG_INPUT Stas Sergeev
2008-05-08 17:35     ` Adrian Bunk
2008-05-08 17:53       ` Stas Sergeev [this message]
2008-05-08 18:25       ` Stas Sergeev
2008-05-08 22:17         ` Adrian Bunk
2008-05-08 22:38           ` Stas Sergeev
2008-05-08 22:48             ` Adrian Bunk

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=48233E15.6000206@aknet.ru \
    --to=stsp@aknet.ru \
    --cc=alsa-devel@alsa-project.org \
    --cc=bunk@kernel.org \
    --cc=tiwai@suse.de \
    /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.