All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andras Mantia <amantia@kde.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 001/001] PCI: PCI quirk for Asus A8V and A8V Deluxe motherboards
Date: Sun, 19 Mar 2006 20:44:38 +0200	[thread overview]
Message-ID: <dvk8qa$l8o$1@sea.gmane.org> (raw)
In-Reply-To: yw1x3bhez3gu.fsf@agrajag.inprovide.com

Måns Rullgård wrote:

> It is the BIOS that disables the onboard sound if it detects a PCI
> sound card.  Chances are other vendors use different BIOS
> configurations that do not automatically disable things.  I don't know
> if messing with those bits might do something bad on another board.
> 

Yes, this might be a case, but you never know if ASUS engineers realize that
they can enable the board even if there is a PCI card and will include in
the next bios (as I wrote, they say it is impossible, but you never know).
So checking for ASUS will be wrong starting from that BIOS version.
When I first saw this bug on my system I searched a lot to see if I made a
wrong decision by buying ASUS and not another brand and everywhere on the
forums the same issue was described for other brands as well.

>From the code I would say that 
       pci_read_config_byte(dev, 0x50, &val);
       if (val & 0xc0) {

is the test if it's enabled by the bios or not, as after trying to enable
with 
pci_write_config_byte(dev, 0x50, val & (~0xc0));
it reads again the same byte and checks if the correct bits are enabled.

I see no harm here, but as I said I am not a hardware guy, just a desktop
programmer. ;-)

Andras

-- 
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org



  reply	other threads:[~2006-03-19 18:45 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
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 [this message]
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='dvk8qa$l8o$1@sea.gmane.org' \
    --to=amantia@kde.org \
    --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 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.