From: Daniel Vetter <daniel@ffwll.ch>
To: Horst Balthasar <ho.balthasar@imed-medical.de>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Access the intel graphic card via libdrm
Date: Wed, 3 Oct 2018 10:56:21 +0200 [thread overview]
Message-ID: <20181003085621.GS11082@phenom.ffwll.local> (raw)
In-Reply-To: <6137cfa5-6c05-af87-eb24-288e62590183@imed-medical.de>
On Tue, Oct 02, 2018 at 12:27:02PM +0200, Horst Balthasar wrote:
> Hallo,
>
> as a software developer at the company "imed medical" in Neu-Ulm" I am
> working with the intel graphics driver
>
> under Debian.
>
> The aim is to output continuous 2D images with the "libdrm" graphic library
> on the screen. We use the Intel i915 driver.
>
> Since I'm not so familiar with the Intel graphics driver (framebuffer, DRM)
> unter Debian, I would be verry happy about tips
>
> and examples to get familiar with this topic.
>
> I have already downloaded, compiled and installed the libdrm 2.4.94. I have
> also implemented the examples from 'modeset'
>
> and I am able to display a png file on the screen.
>
> But to process the images afterwards, we need access to the GPU, maybe GEM
> ??? Are there any examples or docs to help
>
> me get used it?
For a simple bare-metal (i.e. no compositor/desktop environment like X,
wayland or similar) look at kmscube. Contains everything you need for
accelarated rendering with just the kernel. Plus mesa, but you really,
really, really don't want to write your own rendering driver :-)
https://github.com/robclark/kmscube
Cheers, Daniel
>
>
> Thank you very much.
>
>
> Bests regards,
>
>
>
> Horst Balthasar
>
>
> Horst Balthasar
> Software-Entwickler Medizintechnik
>
> --
> imed medical GmbH
> Friedrichshafener Strasse 7
> D-89079 Ulm
>
> Standort Neu-Ulm
> Marlene-Dietrich-Strasse 5
> D-89231 Neu-Ulm
>
> Fon +49 (0)731 1411 179-6
> Fax +49 (0)731 1411 6513
> Zentrale +49 (0)731 1411 179-0
> Web www.imed-medical.de
>
> Sitz der Gesellschaft: Ulm Württemberg | Registergericht Ulm | HRB 730620 | Geschäftsführer: Benedikt Schmalz,
> Stefan Schmalz-Conrad
>
> Diese E-Mail ist vertraulich und enthält gesetzlich geschützte Informationen.
> Wenn Sie NICHT der rechtmäßige Empfänger oder einer seiner Mitarbeiter sind, dürfen Sie den Inhalt WEDER lesen,
> kopieren, verbreiten NOCH nutzen.
> Sollten Sie diese E-Mail versehentlich erhalten haben, senden Sie sie bitte an uns zurück und löschen Sie
> sie anschließend dauerhaft. Vielen Dank.
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-10-03 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 10:27 Access the intel graphic card via libdrm Horst Balthasar
2018-10-03 8:56 ` Daniel Vetter [this message]
[not found] ` <1860a139-b1d4-3d84-2de9-f3c9e70e7457@imed-medical.de>
2018-10-11 8:09 ` 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=20181003085621.GS11082@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=ho.balthasar@imed-medical.de \
/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