All of lore.kernel.org
 help / color / mirror / Atom feed
From: harrykipper <harrykipper@gmail.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: Help needed for unusual hack
Date: Sat, 01 Aug 2015 20:49:55 +0100	[thread overview]
Message-ID: <1438458595.1140.0@smtp.gmail.com> (raw)
In-Reply-To: <20150801150103.GA2676@wunner.de>

On Sat, 1 Aug, 2015 at 4:01 PM, Lukas Wunner <lukas@wunner.de> wrote:
> Hi,

Thanks very much Lukas, I tried both

> 
> Change is_edp() to something like:
> 
> -	return intel_dig_port->base.type == INTEL_OUTPUT_EDP;
> +	return intel_dig_port->base.type == INTEL_OUTPUT_EDP ||
> +	       strncmp(intel_dp->base.name, "DP-1", 4) == 0;


This fails as ‘struct intel_dp’ has no member named ‘base’. 
Tried some variants, but I am clueless.. :-/

> 
> 
> An alternative solution might be to modify intel_bios.c and change 
> what
> has been read vom VBT, see parse_ddi_port().

This seems easier, parse_ddi_port() assigns an 'is_edp' variable with
is_edp = is_dp && (child->common.device_type & 
DEVICE_TYPE_INTERNAL_CONNECTOR);

Assuming that setting it would suffice for my port to be detected as 
eDPI tried to change it to something like:
is_edp = is_dp && child->common.dvo_port == DVO_PORT_DPC;
or
is_edp = is_dp && (port == PORT_C);

is_edp = is_dp && port_name(port) == "DP-3"

since it's the third DP, but no success.

I must admit I am a bit clueless, but the solution seems within 
grasp....


Thanks very much

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-08-01 19:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31 13:34 Help needed for unusual hack harrykipper
2015-08-01 15:01 ` Lukas Wunner
2015-08-01 19:49   ` harrykipper [this message]
2015-08-01 20:37     ` Lukas Wunner
2015-08-02 21:27       ` harrykipper

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=1438458595.1140.0@smtp.gmail.com \
    --to=harrykipper@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lukas@wunner.de \
    /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.