From: "Tais M. Hansen" <tais.hansen@osd.dk>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Re: [Alsa-user] Upgrade problems -addendum
Date: Fri, 24 Jan 2003 15:12:13 +0100 [thread overview]
Message-ID: <200301241512.17848.tais.hansen@osd.dk> (raw)
In-Reply-To: <s5hd6mmptdh.wl@alsa2.suse.de>
[-- Attachment #1: Type: text/plain, Size: 2013 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 24 January 2003 14:30, Takashi Iwai wrote:
> > Same deal as before, another 3 files filled with debug output. Good luck.
> > :)
> it seems that we need to use CURRPTR always on your chip.
> i guess this depends on the board, how reliable IDX register is.
Need any specific info about the board? Chip? I saw some talks about the
ALC650 chip in another thread on this list and alsamixer claims I've got such
a chip.
> if the attached new patch works, i'll add a module option to enable
> this behavior.
> good luck for you, too :)
Thanks. Maybe we should exchange good luck more often. Seems like you worked
some magic here. :)
Ogg123 now plays but there's a lot of pops, clicks and stuttering. Log output
were produced in both syslog and debug. Attached as allways.
Aplay played as always. I think I heard pops here and there but it wasn't
much. Log output from debug attached.
Artsd started as supposed to with a single pop. Noatun seemed to play without
any noticeable weirdness. No pops etc. Log output from debug attached.
- --
Regards,
Tais M. Hansen
OSD
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
iQIVAwUBPjFJwIIvLOJqwYc4AQJUkRAAjIJ66U1Fb2HDWHQcqRh0BnAIJKZaIki3
ky+IkXkJ32YqznaiO88Cv6GlRJjJAfES8IyRrUZB8WT0LA79mKGSQyoS5xoMK6MW
KsqPPHf/h1o3QCKa/rY8OH0oPUzD5PvfGqU1Iyk3uUTjtaQYm+4B/V7wpQjfnRbb
5sumdqo8oWchgzoKqeY17bdPE7lAMxYoWeRglIPMI6N1I/iyJNAONnfHNMFVH1FE
uZQ3EKipd7qMw8RZHA2+C29xTU3rK4aMqRMqsBHHNBXMzNsNIRuGenSYQAynHeCY
U0UzPBirqZKCOWEJuBWjhEWhAk1CCnBb1vsM1MVEJ0e47RfIF9HL3kHK4Eiwk301
fHOIGR+x9iAO/21en8oVzEj6sNdWGMMPXV1U+byJbe/C6I7nRBQCBMZDdbw2/haU
uvhzMoBihW7EwLoWlMFCXbseX3vcHf8lmSLyh39M+aK2FcMnYiFGE7gp0L84NS2Q
mnh6b9CFDPlffGET9+DULqZqv/clYsqHLOtT7ECjLyb3zcm6rGw+pU3wKNPcRtpW
GL0saHyIy1fhU6Z+LDSPYlcBDl0+AtjeGhNTG44UmrfW92SM1jJb0f52rRe0zelq
hih9SE6meCIHYjBk9/LcCYYAdBW9sybBPqjr+ywskbNrLH87TrfYftpUWXAq1sar
einpLW5cIcw=
=K4LD
-----END PGP SIGNATURE-----
[-- Attachment #2: alsa-aplay-test7.txt.gz --]
[-- Type: application/x-gzip, Size: 166 bytes --]
[-- Attachment #3: alsa-artsd-test7.txt.gz --]
[-- Type: application/x-gzip, Size: 1441 bytes --]
[-- Attachment #4: alsa-ogg123-test7.txt.gz --]
[-- Type: application/x-gzip, Size: 1006 bytes --]
next prev parent reply other threads:[~2003-01-24 14:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200301221234.33054.tais.hansen@osd.dk>
[not found] ` <200301221543.52285.tais.hansen@osd.dk>
[not found] ` <s5hznpt1bn2.wl@alsa2.suse.de>
[not found] ` <200301221647.05780.tais.hansen@osd.dk>
2003-01-22 16:23 ` [Alsa-user] Upgrade problems -addendum Takashi Iwai
2003-01-23 0:35 ` Tais M. Hansen
2003-01-23 10:03 ` Takashi Iwai
2003-01-23 11:15 ` Tais M. Hansen
2003-01-23 11:46 ` Takashi Iwai
2003-01-23 12:36 ` Tais M. Hansen
2003-01-23 15:08 ` Takashi Iwai
2003-01-23 17:50 ` Tais M. Hansen
2003-01-23 18:07 ` Takashi Iwai
2003-01-23 18:43 ` Tais M. Hansen
2003-01-24 9:12 ` Takashi Iwai
2003-01-24 12:41 ` Tais M. Hansen
2003-01-24 13:30 ` Takashi Iwai
2003-01-24 14:12 ` Tais M. Hansen [this message]
2003-01-24 15:45 ` Takashi Iwai
2003-01-24 16:40 ` Tais M. Hansen
2003-01-24 17:08 ` Takashi Iwai
2003-01-24 21:24 ` Tais M. Hansen
2003-01-27 10:42 ` Takashi Iwai
2003-01-27 14:42 ` Tais M. Hansen
2003-01-27 15:15 ` Takashi Iwai
2003-01-27 17:01 ` Tais M. Hansen
2003-01-27 17:27 ` Takashi Iwai
2003-01-28 0:43 ` VIA823x testing Tais M. Hansen
2003-01-28 9:31 ` Takashi Iwai
2003-01-28 13:25 ` Tais M. Hansen
2003-01-28 16:21 ` Takashi Iwai
2003-01-28 23:19 ` Tais M. Hansen
2003-01-24 16:42 ` Re: [Alsa-user] Upgrade problems -addendum Tais M. Hansen
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=200301241512.17848.tais.hansen@osd.dk \
--to=tais.hansen@osd.dk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
/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