From: Ben Elliston <bje@redhat.com>
To: sid@sources.redhat.com
Subject: sidcomp.audio test failure
Date: Thu, 12 Jul 2001 22:59:00 -0000 [thread overview]
Message-ID: <15182.36386.608754.484771@scooby.brisbane.redhat.com> (raw)
I tracked down a failure in the `linusraw.exp' test today. It's an
interesting one! The problem is that the audio component uses
non-blocking I/O to write the audio data to /dev/audio. On my older
Linux system with a cs4232 sound chipset, the test passes. On my
newer system with a cs46xx chipset, the driver has a maximum write
size limitation of 32kb.
I have confirmed all of this by reading the drivers/sound/audio.c
source from the kernel.
Basically, I think this test is bogus. It is a mistake to not
consider the possibility that the driver will return with any possible
value for the number of bytes written. Instead, the test should
perhaps keep polling the component until it has emptied its buffer and
*then* check that the tx-sample-count is the correct value. Thoughts?
In the meantime, I have marked the test as XFAIL. It might fail, it
might not -- that depends on your OS and your sound hardware. ;-(
Ben
next reply other threads:[~2001-07-12 22:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-12 22:59 Ben Elliston [this message]
[not found] <15182.36386.608754.484771.cygnus.project.sid@scooby.brisbane.redhat.com>
2001-07-13 4:53 ` Frank Ch. Eigler
2001-07-13 5:23 ` Ben Elliston
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=15182.36386.608754.484771@scooby.brisbane.redhat.com \
--to=bje@redhat.com \
--cc=sid@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).