From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - lib 0000897]: test/timer.c malfunctions with snd-rtctimer
Date: Fri, 11 Mar 2005 09:42:46 +0100 [thread overview]
Message-ID: <fa899faa0a8306ece3822d33dbca9cac@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=897>
======================================================================
Reported By: phunge
Assigned To:
======================================================================
Project: ALSA - lib
Issue ID: 897
Category: timer
Reproducibility: always
Severity: minor
Priority: normal
Status: new
======================================================================
Date Submitted: 02-09-2005 15:45 CET
Last Modified: 03-11-2005 09:42 CET
======================================================================
Summary: test/timer.c malfunctions with snd-rtctimer
Description:
I'm trying to learn how to use the ALSA timer API for getting a hi-res
interrupt in a program of mine. When I compile test/timer.c, it runs
correctly using the default system timer. However, when I try to specify
the RTC timer by modprobing snd-rtctimer and running
./timer class=1 sclass=0 card=0 device=1 subdevice=0
the program fails (output under "additional information").
/dev/rtc is readable and I can run the RTC test from
http://stommel.tamu.edu/~baum/linux-kernel/rtc.txt
so I think the problem is in alsa.
======================================================================
----------------------------------------------------------------------
phunge - 02-16-05 12:02
----------------------------------------------------------------------
I also see the same behavior when using 2.6.8.1 compiled from kernel.org.
----------------------------------------------------------------------
Clemens Ladisch - 03-11-05 09:42
----------------------------------------------------------------------
Works fine with 2.6.11, too.
Issue History
Date Modified Username Field Change
======================================================================
02-09-05 15:45 phunge New Issue
02-14-05 10:47 Clemens LadischNote Added: 0003587
02-14-05 11:35 phunge Note Added: 0003589
02-16-05 12:02 phunge Note Added: 0003622
03-11-05 09:42 Clemens LadischNote Added: 0003882
======================================================================
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-03-11 8:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 8:42 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-09 11:46 [ALSA - lib 0000897]: test/timer.c malfunctions with snd-rtctimer bugtrack
2005-05-30 11:30 bugtrack
2005-02-16 11:02 bugtrack
2005-02-14 10:35 bugtrack
2005-02-14 9:47 bugtrack
2005-02-09 14:45 bugtrack
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=fa899faa0a8306ece3822d33dbca9cac@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox