All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <m.b.lankhorst@gmail.com>
To: Baurzhan Ismagulov <ibr@radix50.net>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: quirk for Samsung 2443BW
Date: Mon, 16 Jul 2012 13:07:23 +0200	[thread overview]
Message-ID: <5003F5EB.6040906@gmail.com> (raw)
In-Reply-To: <20120716110011.GC3428@radix50.net>

Op 16-07-12 13:00, Baurzhan Ismagulov schreef:
> On Mon, Jul 16, 2012 at 12:13:14PM +0200, Maarten Lankhorst wrote:
>>>>> Samsung 2443BW is 1920x1200 but reports 1920x1080 in the EDID. Attached
>>>>> is a proof-of-concept implementation of a quirk. It works on my i686 PC.
>>>>>
>>>>> The patch is against the latest linux-2.6. An attempt to clone
>>>>> git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git (as
>>>>> listed in MAINTAINERS) resulted in "fatal: The remote end hung up
>>>>> unexpectedly".
>>>>>
>>>> I actually own a 2443BW and don't have the problem you're referring to?
>>> Samsung might have fixed the data. If you care to send me your EDID
>>> data, I can compare it with mine. Still, there are many users who have
>>> broken monitors; it would be nice to provide a fix for them.
>> Attached.
> You have product code 0x0587 and vactive of 1200 in the first detailed
> mode. I have 0x06b0 and 1080, respectively. So, a fix is needed for the
> latter model.
>
> How did you obtain the file?
>
I was running the nvidia drivers, nvidia-settings allows you to save it.
But open source drivers allow you to copy it from  /sys/class/drm/card*/*/edid

~Maarten

  reply	other threads:[~2012-07-16 11:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16 10:13 quirk for Samsung 2443BW Maarten Lankhorst
2012-07-16 11:00 ` Baurzhan Ismagulov
2012-07-16 11:07   ` Maarten Lankhorst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-07-14 21:42 Baurzhan Ismagulov
2012-07-16  9:13 ` Maarten Lankhorst
2012-07-16  9:49   ` Baurzhan Ismagulov
2012-07-20  2:34 ` Dave Airlie

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=5003F5EB.6040906@gmail.com \
    --to=m.b.lankhorst@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ibr@radix50.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.