qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: malc <malc@pulsesoft.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Sound & Win98
Date: Mon, 26 Jul 2004 09:10:05 +0000 (UTC)	[thread overview]
Message-ID: <Pine.LNX.4.55.0407260907490.598@home.oyster.ru> (raw)
In-Reply-To: <200407251656.47811.menola@sbcglobal.net>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 806 bytes --]

On Sun, 25 Jul 2004, Joe Menola wrote:

> > Thank you for this detailed bug report.
>
> My pleasure.
>
> > Following patch (which must be applied after qemu-0.6.0-6_aqemu.patch.gz
> > will definitely workaround 1st problem and might help with 2nd.
>
> I copied your text to file sb-sub.patch, but fudged things some how.
> $ patch -p1 < sb-sub.patch
> patch: **** Only garbage was found in the patch input.

Let's try that again:
$ cd /cvs/qemu
$ patch </path/to/patch/oss.c.patch

>
> >
> > It would be interesting to know if "Unknown error 2996" goes away if
> > vanilla OSS/ALSA is used.
>
> By that you mean disable arts?

Yes.

> >
> > P.S. The only missing information is the name of the soundcard.
>
> Physical soundcard?  =SB Live 5.1

Ok. SB Live 5.1 + arts. Thanks.

-- 
mailto:malc@pulsesoft.com

[-- Attachment #2: Type: TEXT/PLAIN, Size: 786 bytes --]

--- oss.c.orig	Mon Jul 26 01:00:48 2004
+++ oss.c	Mon Jul 26 01:04:45 2004
@@ -796,12 +796,13 @@
         play = MIN (left, bytes);
         written = write (s->fd, (void *) ((uint32_t) s->buf + s->rpos), play);
 
-        if (-1 == written) {
+        if (written < 0) {
             if (EAGAIN == errno || EINTR == errno) {
                 return;
             }
             else {
-                ERRFail ("write audio");
+	        fprintf (stderr, "write failed, errno=%d\n", errno);
+		return;
             }
         }
 
@@ -895,6 +896,9 @@
             elapsed += s->leftover;
         }
     }
+
+    if (elapsed < 1024)
+        return 0;
 
     if (elapsed > free) {
         lwarn ("audio can not keep up elapsed %d free %d\n", elapsed, free);

  reply	other threads:[~2004-07-26  5:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-25 10:25 [Qemu-devel] Sound & Win98 Nicolas Wu
2004-07-25 19:55 ` Joe Menola
2004-07-25 23:15   ` Lindsay Mathieson
2004-07-26  1:06   ` malc
2004-07-25 21:56     ` Joe Menola
2004-07-26  9:10       ` malc [this message]
2004-07-26  6:18         ` Lindsay Mathieson
2004-07-26  6:24           ` Lindsay Mathieson
2004-07-26 10:38         ` Joe Menola
2004-07-26 21:06           ` malc
2004-07-26 21:51             ` Joe Menola
2004-07-26 22:29               ` Laurent Amon
2004-07-26 23:26                 ` Joe Menola
2004-07-27  6:23                   ` Laurent Amon
2004-07-27  2:41               ` malc
2004-07-26 23:29                 ` Joe Menola
2004-07-25 23:22     ` Lindsay Mathieson
2004-07-26  1:58       ` Jim C. Brown
2004-07-26  3:16       ` Joe Menola
2004-07-30 10:59     ` Johannes Martin
2004-07-30 17:13       ` malc
2004-08-02  9:01       ` Johannes Martin
  -- strict thread matches above, loose matches on Subject: below --
2004-07-24 22:56 Lindsay Mathieson
2004-07-24 23:32 ` Joe Menola
2004-07-25  5:23   ` malc
2004-07-25  2:10     ` Lindsay Mathieson
2004-07-25  2:18     ` Joe Menola

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=Pine.LNX.4.55.0407260907490.598@home.oyster.ru \
    --to=malc@pulsesoft.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).