From: Jani Nikula <jani.nikula@intel.com>
To: Romain Francoise <romain@orebokech.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: v3.14-rc7: Backlight control broken on Dell XPS13
Date: Mon, 17 Mar 2014 17:03:31 +0200 [thread overview]
Message-ID: <87txawzx30.fsf@intel.com> (raw)
In-Reply-To: <877g7s53ac.fsf@kima.orebokech.com>
On Mon, 17 Mar 2014, Romain Francoise <romain@orebokech.com> wrote:
> Hi Daniel,
>
> Daniel Vetter <daniel.vetter@ffwll.ch> writes:
>
>> Please never just send a mail to maintainers, always cc mailing lists.
>
> Yes, sorry, I sent this privately because it wasn't a fully-formed bug
> report; I just wanted Jani to confirm that it wasn't intentionally
> broken as of -rc7.
>
>> Have you tested with the patch reverted to confirm that it's indeed
>> this commit and not something else (e.g. in the acpi code)?
>
> I hadn't, but I've now reverted the revert and things work again as in
> v3.13. So as far as I can tell the quirk is still definitely needed.
I still don't think having the quirk is the way to go. Let's fix this
properly, shall we?
Please file a new bug on DRM/Intel component at [1]. Please attach
intel_reg_dumper output (tool from intel-gpu-tools [2]) with and without
the revert. Please also attach dmesg with drm.debug=0xe from early boot.
Do you have the snb or ivb model?
BR,
Jani.
[1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI
[2] http://cgit.freedesktop.org/xorg/app/intel-gpu-tools/
>
> Thanks!
> -r
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-03-17 15:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87eh213q70.fsf@kima.orebokech.com>
2014-03-17 13:44 ` v3.14-rc7: Backlight control broken on Dell XPS13 Daniel Vetter
2014-03-17 14:05 ` Romain Francoise
2014-03-17 15:03 ` Jani Nikula [this message]
2014-03-17 15:42 ` Jani Nikula
2014-03-17 16:34 ` Romain Francoise
2014-03-17 16:41 ` Jani Nikula
2014-03-17 17:27 ` Romain Francoise
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=87txawzx30.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=romain@orebokech.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