From: Jon <jcb@niluge.net>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Giuliano Pochini <pochini@shiny.it>,
Ryan Underwood <nemesis-lists@icequake.net>,
alsa-devel@lists.sourceforge.net
Subject: Re: Unexpected hw_pointer value
Date: Tue, 7 Oct 2003 00:33:44 +0200 [thread overview]
Message-ID: <20031006223344.GA589@zeus.homenet> (raw)
In-Reply-To: <Pine.LNX.4.53.0310061419200.1641@pnote.perex-int.cz>
On Monday 06 October, 2003 � 03:36:32PM +0200, Jaroslav Kysela wrote:
> We added these sanity checks for debugging purposes, but if they occur too
> much, there's something bad with driver or hardware.
>
> Basically, we have only information from last interrupt position and the
> actual position in the ring buffer. We need to determine the new
> "absolute" position. To detect the wrap point, we compute the delta value
> for the new and old position and if delta is greater than buffer_size / 2,
> we correct the new position by adding buffer_size. Otherwise we take value
> as error, because we ask driver to acknowledge interrupts after
> period_size not before. Note that some interrupt might be lost.
>
> Jaroslav
my hardware seems really bad : ES1983S Maestro-3i on a dell c600.
i experience lots of hardware freeze (bios does not respond) caused the
driver/card with oss or alsa.
i'm kind of desperate with my sound card :(
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-10-06 22:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-04 21:12 Unexpected hw_pointer value Jon
2003-10-04 21:58 ` Ryan Underwood
2003-10-05 14:26 ` Giuliano Pochini
2003-10-06 13:36 ` Jaroslav Kysela
2003-10-06 22:33 ` Jon [this message]
2003-10-06 11:07 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2003-08-07 23:05 Giuliano Pochini
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=20031006223344.GA589@zeus.homenet \
--to=jcb@niluge.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=nemesis-lists@icequake.net \
--cc=perex@suse.cz \
--cc=pochini@shiny.it \
/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