From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-fbdev-devel@lists.sourceforge.net,
"Daniel Würfel" <daniel.wuerfel@gmx.net>,
linux-acpi@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
"Andrew Morton" <akpm@linux-foundation.org>,
"Len Brown" <lenb@kernel.org>
Subject: Re: [Bugme-new] [Bug 9155] New: No fan control with ATI Radeon display support on HP nx6125.
Date: Tue, 16 Oct 2007 06:57:44 +1000 [thread overview]
Message-ID: <1192481864.11795.27.camel@pasglop> (raw)
In-Reply-To: <200710152232.35324.rjw@sisk.pl>
On Mon, 2007-10-15 at 22:32 +0200, Rafael J. Wysocki wrote:
>
> Thanks for having narrowed this, good job.
>
> Now, the question is why the radeonfb compiled in statically has this effect.
>
> Can you please attach your current .config to the bugzilla entry?
I don't have the beginning of an idea of why radeonfb would cause that
indeed. (And especially not cause it when compiled as a module).
Ben.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-15 20:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9155-10286@http.bugzilla.kernel.org/>
2007-10-13 17:53 ` [Bugme-new] [Bug 9155] New: No fan control with ATI Radeon display support on HP nx6125 Andrew Morton
[not found] ` <20071013105315.accef6aa.akpm@linux-foundation.org>
2007-10-13 18:30 ` Rafael J. Wysocki
2007-10-14 7:26 ` Daniel Würfel
2007-10-14 14:02 ` Rafael J. Wysocki
2007-10-14 14:18 ` Daniel Würfel
2007-10-14 19:55 ` Rafael J. Wysocki
2007-10-15 17:12 ` Daniel Würfel
2007-10-15 20:32 ` Rafael J. Wysocki
2007-10-15 20:57 ` Benjamin Herrenschmidt [this message]
2007-10-15 21:17 ` Rafael J. Wysocki
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=1192481864.11795.27.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=daniel.wuerfel@gmx.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).