Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
To: Takashi Iwai <tiwai@suse.de>
Cc: manuel.jander@mat.utfsm.cl, alsa-devel@lists.sourceforge.net
Subject: Re: Aureal Vortex PATCH [Fwd: via workaround error]
Date: Tue, 13 Jan 2004 20:47:13 +0100	[thread overview]
Message-ID: <40044B41.8020707@gmx.at> (raw)
In-Reply-To: <s5hbrp9auwa.wl@alsa2.suse.de>

[-- Attachment #1: Type: text/plain, Size: 283 bytes --]

Takashi Iwai wrote:
[snip]
> i applied the fixed version to cvs.  please check it later.

the changes are fine.

> 
> could you also provide the patch to INSTALL (document) file?

the patch is attached (against current alsa CVS)...

> 
> 
> thanks,
> 
> Takashi

greetings,
wilfried

[-- Attachment #2: alsa-1.0.1-aureal-via-quirks-docs.patch --]
[-- Type: text/plain, Size: 791 bytes --]

Index: INSTALL
===================================================================
RCS file: /cvsroot/alsa/alsa-driver/INSTALL,v
retrieving revision 1.154
diff -u -r1.154 INSTALL
--- INSTALL	12 Jan 2004 14:40:21 -0000	1.154
+++ INSTALL	13 Jan 2004 19:39:29 -0000
@@ -261,6 +261,14 @@
            control correctly. If you have problems regarding this, try
            another ALSA compliant mixer (alsamixer works).
 
+    pcifix	- Control PCI workarounds
+		  0 = Disable all workarounds
+		  1 = Force the PCI latency of the Aureal card to 0xff
+		  2 = Force the Extend PCI#2 Internal Master for Efficient
+		      Handling of Dummy Requests on the VIA KT133 AGP Bridge
+		  3 = Force both settings
+		  255 = Autodetect what is required (default)
+
 
 Trouble Shooting
 ================

      reply	other threads:[~2004-01-13 19:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-10  3:04 Aureal Vortex PATCH [Fwd: via workaround error] Manuel Jander
2004-01-12 14:00 ` Takashi Iwai
2004-01-12 18:08   ` Wilfried Weissmann
2004-01-12 18:23     ` Takashi Iwai
2004-01-13 19:47       ` Wilfried Weissmann [this message]

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=40044B41.8020707@gmx.at \
    --to=wilfried.weissmann@gmx.at \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=manuel.jander@mat.utfsm.cl \
    --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