From: yakui_zhao <yakui.zhao@intel.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
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 09:12:41 +0800 [thread overview]
Message-ID: <1239757961.5564.109.camel@localhost.localdomain> (raw)
In-Reply-To: <20090414193538.GB8304@srcf.ucam.org>
On Wed, 2009-04-15 at 03:35 +0800, Matthew Garrett wrote:
> On Tue, Apr 14, 2009 at 11:04:35AM +0800, yakui_zhao wrote:
>
> > Patch 2/2: weaken the tight dependency between the ACPI video driver and i915 driver
> > Now there exists the tight dependency between the ACPI video driver and i915 driver.
> > If the I915 driver is compiled as built-in module and the acpi video is compiled as module,
> > it will fail in the kernel compilation.
> > At the same time the acpi video driver must be loaded in order to load
> > the I915 driver. It is very hack.
>
> 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.
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.
Is this reasonable?
Thanks.
>
next prev parent reply other threads:[~2009-04-15 1:11 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 [this message]
2009-04-15 4:53 ` Matthew Garrett
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=1239757961.5564.109.camel@localhost.localdomain \
--to=yakui.zhao@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.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;
as well as URLs for NNTP newsgroup(s).