From: Takashi Iwai <tiwai@suse.de>
To: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
Cc: manuel.jander@mat.utfsm.cl, alsa-devel@lists.sourceforge.net
Subject: Re: Aureal Vortex PATCH [Fwd: via workaround error]
Date: Mon, 12 Jan 2004 19:23:17 +0100 [thread overview]
Message-ID: <s5hbrp9auwa.wl@alsa2.suse.de> (raw)
In-Reply-To: <4002E295.3050001@gmx.at>
At Mon, 12 Jan 2004 19:08:21 +0100,
Wilfried Weissmann wrote:
>
> [1 <text/plain; us-ascii (7bit)>]
> Takashi Iwai wrote:
> > At Fri, 09 Jan 2004 23:04:49 -0400,
> > Manuel Jander wrote:
> >
> >>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...
> >
> >
> > i didn't receive the VIA workaround patch itself yet.
> > could you send the whole patch?
>
> here we go...
thanks!
> +static void __devinit snd_vortex_workaround(struct pci_dev *vortex, int fix) {
> + struct pci_dev *via=NULL;
> + /* autodetect if workarounds are required */
> + while( (via = pci_find_device(PCI_VENDOR_ID_VIA,
> + PCI_DEVICE_ID_VIA_8365_1, via)) ) {
> + if(fix == 255) {
> + printk(KERN_INFO CARD_NAME
> + ": detected VIA KT133/KM133. activating workaround...\n");
> + fix = 3; // do latency and via bridge workaround
> + }
> + break;
> + }
i think "if" is enough in the above.
> +
> + int rc;
gcc-2.9.x won't accept this.
i applied the fixed version to cvs. please check it later.
could you also provide the patch to INSTALL (document) file?
thanks,
Takashi
-------------------------------------------------------
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 prev parent reply other threads:[~2004-01-12 18:23 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 [this message]
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=s5hbrp9auwa.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=Wilfried.Weissmann@gmx.at \
--cc=alsa-devel@lists.sourceforge.net \
--cc=manuel.jander@mat.utfsm.cl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.