From: Thomas Richter <thor@math.tu-berlin.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: i830 watermark problems - status?
Date: Mon, 25 Nov 2013 16:55:47 +0100 [thread overview]
Message-ID: <52937303.5000209@math.tu-berlin.de> (raw)
In-Reply-To: <26487_1385392973_52936B4D_26487_126_1_20131125152331.GB27344@phenom.ffwll.local>
Am 25.11.2013 16:23, schrieb Daniel Vetter:
> On Mon, Nov 25, 2013 at 04:14:12PM +0100, Thomas Richter wrote:
>> Hi Daniel, hi group,
>>
>> just being curious - what is the status of the i830 watermark
>> problems, i.e. the state of affairs
>> concerning that the i830 does not allow the maximum watermark value,
>> but requires a "headroom" of eight entries to
>> avoid flickering.
>>
>> I provided a patch for this a while ago, but this seems to go
>> nowhere. Just to remind you: The current code does not create
>> a stable image on i830 based devices, even if only an internal
>> display is connected.
>>
>> I provided two possible attacks to the problem: A quick and dirty
>> method which checks for the maximum value for
>> i830 manually, or an overall solution which adds a "minimum"
>> watermark value for all supported chipsets.
>>
>> Please let me know how to proceed.
> I seem to be too swamped with firedrills and bugs atm to get the polished
> version in. The problem with just a quick hack is that we still need to
> switch i830M to the dual-pipe watermark function, and somehow my patch to
> do so seems to be broken. At least you've said that the kernel still seems
> to hit the single-watermark version of the function.
>
> So atm I'm a bit stalled on this :( But if you can track this down I'd go
> with a quick hack to enforce the minimum of 8 or so in the dual-pipe
> watermark function shared by gen2/3.
Not a problem on my side, but it would be a "bad thing"(tm) to release a
kernel that leaves a i830 based
architecture essentially non-usable. Well, if you depend on a local
display, that is. (-;
Greetings,
Thomas
next prev parent reply other threads:[~2013-11-25 15:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1385093524-22276-1-git-send-email-keithp@keithp.com>
[not found] ` <20131122102632.GQ27344@phenom.ffwll.local>
[not found] ` <86d2lsem3m.fsf@miki.keithp.com>
2013-11-22 16:17 ` [Mesa-dev] [PATCH] dri3, i915, i965: Add __DRI_IMAGE_FOURCC_SARGB8888 Daniel Vetter
2013-11-22 17:46 ` Ville Syrjälä
2013-11-22 22:12 ` [Intel-gfx] " Kristian Høgsberg
2013-11-22 23:05 ` Ville Syrjälä
2013-11-22 23:43 ` Keith Packard
2013-11-23 1:10 ` Ville Syrjälä
2013-11-25 14:57 ` Geert Uytterhoeven
2013-11-22 23:36 ` [Intel-gfx] " Keith Packard
2013-11-25 8:57 ` [Mesa-dev] " Daniel Vetter
2013-11-25 14:15 ` Ville Syrjälä
[not found] ` <16967_1385369810_529310D2_16967_15891_1_20131125085723.GW27344@phenom.ffwll.local>
2013-11-25 15:14 ` i830 watermark problems - status? Thomas Richter
2013-11-25 15:23 ` Daniel Vetter
[not found] ` <26487_1385392973_52936B4D_26487_126_1_20131125152331.GB27344@phenom.ffwll.local>
2013-11-25 15:55 ` Thomas Richter [this message]
2013-11-25 20:30 ` Daniel Vetter
[not found] ` <26487_1385411456_5293B380_26487_2367_1_CAKMK7uFFZcf92XbzA9Mj2c0fdhDWZMKkZVNK9yy8Shc8pcLygg@mail.gmail.com>
2013-11-30 20:11 ` Thomas Richter
2013-12-19 14:01 ` intel-drm-nightly: hang and black screen on i830 Thomas Richter
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=52937303.5000209@math.tu-berlin.de \
--to=thor@math.tu-berlin.de \
--cc=daniel@ffwll.ch \
--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