From: Matthew Garrett <mjg59@srcf.ucam.org>
To: yakui_zhao <yakui.zhao@intel.com>
Cc: "lenb@kernel.org" <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH 0/2]: the patch set to weaken the dependency between ACPI video driver and i915 driver
Date: Wed, 15 Apr 2009 05:53:59 +0100 [thread overview]
Message-ID: <20090415045359.GA15437@srcf.ucam.org> (raw)
In-Reply-To: <1239757961.5564.109.camel@localhost.localdomain>
On Wed, Apr 15, 2009 at 09:12:41AM +0800, yakui_zhao wrote:
> > No, it's *correct*. In a modesetting world, i915 requires ACPI.
> Why is the ACPI required by i915 when KMS is used?
> It seems that we still can use the KMS with ACPI disabled.
> In such case it is unnecessary to load the acpi video driver.
You can, but things will break.
> In fact what I have done is to weaken the tight dependency. When the
> i915 driver is compiled as built-in and the acpi video is compiled as
> module, the kernel compilation will be OK.
> Before the acpi video driver is loaded, the system is still OK
> except that there is no backlight control.
I know that that's what you've done. I just don't think it's useful.
Weakening the dependency means that you're driving the hardware outside
of its design parameters, and I really don't see any reason to do that.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-04-15 4:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 3:04 [PATCH 0/2]: the patch set to weaken the dependency between ACPI video driver and i915 driver yakui_zhao
2009-04-14 19:35 ` Matthew Garrett
2009-04-15 1:12 ` yakui_zhao
2009-04-15 4:53 ` Matthew Garrett [this message]
2009-04-15 13:21 ` Zhao, Yakui
2009-04-15 16:54 ` Matthew Garrett
2009-04-16 1:15 ` yakui_zhao
2009-04-15 7:35 ` Zhang Rui
2009-04-15 20:56 ` Matthew Garrett
2009-04-23 19:56 ` Len Brown
2009-04-30 20:23 ` Andrew Morton
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=20090415045359.GA15437@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=yakui.zhao@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;
as well as URLs for NNTP newsgroup(s).