public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: bjd <bjdouma@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 001/001] PCI: PCI quirk for Asus A8V and A8V Deluxe motherboards
Date: Sun, 5 Mar 2006 14:34:22 -0500	[thread overview]
Message-ID: <20060305193422.GA18593@redhat.com> (raw)
In-Reply-To: <20060305192709.GA3789@skyscraper.unix9.prv>

On Sun, Mar 05, 2006 at 08:27:09PM +0100, bjd wrote:

 > +static void __init asus_hides_ac97_lpc(struct pci_dev *dev)
 > +{
 > +	u8 val;
 > +	int asus_hides_ac97 = 0;
 > +
 > +	if (likely(dev->subsystem_vendor == PCI_VENDOR_ID_ASUSTEK)) {
 > +		if (dev->device == PCI_DEVICE_ID_VIA_8237)
 > +			asus_hides_ac97 = 1;
 > +	}
 > +
 > +	if (!asus_hides_ac97)
 > +		return;

Why likely ?  It's just as unlikely to be an ASUS.
Also, why not just ..

	if (dev->subsystem_vendor != PCI_VENDOR_ID_ASUSTEK)
		return;
	if (dev->device != PCI_DEVICE_ID_VIA_8237)
		return;

and lose the asus_hides_ac97 var completely?

Is this true of every ASUS board that has an 8237 ?
Does it actually remove the enable/disable ac97 feature from the BIOS,
or just reset it to disabled ?

 > +	pci_read_config_byte(dev, 0x50, &val);
 > +	if (val & 0xc0) {
 > +		pci_write_config_byte(dev, 0x50, val & (~0xc0));
 > +		pci_read_config_byte(dev, 0x50, &val);
 > +		if (val & 0xc0)
 > +			printk(KERN_INFO "PCI: onboard AC97/MC97 devices continue to
 > play 'hide and seek'! 0x%x\n", val);

How often does this trigger ?
The message could be a little more end-user friendly too
"Failed to enable onboard AC97/MC97 devices"

		Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2006-03-05 19:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-05 19:27 [PATCH 001/001] PCI: PCI quirk for Asus A8V and A8V Deluxe motherboards bjd
2006-03-05 19:34 ` Dave Jones [this message]
2006-03-05 20:32 ` Lee Revell
2006-03-06  9:34   ` Jan-Benedict Glaw
2006-03-05 21:24 ` Måns Rullgård
2006-03-11 19:49   ` Måns Rullgård
2006-03-17 10:38 ` Andras Mantia
2006-03-17 14:33   ` Jan-Benedict Glaw
2006-03-17 14:43     ` Andras Mantia
2006-03-17 14:49       ` Jan-Benedict Glaw
2006-03-17 18:18         ` Andras Mantia
2006-03-17 19:29           ` Måns Rullgård
2006-03-18 14:01             ` Andras Mantia
2006-03-18 14:23               ` Måns Rullgård
2006-03-18 15:00                 ` Andras Mantia
2006-03-18 15:58                   ` Måns Rullgård
2006-03-19 10:38                     ` Andras Mantia
2006-03-19 12:58                       ` Måns Rullgård
2006-03-19 15:11                         ` Andras Mantia
2006-03-19 16:35                           ` Måns Rullgård
2006-03-19 17:38                             ` Andras Mantia
2006-03-19 18:03                               ` Måns Rullgård
2006-03-19 18:18                                 ` Andras Mantia
2006-03-19 18:36                                   ` Måns Rullgård
2006-03-19 18:44                                     ` Andras Mantia
2006-03-17 19:15       ` Måns Rullgård
  -- strict thread matches above, loose matches on Subject: below --
2006-03-05 12:37 Bauke jan Douma
2006-02-12  2:22 bjd

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=20060305193422.GA18593@redhat.com \
    --to=davej@redhat.com \
    --cc=bjdouma@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    /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