From: Eric Valette <eric.valette@free.fr>
To: Dominik Brodowski <linux@dominikbrodowski.de>
Cc: "Li, Shaohua" <shaohua.li@intel.com>,
Karol Kozimor <sziwan@hell.org.pl>,
"Brown, Len" <len.brown@intel.com>,
"Wang, Zhenyu Z" <zhenyu.z.wang@intel.com>,
Andrew Morton <akpm@osdl.org>, Greg KH <greg@kroah.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8.1-mm1 and Asus L3C : problematic change found, can be reverted. Real fix still missing
Date: Sun, 29 Aug 2004 15:50:07 +0200 [thread overview]
Message-ID: <4131DF0F.5040306@free.fr> (raw)
In-Reply-To: <20040829130423.GD17032@dominikbrodowski.de>
Dominik Brodowski wrote:
> On Thu, Aug 19, 2004 at 10:05:45AM +0200, Eric Valette wrote:
>
>>Li, Shaohua wrote:
>>
>>>Eric,
>>>The patch for bug 3049 has been in 2.6.8.1 and should fix the IO port
>>>problem. If the Asus quirk is just because of IO port problem, I'd like
>>>to remove it.
>
> It's not because of the IO port problem -- actually, this "IO" problem is a
> new appearance, while the Asus quirk works perfectly for many people.
>
>
>>>Note PNP driver also reserves the IO port for the SMBus
>>>and lets SMBus driver to use it. ACPI motherboard driver behaves the
>>>same as PNP driver.
>>
>>Unfortunately, as I understand it, the fix is done to "unhide" the SMBus
>>that otherwyse is not seen but it has unexpected side effect of messing
>>ioports allocation/reservation. I guess lspci with and without the fix
>>could help to understand the problem.
>
>
> Indeed. lspci without the fix doesn't show the device, lspci with the fix
> shows the device.
>
> Dominik
Dominik,
This is a little bit late. There are already two fixes for the SMBus
unhidding : one generic by linux, that is in 2.6.9-rc1-bk2 or
2.6.9-rc1-mm1 that fixes the SMBus but that is not really SMBus related
and one specific that you can find at
<http://bugme.osdl.org/show_bug.cgi?id=3191>. Linux blessed this patch
as it makes clear that unhiding the bus without reserving the IO space
is the root of the real problem but did not incorporate it probably
because the other fix is already in and mine should be done for buggy
BIOS (DTST) that access the hidden SMBus not indirect the IO BAR but via
hardwired values,
Patch is not yet merged and may well never be as now problem is masked,
--
__
/ ` Eric Valette
/-- __ o _. 6 rue Paul Le Flem
(___, / (_(_(__ 35740 Pace
Tel: +33 (0)2 99 85 26 76 Fax: +33 (0)2 99 85 26 76
E-mail: eric.valette@free.fr
next prev parent reply other threads:[~2004-08-29 13:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 7:50 2.6.8.1-mm1 and Asus L3C : problematic change found, can be reverted. Real fix still missing Li, Shaohua
2004-08-19 8:05 ` Eric Valette
2004-08-19 11:09 ` Eric Valette
2004-08-29 13:04 ` Dominik Brodowski
2004-08-29 13:50 ` Eric Valette [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-10 9:08 2.6.8-rc4-mm1 : radeon_monitor.c broken vs CONFIG_FB_MODE_HELPERS + Hard freeze Eric Valette
2004-08-10 10:35 ` 2.6.8-rc4-mm1 : Hard freeze due to ACPI Eric Valette
2004-08-10 16:07 ` Andrew Morton
[not found] ` <4123AC79.5000709@free.fr>
2004-08-19 0:00 ` 2.6.8.1-mm1 and Asus L3C : problematic change found, can be reverted. Real fix still missing Karol Kozimor
2004-08-19 7:16 ` Eric Valette
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=4131DF0F.5040306@free.fr \
--to=eric.valette@free.fr \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.de \
--cc=shaohua.li@intel.com \
--cc=sziwan@hell.org.pl \
--cc=zhenyu.z.wang@intel.com \
/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