From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: DRM framebuffer refcounting bug... still present
Date: Sat, 11 Oct 2014 15:08:58 +0100 [thread overview]
Message-ID: <20141011140858.GA27357@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20141011092620.GQ5182@n2100.arm.linux.org.uk>
On Sat, Oct 11, 2014 at 10:26:20AM +0100, Russell King - ARM Linux wrote:
> Daniel,
>
> A while back you had a go at fixing the framebuffer reference counting.
> Unfortunately, I'm still seeing leaks, particularly with the framebuffer
> used with a mode set which is subsequently flipped. It is only this
> framebuffer which is leaked, flips of an already flipped framebuffer do
> not.
I think I've fixed this now, so, please disregard this message. I'll
post some Armada fixes later today for this, and for the vblank issue
discussed previously.
Thanks.
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2014-10-11 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-11 9:26 DRM framebuffer refcounting bug... still present Russell King - ARM Linux
2014-10-11 14:08 ` Russell King - ARM Linux [this message]
2014-10-11 19:12 ` 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=20141011140858.GA27357@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@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