From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "Michel Dänzer" <michel@daenzer.net>,
"Peter Hurley" <peter@hurleysoftware.com>,
"Archit Taneja" <architt@codeaurora.org>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Ben Skeggs" <bskeggs@redhat.com>,
"Linux kernel" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: BUG caused by "Use new drm_fb_helper functions" series
Date: Tue, 9 Feb 2016 13:44:22 +0000 [thread overview]
Message-ID: <20160209134422.00e6f6b6@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20160209093240.GF11240@phenom.ffwll.local>
> > > But a better look has me wondering how all these gpus are syncing
> > > the framebuffer for direct access via cfb_imageblit and friends. I only see
> > > nouveau and intel gma even trying.
> >
> > Probably no other DRM driver uses hardware acceleration for fbcon.
>
> Yup. We've had patches for i915, resulted in half of mesa+glamour in-kernel, which
> is just pointless.
> -Daniel
When I did the gma500 driver I played with it a little and the only thing
that made any difference was scrolling acceleratin - which actually the
i915 can probably also do without using the 2D/3D engine.
It's actually trying to fix the wrong problem. The real problem is that
the fbcon layer when running pure text output tries to write everything to
the screen rather than just updating the offscreen array of text and
then doing at most one difference update per vblank based upon the state
of the display. That would make most of the dumb fbs feel lightning fast.
Alan
prev parent reply other threads:[~2016-02-09 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 20:37 Peter Hurley
2016-02-02 5:20 ` Archit Taneja
2016-02-02 18:38 ` Peter Hurley
2016-02-03 9:30 ` Michel Dänzer
2016-02-09 9:32 ` Daniel Vetter
2016-02-09 13:44 ` One Thousand Gnomes [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=20160209134422.00e6f6b6@lxorguk.ukuu.org.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=architt@codeaurora.org \
--cc=bskeggs@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
--cc=peter@hurleysoftware.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
all inboxes | Powered by JetHome®