All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Sophie Hamilton <sophie-alsa@theblob.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: Problems with safe API and snd-cs46xx
Date: Mon, 07 Sep 2009 14:32:39 +0200	[thread overview]
Message-ID: <s5hljkrrl3s.wl%tiwai@suse.de> (raw)
In-Reply-To: <a080dbc80909050524o7b00ceas46184b52fdac9cbc@mail.gmail.com>

At Sat, 5 Sep 2009 13:24:04 +0100,
Sophie Hamilton wrote:
> 
> Hi there,
> 
> I was pointed here by Audacious developers, who believe I've found a
> bug in the snd-cs46xx driver, which I use for my sound card (a Turtle
> Beach Santa Cruz, whose PCI ID is 1013:6003).
> 
> Audacious, as of version 2.1, uses the default period time offered by
> ALSA and limits itself to the "safe API" as per Lennart Poettering.

Hm, I don't know of "safe API"...

(snip)
> Most applications that I have seem to work properly with regards to
> audio, although I've heard that this is probably because ALSA's safe
> API isn't very well documented and as such most applications will not
> be using it, thus not exposing the bug in snd-cs46xx.
> 
> No information is output to dmesg when this happens, on either the
> Gentoo-patched 2.6.29 kernel, or the vanilla 2.6.30.5 kernel.
> 
> If you need any further information, please let me know!

A small test case, preferably a short C program just to reproduce
the problem would be really needed in such a case.  It's very hard to
guess what's going on and what is actually wrong in the driver only
from your problem description, because of no obvious debug logs.


thanks,

Takashi

  reply	other threads:[~2009-09-07 12:32 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-05 12:24 Problems with safe API and snd-cs46xx Sophie Hamilton
2009-09-07 12:32 ` Takashi Iwai [this message]
2009-09-07 13:29   ` Tony Vroon
2009-09-07 14:18     ` Raymond Yau
2009-09-07 14:25     ` Error with custom driver: playback drain error (DMA or IRQ trouble?) Stefan Schoenleitner
2009-09-07 15:01     ` Problems with safe API and snd-cs46xx Takashi Iwai
2009-09-07 15:07       ` Raymond Yau
2009-09-07 15:15         ` Takashi Iwai
2009-09-07 22:47       ` Lennart Poettering
2009-09-07 23:10         ` Sophie Hamilton
2009-09-08  6:29         ` Takashi Iwai
2009-09-08  7:46           ` Sophie Hamilton
2009-09-08  8:53             ` Takashi Iwai
2009-09-09 11:04               ` Takashi Iwai
2009-09-09 12:29                 ` Sophie Hamilton
2009-09-09 12:35                   ` Takashi Iwai
2009-09-09 14:07                     ` Lennart Poettering
2009-09-09 14:14                       ` Takashi Iwai
2009-09-09 14:27                         ` Lennart Poettering
2009-09-09 14:37                           ` Takashi Iwai
2009-09-10  8:47                             ` Raymond Yau
2009-09-08 13:38           ` Lennart Poettering
2009-09-08 14:42             ` Takashi Iwai
2009-09-09  2:18               ` Raymond Yau
2009-09-07 15:02   ` Sophie Hamilton
2009-09-07 17:04     ` Sophie Hamilton
2009-09-07 17:27       ` Takashi Iwai
2009-09-07 19:06         ` Sophie Hamilton
2009-09-08  6:38           ` Takashi Iwai
2009-09-08  8:19             ` Sophie Hamilton
2009-09-08  9:03               ` Takashi Iwai
2009-09-08 13:18               ` Raymond Yau
2009-09-08 13:21                 ` 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=s5hljkrrl3s.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=sophie-alsa@theblob.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.