From: Daniel Vetter <daniel@ffwll.ch>
To: Kirill Tkhai <tkhai@yandex.ru>
Cc: "daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [i915] invert_brightness on 8086:0116:103c:1854
Date: Mon, 7 Oct 2013 16:45:23 +0200 [thread overview]
Message-ID: <20131007144523.GZ31334@phenom.ffwll.local> (raw)
In-Reply-To: <163041381153391@web10g.yandex.ru>
On Mon, Oct 07, 2013 at 05:43:11PM +0400, Kirill Tkhai wrote:
>
>
> 07.10.2013, 16:14, "Kirill Tkhai" <tkhai@yandex.ru>:
> > 07.10.2013, 11:42, "Jani Nikula" <jani.nikula@linux.intel.com>:
> >
> >> On Sat, 05 Oct 2013, Kirill Tkhai <tkhai@yandex.ru> wrote:
> >>> Hi,
> >>>
> >>> I've just installed kernel 3.10 on HP 250 G1 and the found option
> >>> invert_brightness is required.
> >> Hi Kirill, thanks for the report. I suspect invert_brightness is not the
> >> right fix, since we've only ever seen that on gen4 Acer based
> >> laptops. Please file a bug on DRM/Intel at [1].
> >
> > One more detail before I post a BUG.
> >
> > My screen is black in *console* right after kernel is started unless
> > the option is passed.
> >
> > DRI is about XServer as I understand right. Do we mean the same?
>
> *if* I understand right :)
DRI is X server, but DR_M_ is the kernel part. Yeah, the linux gfx stack
is a rather complex beast ...
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2013-10-07 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <31941380503904@web12m.yandex.ru>
2013-10-05 4:06 ` [i915] invert_brightness on 8086:0116:103c:1854 Kirill Tkhai
2013-10-07 7:44 ` Jani Nikula
2013-10-07 12:14 ` Kirill Tkhai
2013-10-07 13:43 ` Kirill Tkhai
2013-10-07 14:45 ` Daniel Vetter [this message]
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=20131007144523.GZ31334@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tkhai@yandex.ru \
/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