All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raymond <rayau@netvigator.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net,
	Manuel Jander <manuel.jander@gmail.com>,
	openvortex-dev@nongnu.org, xslaby@fi.muni.cz
Subject: Re : CVS: alsa-kernel/pci/au88x0 au88x0.c,1.18,1.19
Date: Sat, 10 Sep 2005 13:11:02 +0800	[thread overview]
Message-ID: <43226AE6.3060502@netvigator.com> (raw)

Refer to the recent change in CVS

http://cvs.sourceforge.net/viewcvs.py/alsa/alsa-kernel/pci/au88x0/au88x0.c?r1=1.18&r2=1.19

The au88x0 chips have known conflict with the following PCI devices

1) PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_8365_1
2) PCI_VENDOR_ID_VIA, PCI_EVICE_ID_VIA_82C598_1
3) PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_FE_GATE_7007

The function of snd_vortex_workaround() is to detect the presence of
these devices and  perform vortex_fix_latency() and
vortex_fix_agp_bridge() automatically.

http://sourceforge.net/mailarchive/forum.php?thread_id=8137444&forum_id=33141

What is the difference between pci_find_device() and pci_get_device() ?

What is the purpose of adding pci_dev_put(via); at the end of
snd_vortex_workaround() ?






-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

             reply	other threads:[~2005-09-10  5:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-10  5:11 Raymond [this message]
2005-09-10  7:57 ` Re : CVS: alsa-kernel/pci/au88x0 au88x0.c,1.18,1.19 Jiri Slaby
2005-09-10  9:56   ` Jiri Slaby
2005-09-12 17:26   ` Raymond

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=43226AE6.3060502@netvigator.com \
    --to=rayau@netvigator.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=manuel.jander@gmail.com \
    --cc=openvortex-dev@nongnu.org \
    --cc=tiwai@suse.de \
    --cc=xslaby@fi.muni.cz \
    /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.