From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Thomas Wood <thomas.wood@intel.com>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH i-g-t 1/3] tests/kms_force_connector: Fixes
Date: Wed, 02 Dec 2015 13:50:36 +0200 [thread overview]
Message-ID: <87poyp2ho3.fsf@intel.com> (raw)
In-Reply-To: <20151201133819.GU17050@phenom.ffwll.local>
On Tue, 01 Dec 2015, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Tue, Dec 01, 2015 at 01:12:43PM +0200, Jani Nikula wrote:
>> On Tue, 01 Dec 2015, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>> > Somehow the kernel's mode list changed with our EDID.
>>
>> I do not undestand what you're trying to say here.
>
> The EDID we injected stayed the same, but the kernel started listing more
> modes for it. I didn't do a bisect nor analyse the root-cause since that
> would mean decoding the edid by hand to double-check what's going on.
>
> Suggestions for better phrasing?
Your first sentence above.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-12-02 11:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 10:24 [PATCH i-g-t 1/3] tests/kms_force_connector: Fixes Daniel Vetter
2015-12-01 10:24 ` [PATCH i-g-t 2/3] lib/kms+tests: Use cached connector state Daniel Vetter
2015-12-01 10:24 ` [PATCH i-g-t 3/3] tests/kms_force_connector: Include in BAT set Daniel Vetter
2015-12-01 10:33 ` Thomas Wood
2015-12-01 13:39 ` Daniel Vetter
2015-12-01 11:12 ` [PATCH i-g-t 1/3] tests/kms_force_connector: Fixes Jani Nikula
2015-12-01 13:38 ` Daniel Vetter
2015-12-02 11:50 ` Jani Nikula [this message]
2015-12-04 9:51 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2015-12-01 8:08 Daniel Vetter
2015-12-01 10:11 ` Thomas Wood
2015-12-01 10:19 ` Daniel Vetter
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=87poyp2ho3.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thomas.wood@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 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.