All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/edid: Adding common CVT inferred modes when monitor allows range limited ones trough EDID.
Date: Fri, 13 Apr 2012 15:35:04 +0100	[thread overview]
Message-ID: <CAPM=9twhG8TSt5xdmbaFgjqMqi9+2sDD_SEOp0VwVy9v5cHV+A@mail.gmail.com> (raw)
In-Reply-To: <s5h3987vh60.wl%tiwai@suse.de>

> I don't think we need to support all wild modes, too.  But the _very_
> common modes like 1366x768 and 1600x900 should be really supported as
> default.

You guys still haven't answered the basic question, what HW is this broken?

Can you provide some EDIDs?

Dave.

  reply	other threads:[~2012-04-13 14:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12  0:59 [PATCH] drm/edid: Adding common CVT inferred modes when monitor allows range limited ones trough EDID Rodrigo Vivi
2012-04-12 16:03 ` Adam Jackson
2012-04-12 16:33 ` [Intel-gfx] " Takashi Iwai
2012-04-12 23:09   ` Rodrigo Vivi
2012-04-13 14:14     ` Adam Jackson
2012-04-13 14:29       ` Takashi Iwai
2012-04-13 14:35         ` Dave Airlie [this message]
2012-04-13 15:13           ` Takashi Iwai
2012-04-13 15:30             ` Alex Deucher
2012-04-13 15:41               ` Takashi Iwai
2012-04-13 15:52                 ` Alex Deucher
2012-04-13 16:31                 ` Adam Jackson
2012-04-13 16:48                   ` Takashi Iwai
2012-04-13 14:55         ` Adam Jackson
2012-04-13 15:20           ` Takashi Iwai
2012-04-13 15:25             ` David Airlie
2012-04-13 17:16               ` Adam Jackson
2012-04-13 19:05                 ` Rodrigo Vivi

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='CAPM=9twhG8TSt5xdmbaFgjqMqi9+2sDD_SEOp0VwVy9v5cHV+A@mail.gmail.com' \
    --to=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=tiwai@suse.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.