From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: Alex Williamson <alex.williamson-VXdhtT5mjnY@public.gmane.org>
Cc: "Moore,
Robert" <robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
acpi-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: lost thermal zones on 20040715 nc6000
Date: Tue, 24 Aug 2004 23:51:18 +0200 [thread overview]
Message-ID: <20040824215118.GA13853@hell.org.pl> (raw)
In-Reply-To: <1093382665.5299.16.camel@tdi>
Thus wrote Alex Williamson:
>
> I've nearly gotten to the bottom of this problem. It's not an
> interpreter bug, nor is it a BIOS bug. The address we were trying to
> read in AML is a SMBus controller address. This address sits on the
> hidden SMBus function in the Intel chipset. Unfortunately, the PCI
> quirks routine un-hides the devices. So far this is all the same as the
> way it behaved prior to the 20040715 code drop.
>
> The new piece is the motherboard driver. Now this driver comes in an
> claims the I/O port region that the SMBus controller is using. We've
> un-hidden the PCI function, so PCI wants that resource range. It can't
> get it so it moves the SMBus BAR to a different address. The AML is now
> hosed cause it's hard-coded to use the address it programmed in (why
> shouldn't it, the device is hidden). Why are we un-hiding the SMBus
> function? The AML sets up an OpRegion for the address space it uses, so
> should have exclusive access to that range. Suggestions? Thanks,
Ouch, see bug #3191.
Best regards,
--
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
next prev parent reply other threads:[~2004-08-24 21:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 16:42 lost thermal zones on 20040715 nc6000 Moore, Robert
[not found] ` <37F890616C995246BE76B3E6B2DBE05501A8B206-sBd4vmA9Se5Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-08-11 16:55 ` Alex Williamson
2004-08-24 21:24 ` Alex Williamson
2004-08-24 21:51 ` Karol Kozimor [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-25 1:59 Li, Shaohua
2004-08-25 1:27 Li, Shaohua
[not found] ` <B44D37711ED29844BEA67908EAF36F03A38375-4yWAQGcml65pB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-08-25 1:51 ` Alex Williamson
2004-08-24 21:40 Moore, Robert
2004-08-10 15:50 Alex Williamson
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=20040824215118.GA13853@hell.org.pl \
--to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=alex.williamson-VXdhtT5mjnY@public.gmane.org \
--cc=robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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