dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Rob Clark <robdclark@gmail.com>,
	dri-devel@lists.freedesktop.org, mesa-dev@lists.freedesktop.org
Cc: Rob Clark <robclark@freedesktop.org>
Subject: Re: [Mesa-dev] [PATCH libdrm] freedreno: add freedreno DRM
Date: Tue, 19 Feb 2013 12:50:43 -0800	[thread overview]
Message-ID: <87y5ekf2os.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <1361129597-8221-1-git-send-email-robdclark@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1515 bytes --]

Rob Clark <robdclark@gmail.com> writes:

> From: Rob Clark <robclark@freedesktop.org>
>
> The libdrm_freedreno helper layer for use by xf86-video-freedreno,
> fdre (freedreno r/e library and tests for driving gpu), and eventual
> gallium driver for the Adreno GPU.  This uses the msm gpu driver
> from QCOM's android kernel tree.
>
> Note that current msm kernel driver is a bit strange.  It provides a
> DRM interface for GEM, which is basically sufficient to have DRI2
> working.  But it does not provide KMS.  And interface to 2d and 3d
> cores is via different other devices (/dev/kgsl-*).  This is not
> quite how I'd write a DRM driver, but at this stage it is useful for
> xf86-video-freedreno and fdre (and eventual gallium driver) to be
> able to work on existing kernel driver from QCOM, to allow to
> capture cmdstream dumps from the binary blob drivers without having
> to reboot.  So libdrm_freedreno attempts to hide most of the crazy.
> The intention is that when there is a proper kernel driver, it will
> be mostly just changes in libdrm_freedreno to adapt the gallium
> driver and xf86-video-freedreno (ignoring the fbdev->KMS changes).
>
> So don't look at freedreno as an example of how to write a libdrm
> module or a DRM driver.. it is just an attempt to paper over a non-
> standard kernel driver architecture.

Yeah, at this stage I expect things to be kinda held together with duct
tape and baling wire, and it's still worth having the code in git.

Acked-by: Eric Anholt <eric@anholt.net>

[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2013-02-19 20:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-17 19:33 [PATCH libdrm] freedreno: add freedreno DRM Rob Clark
2013-02-19 20:50 ` Eric Anholt [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=87y5ekf2os.fsf@eliezer.anholt.net \
    --to=eric@anholt.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=mesa-dev@lists.freedesktop.org \
    --cc=robclark@freedesktop.org \
    --cc=robdclark@gmail.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