From: Manuel Jander <manuel.jander@mat.utfsm.cl>
To: Alsa Devel list <alsa-devel@lists.sourceforge.net>
Subject: Aureal Vortex PATCH [Fwd: via workaround error]
Date: Fri, 09 Jan 2004 23:04:49 -0400 [thread overview]
Message-ID: <1073703888.4419.2.camel@localhost> (raw)
Please apply to CVS. Thanks
-----Forwarded Message-----
From: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
To: openvortex-dev@nongnu.org, manuel.jander@mat.utfsm.cl
Subject: via workaround error
Date: Fri, 09 Jan 2004 20:16:01 +0100
i made a stupid error when i wrote the via workaround patch. the pci
latency for the vortex was still set to 0xff when using autodetection
and no via chipset was found. i discovered this after i exchanged my
motherboard from a via kt133 to a sis 735. the fix is attached. the bug
should not have caused any troubles but it is just not right...
bye,
wilfried
________________________________________________________________________
--- alsa-driver-1.0.0rc1-ww1/pci/au88x0/au88x0.c 2003-12-03 01:01:19.000000000 +0100
+++ alsa-driver-1.0.0rc1-ww2/pci/au88x0/au88x0.c 2004-01-09 20:01:32.000000000 +0100
@@ -77,6 +77,10 @@ static void __devinit snd_vortex_workaro
}
break;
}
+
+ /* do not do anything if autodetection was enabled and found no VIA */
+ if(fix == 255)
+ return;
int rc;
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
next reply other threads:[~2004-01-10 3:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 3:04 Manuel Jander [this message]
2004-01-12 14:00 ` Aureal Vortex PATCH [Fwd: via workaround error] Takashi Iwai
2004-01-12 18:08 ` Wilfried Weissmann
2004-01-12 18:23 ` Takashi Iwai
2004-01-13 19:47 ` Wilfried Weissmann
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=1073703888.4419.2.camel@localhost \
--to=manuel.jander@mat.utfsm.cl \
--cc=alsa-devel@lists.sourceforge.net \
/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