dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Jason Chen <weitway@gmail.com>,
	Konstantinos Margaritis <markos@genesi-usa.com>,
	DRI mailing list <dri-devel@lists.freedesktop.org>,
	Eric Miao <eric.miao@linaro.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH] KMS support for i.MX51/53
Date: Tue, 7 Jun 2011 12:17:01 +0100	[thread overview]
Message-ID: <20110607121701.71cdd06e@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <1307443550-25549-1-git-send-email-s.hauer@pengutronix.de>

> Currently I don't use any sophisticated memory allocater like GEM
> or similar. I helped myself with simple dma_alloc where needed. At

GEM is actually pretty sane when you get your head around it a spot. The
main thing it took me a bit of time to get my head around is that it
allocates backing memory and handles but it doesn't allocate address
space on the card side.

For a minimal GEM take a look at drivers/staging/gma500/psb_gem.c. As I
need to use a GTT and allocate address space I also use a standard Linux
resource struct. If you just need to grab RAM and don't care about
address spaces then you are well away except for getting console support I
imagine.

The GMS500 one has no magic interfaces for things like swapping objects,
as the card is just using it for 2D frame buffer objects so hopefully is
a bit easier to follow than the full works.

Alan

  parent reply	other threads:[~2011-06-07 11:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07 10:45 [RFC PATCH] KMS support for i.MX51/53 Sascha Hauer
2011-06-07 10:45 ` [PATCH 1/5] DRM: add i.MX IPUv3 base driver Sascha Hauer
2011-06-07 15:45   ` Fabio Estevam
2011-06-07 10:45 ` [PATCH 2/5] DRM i.MX IPU: Add support for IPU submodules Sascha Hauer
2011-06-07 10:45 ` [PATCH 3/5] DRM: Add drm encoder/connector helper Sascha Hauer
2011-06-07 10:45 ` [PATCH 4/5] DRM: Add support for the sii902x HDMI/DVI encoder Sascha Hauer
2011-07-08 20:42   ` Alex Deucher
2011-07-08 21:01   ` Michał Mirosław
2011-07-12 13:21     ` Sascha Hauer
2011-06-07 10:45 ` [PATCH 5/5] DRM: Add i.MX IPUv3 support Sascha Hauer
2011-06-07 11:17 ` Alan Cox [this message]
2011-06-07 19:12   ` [RFC PATCH] KMS support for i.MX51/53 Sascha Hauer
2011-06-07 19:59     ` Alan Cox
2011-06-08  8:54       ` Sascha Hauer

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=20110607121701.71cdd06e@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eric.miao@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=markos@genesi-usa.com \
    --cc=s.hauer@pengutronix.de \
    --cc=weitway@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