From: Thomas Richter <richter@rus.uni-stuttgart.de>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 6/6] drm/i915: i830M has watermarks like i855
Date: Mon, 02 Dec 2013 15:27:51 +0100 [thread overview]
Message-ID: <529C98E7.4010007@rus.uni-stuttgart.de> (raw)
In-Reply-To: <1385990771-3877-7-git-send-email-rodrigo.vivi@gmail.com>
On 12/02/2013 02:26 PM, Rodrigo Vivi wrote:
> From: Daniel Vetter<daniel.vetter@ffwll.ch>
>
> So shuffle the checks around a bit. Also give all the structs and
> functions proper prefixes: i830_ for the dual-pipe mobile platforms
> and i845_ for the two single-pipe desktop platforms.
>
> Note that the max fifo value isn't actually correct for the i830M, but
> since we don't frob the fifo split we don't actually need it. This is
> different for some gen3 devices where we need the full fifo for self
> refresh mode.
>
Thanks, will try, possibly next Friday. I'm unfortunately booked until then.
Greetings,
Thomas
prev parent reply other threads:[~2013-12-02 14:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 13:26 [PATCH 0/6] drm-intel-collector - update Rodrigo Vivi
2013-12-02 13:26 ` [PATCH 1/6] drm/i915: Asynchronously perform the set-base for a simple modeset Rodrigo Vivi
2013-12-02 13:26 ` [PATCH 2/6] drm/i915: Do hw quiescing first during unload Rodrigo Vivi
2013-12-05 11:49 ` Daniel Vetter
2013-12-02 13:26 ` [PATCH 3/6] drm/i915: Downgrade pipe state mismatches to DRM_DEBUG_KMS Rodrigo Vivi
2013-12-05 11:49 ` Daniel Vetter
2013-12-02 13:26 ` [PATCH 4/6] drm/i915: use __packed instead of __attribute__((packed)) Rodrigo Vivi
2013-12-03 11:34 ` Damien Lespiau
2013-12-02 13:26 ` [PATCH 5/6] drm/i915: parse backlight modulation frequency from the BIOS VBT Rodrigo Vivi
2013-12-06 12:45 ` Rodrigo Vivi
2013-12-02 13:26 ` [PATCH 6/6] drm/i915: i830M has watermarks like i855 Rodrigo Vivi
2013-12-02 14:27 ` Thomas Richter [this message]
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=529C98E7.4010007@rus.uni-stuttgart.de \
--to=richter@rus.uni-stuttgart.de \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@gmail.com \
/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