From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Dave Airlie <airlied@gmail.com>
Cc: Alan Cox <alan@linux.intel.com>,
greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gma500: Intel GMA500 staging driver
Date: Thu, 24 Feb 2011 12:10:42 +0000 [thread overview]
Message-ID: <20110224121042.6fa3fe37@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <AANLkTimPpr+OugTiPpYxNyS78vqActuURw-tnxJVxi18@mail.gmail.com>
> So where do we want to go my opinion is
>
> a) remove all userspace interfaces and simplify ttm memory management usage.
Some of them appear to be valid/sensible ones for querying mode data and
config bits. I'm slowly pruning out the rest
> b) add support to hook this up to the dumb ioctl so we can do trivial
> generic front buffer allocation, so then a libkms + dumb kms
> modesetting driver can work on it.
What sort of dumb ioctl do you have in mind ?
> c) figure out how to add interface for acceleration users. Whether TTM
> fence interfaces are required etc.
The fencing seems to be solely for the various capture/acceleration bits
for video as far as I can tell.
It seems we need two things - issue a 2D command and stuff for
transferring objects, although it's not clear that the latter is needed.
The old X 2D code is at:
http://git.moblin.org/cgit.cgi/deprecated/xf86-video-psb/
> We could probably just add a GEM style buffer allocation interface but
> we'd probably need to do a lot of RE first to figure out what best
> suits the hardware, I'm pretty sure I've haven't heard any glowing
> praise that the current interface suits the hw or is maintainable.
Nor me
I'll push the 2D bits to the tree but disabled (right now they go pop and
I've not pinned down what register or other incantation I've missed
somewhere) so there is a better view of what is needed.
Alan
next prev parent reply other threads:[~2011-02-24 12:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 12:17 Alan Cox
2011-02-22 14:44 ` Greg KH
2011-02-22 14:51 ` Alan Cox
2011-02-22 15:40 ` Matthew Garrett
2011-02-22 16:17 ` Alan Cox
2011-02-22 22:59 ` Patrik Jakobsson
2011-02-22 17:09 ` Arnd Bergmann
2011-02-22 17:43 ` Alan Cox
2011-02-23 23:51 ` Dave Airlie
2011-02-24 0:01 ` Greg KH
2011-02-24 12:10 ` Alan Cox [this message]
2011-03-01 3:40 ` Dave Airlie
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=20110224121042.6fa3fe37@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=airlied@gmail.com \
--cc=alan@linux.intel.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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 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®