From: Volker Vogelhuber <v.vogelhuber@digitalendoscopy.de>
To: dri-devel@lists.freedesktop.org
Subject: Update front buffer without CPU interaction?
Date: Mon, 16 Feb 2015 13:43:07 +0100 [thread overview]
Message-ID: <54E1E5DB.7050303@digitalendoscopy.de> (raw)
I'm currently trying to setup a rendering pipe on an Intel Baytrail
E3845 cpu.
In our product we want to have an FPGA streaming video images to a
predefined memory area using bus master dma and render those images
using OpenGL. So far this works in a preliminary state.
We now have the security requirement that in case the CPU
(software/kernel driver) crashes for what ever reason, the GPU display
signal should still output at least the video images (obviously any
additional render stuff will not be available anymore). My question is
now, would it be possible to get the physical address of the DRM front
buffer, so that I can provide this address to the FPGA (connected via
PCIe) and is it possible to have the GPU still reading the last front
buffer for the display output while the FPGA writes to that area. So I
would think that the GPU has some kind of DMA engine running, that
continuously reading the last front buffer until switched to another
buffer by the CPU. So even if the CPU does not control the GPU anymore,
it might be possible to have the front buffer updated by the FPGA
directly. Of course there will be tearing artefacts as no VSYNC will be
available but that wouldn't be an issue so far.
Kind regards,
Volker
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-02-16 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 12:43 Volker Vogelhuber [this message]
2015-02-22 11:52 ` Update front buffer without CPU interaction? Daniel Vetter
2015-02-23 8:22 ` Volker Vogelhuber
2015-02-23 9:18 ` Daniel Vetter
2015-03-24 7:51 ` Volker Vogelhuber
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=54E1E5DB.7050303@digitalendoscopy.de \
--to=v.vogelhuber@digitalendoscopy.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.