All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <dmarkh@cfl.rr.com>
To: "Bruno Prémont" <bonbons@linux-vserver.org>
Cc: markh@compro.net, linux-kernel@vger.kernel.org,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: Intel graphics drm issue?
Date: Sun, 14 Oct 2012 14:03:21 -0400	[thread overview]
Message-ID: <507AFE69.70405@cfl.rr.com> (raw)
In-Reply-To: <20121014192253.5a7517ef@neptune.home>

On 10/14/2012 01:22 PM, Bruno Prémont wrote:
> Hi Mark,
>
> On Sun, 14 October 2012 Mark Hounschell <dmarkh@cfl.rr.com> wrote:
>> I've taken the EDID data from that service manual. I've looked at the
>> EDID-Howto for how to specify the connector but all I see is:
>>
>> "An EDID data set will only be used for a particular connector,
>>    if its name and a colon are prepended to the EDID name."
>>
>> Where can I find the connector names?
>
> Those are the ones you see under /sys/class/drm/, without the card0-
> prefix.
>
> E.g. on my system I have:
>
> # ls /sys/class/drm/
> card0  card0-DVI-I-1  card0-LVDS-1  card0-VGA-1  controlD64  version
>
> Thus I have connectors "DVI-I-1", "LVDS-1" and "VGA-1" (note that your
> HDMI connector might not be named HDMI-1, if you are not sure which one
> it is, you can look at the files below (edid, enabled, status) which
> should help your find the right connector).
>

Perfect.

>
> In addition, if you rmmod i915 and modprobe it again connectors will get
> increased suffix numbers. So don't expect them to remain the same if you
> have multiple GPUs detected in random order or if you rebind them to
> their driver. (though except during testing or for special systems you
> don't have to worry about this)
>
>> And could I ask if this simple pgm might work to build the file I need?
>
> It looks fine. You can also check the output with hexdump just to
> make sure it looks sane.

Did that and the data looks swapped compared to the array written, but I 
guess that's normal?

> If it's broken kernel will tell you that checksum does not match.
>

So the  check sum is actually already in the data provided by the service 
manual then.

> In any case the (successful) loading of edid should be visible in kernel
> log.
>

I'll be trying this a little later in the day.

Thanks again
Mark

  reply	other threads:[~2012-10-14 18:03 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12 12:54 Intel graphics drm issue? Mark Hounschell
2012-10-12 21:14 ` Bruno Prémont
2012-10-13 18:57   ` Mark Hounschell
2012-10-13 19:17     ` Mark Hounschell
2012-10-14  8:41       ` Bruno Prémont
2012-10-14  8:41         ` Bruno Prémont
2012-10-14 10:34         ` Mark Hounschell
2012-10-14 10:52         ` Mark Hounschell
2012-10-14 11:03           ` Bruno Prémont
2012-10-14 11:03             ` Bruno Prémont
2012-10-14 16:54             ` Mark Hounschell
2012-10-14 17:22               ` Bruno Prémont
2012-10-14 18:03                 ` Mark Hounschell [this message]
2012-10-14 18:19                   ` Bruno Prémont
2012-10-14 18:19                     ` Bruno Prémont
2012-10-14 18:57                     ` Mark Hounschell
2012-10-14 20:40                       ` Bruno Prémont
2012-10-14 20:40                         ` Bruno Prémont
2012-10-15  9:58                         ` Mark Hounschell
2012-10-14  8:58       ` Daniel Vetter
2012-10-14  8:58         ` [Intel-gfx] " Daniel Vetter
2012-10-14 10:20         ` Mark Hounschell
2012-10-14 11:26           ` Daniel Vetter
2012-10-14 11:26             ` [Intel-gfx] " Daniel Vetter
2012-10-14 11:39             ` Mark Hounschell
2012-10-14 14:19             ` Mark Hounschell
2012-10-14 14:40               ` Daniel Vetter
2012-10-14 15:41                 ` Mark Hounschell
2012-10-14 15:53                   ` Daniel Vetter
2012-10-14 15:55                     ` Bruno Prémont
2012-10-14 16:09                       ` Mark Hounschell
2012-10-14 16:13                         ` Mark Hounschell

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=507AFE69.70405@cfl.rr.com \
    --to=dmarkh@cfl.rr.com \
    --cc=bonbons@linux-vserver.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markh@compro.net \
    /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.