public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Edgar Toernig <froese@gmx.de>
Cc: Bodo Eggert <7eggert@gmx.de>, Joseph Fannin <jfannin@gmail.com>,
	Stas Sergeev <stsp@aknet.ru>,
	dtor_core@ameritech.net,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/1] pc-speaker: add SND_SILENT
Date: Sat, 1 Apr 2006 08:11:42 +0200	[thread overview]
Message-ID: <20060401061142.GC7751@suse.cz> (raw)
In-Reply-To: <20060331230635.4a11e618.froese@gmx.de>

On Fri, Mar 31, 2006 at 11:06:35PM +0200, Edgar Toernig wrote:
> Vojtech Pavlik wrote:
> >
> > On Fri, Mar 31, 2006 at 01:07:34AM +0200, Edgar Toernig wrote:
> > >
> > > Latency is no problem.  I'm using a userspace daemon to emulate
> > > the console beeper for about 6 months now and it work's very well.
> > > 
> > > The daemon listens on /dev/input/eventX and when receiving a
> > 
> > It needs to use /dev/input/uinput, not eventX. SND_TONE events are not
> > sent to the event devices.
> 
> Well, I get them - stock 2.6.16.

Oh, yes, you're right. But still, this will only work if a speaker
device is present, so uinput is the right way to do it.

> > > Latency isn't noticable and memory footprint is small.
> > 
> > It needs to have the sample ready in memory and not swapped out. Then
> > the latency will be OK, but if it needs to read it in from the disk, it
> > may be very noticeable.
> 
> Yeah, if one ever cares one could mlock the samples, or (as I do) run
> without swap.  Fixing the 'air' latency of 3ms/m is harder though *g*

-- 
Vojtech Pavlik
Director SuSE Labs

  reply	other threads:[~2006-04-01  6:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5TCqf-E6-49@gated-at.bofh.it>
     [not found] ` <5TCqf-E6-51@gated-at.bofh.it>
     [not found]   ` <5TCqf-E6-53@gated-at.bofh.it>
     [not found]     ` <5TCqg-E6-55@gated-at.bofh.it>
     [not found]       ` <5TCqf-E6-47@gated-at.bofh.it>
2006-03-24 22:43         ` [patch 1/1] pc-speaker: add SND_SILENT Bodo Eggert
2006-03-26  9:52           ` Stas Sergeev
2006-03-26 11:24             ` Bodo Eggert
2006-03-26 18:46             ` Jan Engelhardt
2006-03-26 20:15               ` Kyle Moffett
2006-03-27 16:34             ` Dmitry Torokhov
2006-03-27 17:36               ` Stas Sergeev
2006-04-08  8:02               ` Stas Sergeev
2006-03-28 18:31             ` Joseph Fannin
2006-03-28 18:43               ` Bodo Eggert
2006-03-28 18:51                 ` Vojtech Pavlik
2006-03-30 23:07                   ` Edgar Toernig
2006-03-31  7:46                     ` Vojtech Pavlik
2006-03-31 21:06                       ` Edgar Toernig
2006-04-01  6:11                         ` Vojtech Pavlik [this message]
     [not found] <200603220652.k2M6qZgi020656@shell0.pdx.osdl.net>
     [not found] ` <d120d5000603221332n6a6f9208x5651dc9ec993f4bf@mail.gmail.com>
     [not found]   ` <4422318C.407@aknet.ru>
     [not found]     ` <d120d5000603230651p6b43aad9ocad1aa3c2b51b388@mail.gmail.com>
2006-03-23 18:03       ` Stas Sergeev
2006-03-23 18:12         ` Dmitry Torokhov
2006-03-23 18:31           ` Stas Sergeev
2006-03-23 18:47             ` Dmitry Torokhov
2006-03-23 19:34               ` Stas Sergeev
2006-03-23 20:36                 ` Dmitry Torokhov
2006-03-24  4:59                   ` Stas Sergeev

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=20060401061142.GC7751@suse.cz \
    --to=vojtech@suse.cz \
    --cc=7eggert@gmx.de \
    --cc=dtor_core@ameritech.net \
    --cc=froese@gmx.de \
    --cc=jfannin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stsp@aknet.ru \
    /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