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: Fri, 17 Mar 2006 16:43:55 +0200 [thread overview]
Message-ID: <dvehv7$j9r$1@sea.gmane.org> (raw)
In-Reply-To: <20060317143303.GR20746@lug-owl.de>
Jan-Benedict Glaw wrote:
> Just for the records, it happens actually quite often that some little
> features / improvements of a chipset have bugs; from time to time,
> you'll see a BIOS update that doesn't really do more than switching
> off that feature. I guess that quite some of our quirks originate from
> looking at what a newer BIOS configures differently compared to an
> older version. Some instability can be fixed that way (though it's
> better to have a fix for such a bug inside the BIOS: this way, the fix
> is in place at the time the Linux kernel is loaded, so there's no way
> for it to eg. cause memory corruption between loading the kernel and
> issueing the quirks.)
I know, but in this case I got this answer:
" Dear Friend :
Thank you for contacting ASUS Customer Service.
My name is ZYC, and I would be assisting you today.
sorry ,due to chipset limitation ,
when you add a PCI AUDIO card to a board which use VIA VT8237 southbridge
controller ,
the built in AC97 audio will be disabled automaticly .
it is a chip limitation without way to fix ."
Meantime I tried the patch against the 2.6.13-15 kernel shipped with SuSE 10
(applied without errors), and altough I see
PCI: enabled onboard AC97/MC97 devices
in the logs, the onboard card doesn't appear in lspci.
I'm downloading the 2.6.16-rc6 kernel to try with that one. Mine is an
A8V-Deluxe, so I don't know why it didn't work. :-( I have the latest Asus
bios and verified that it is enabled in the BIOS (I know, it doesn't really
matter, but I mention here).
Andras
--
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org
next prev parent reply other threads:[~2006-03-17 14:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 19:27 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 [this message]
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='dvehv7$j9r$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome