From: Jani Nikula <jani.nikula@intel.com>
To: Adam Jackson <ajax@redhat.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: add sanity checks for hsync and htotal
Date: Thu, 21 Jun 2012 10:33:12 +0300 [thread overview]
Message-ID: <87zk7xw24n.fsf@intel.com> (raw)
In-Reply-To: <1340228186.14667.7.camel@atropine>
On Thu, 21 Jun 2012, Adam Jackson <ajax@redhat.com> wrote:
> On Wed, 2012-06-20 at 23:15 +0300, Jani Nikula wrote:
>> Restrict hsync start, end, hdisplay and htotal to be according to hw
>> spec. Through drm_mode_set_crtcinfo(), these will also limit hblank start,
>> end.
>
> I'm pretty sure any physical hardware would balk at modes like this.
> Virtual framebuffers probably wouldn't care, I guess. Still, seems
> wrong to have this in i915 when it should be common.
>
> Is this a problem we've seen in the wild, or is this just paranoia?
Looking at patch 2/2 I thought this would be a sensible thing to
do. That patch adds a check for a condition people might expect to work,
but doesn't, on Cantiga and later. It seemed a bit odd to merely add a
check for hsync_start == hdisplay while hsync_start < hdisplay (and the
other related conditions) would fail too.
BR,
Jani.
next prev parent reply other threads:[~2012-06-21 7:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 20:15 [PATCH 1/2] drm/i915: add sanity checks for hsync and htotal Jani Nikula
2012-06-20 20:15 ` [PATCH 2/2] drm/i915: Cantiga+ cannot handle a hsync front porch of 0 Jani Nikula
2012-06-20 21:36 ` [PATCH 1/2] drm/i915: add sanity checks for hsync and htotal Adam Jackson
2012-06-21 7:33 ` Jani Nikula [this message]
2012-06-21 10:19 ` [PATCH v2] drm/i915: Cantiga+ cannot handle a hsync front porch of 0 Jani Nikula
2012-06-21 12:16 ` Ville Syrjälä
2012-08-22 15:39 ` 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=87zk7xw24n.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=ajax@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox