All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lennart Poettering <mznyfn@0pointer.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Status of snd_pcm_rewind()
Date: Mon, 7 Jan 2008 16:14:58 +0100	[thread overview]
Message-ID: <20080107151458.GB14386@tango.0pointer.de> (raw)
In-Reply-To: <s5hmyrh91bx.wl%tiwai@suse.de>

On Mon, 07.01.08 15:06, Takashi Iwai (tiwai@suse.de) wrote:

> 
> At Sat, 22 Dec 2007 19:33:01 +0100,
> Lennart Poettering wrote:
> > 
> > Hi!
> > 
> > What's the status of snd_pcm_rewind()? Is it available on all devices?
> 
> It should work on all "hw" PCM, but not via every plugin.  The
> functionality is basically in the PCM core level, independent from
> the lowlevel driver implementation.
> 
> dmix and dshare don't work (unimplemented).  The other plugins should
> work, though.
> 
> > I assume not (at least dmix doesn't...). But I guess I can safely
> > assume it is available when mmap is used? Is there any API function to
> > test if it is available?
> 
> No, unfortunately.  A self-test?

Ii assume th "No" is a response to the question if there was any API
function to test whether it is available, right?

What's the answer to the question that I can safely assume that it is
available when mmap is used?

May I suggest adding an API function that can be used to detect
whether _rewind() functionality is available?

Lennart

-- 
Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net         ICQ# 11060553
http://0pointer.net/lennart/           GnuPG 0x1A015CC4

  reply	other threads:[~2008-01-07 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-22 18:33 Status of snd_pcm_rewind() Lennart Poettering
2008-01-07 14:06 ` Takashi Iwai
2008-01-07 15:14   ` Lennart Poettering [this message]
2008-01-07 15:24     ` Takashi Iwai

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=20080107151458.GB14386@tango.0pointer.de \
    --to=mznyfn@0pointer.de \
    --cc=alsa-devel@alsa-project.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.