From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: airlied@linux.ie, dri-devel@lists.freedesktop.org,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH 2/3] acpi_video: Intel video is not always i915
Date: Wed, 25 Apr 2012 13:40:18 +0100 [thread overview]
Message-ID: <20120425124018.GA10533@srcf.ucam.org> (raw)
In-Reply-To: <20120425132438.562c52cf@pyramind.ukuu.org.uk>
On Wed, Apr 25, 2012 at 01:24:38PM +0100, Alan Cox wrote:
> Because as I said before there are two drivers involved and you may only
> have one compiled into your kernel. If you have
>
> CONFIG_DRM_GMA500=y
> CONFIG_DRM_I915=n
>
> you want the acpi stuff to autoregister even if an i915 is found, but not
> if a GMA500 is found. Ditto the reverse.
No you don't - there's various platforms that will hang if you do that.
It's necessary to make sure that the DIDL fields are set up before
calling any ACPI video functions on opregion hardware.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2012-04-25 12:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 15:44 [PATCH 1/3] acpi_video: fix leaking PCI references Alan Cox
2012-04-24 15:45 ` [PATCH 2/3] acpi_video: Intel video is not always i915 Alan Cox
2012-04-24 21:02 ` Matthew Garrett
2012-04-24 22:31 ` Alan Cox
2012-04-24 22:30 ` Matthew Garrett
2012-04-25 10:27 ` Alan Cox
2012-04-25 11:31 ` Matthew Garrett
2012-04-25 12:24 ` Alan Cox
2012-04-25 12:40 ` Matthew Garrett [this message]
2012-04-25 12:49 ` Alan Cox
2012-04-25 12:48 ` Matthew Garrett
2012-04-24 15:45 ` [PATCH 3/3] gma500: don't register the ACPI video bus Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2012-04-25 13:33 [PATCH 1/3] acpi_video: fix leaking PCI references Alan Cox
2012-04-25 13:33 ` [PATCH 2/3] acpi_video: Intel video is not always i915 Alan Cox
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=20120425124018.GA10533@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=airlied@linux.ie \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-acpi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.