From: Arnd Bergmann <arnd@arndb.de>
To: Alan Cox <alan@linux.intel.com>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gma500: Intel GMA500 staging driver
Date: Tue, 22 Feb 2011 18:09:50 +0100 [thread overview]
Message-ID: <201102221809.50716.arnd@arndb.de> (raw)
In-Reply-To: <20110222121704.19437.4650.stgit@localhost.localdomain>
On Tuesday 22 February 2011, Alan Cox wrote:
> This is an initial staging driver for the GMA500. It's been stripped out
> of the PVR drivers and crunched together from various bits of code and
> different kernels.
>
> Currently it's unaccelerated but still pretty snappy even compositing with
> the frame buffer X server.
>
> Lots of work is needed to rework the ttm and bo interfaces from being
> ripped out and then 2D acceleration wants putting back for framebuffer and
> somehow eventually via DRM.
>
> There is no support for the parts without open source userspace (video
> accelerators, 3D) as per kernel policy.
>
> I'm not a DRM expert so if there is anyone with a GMA500 who actually knows
> something about DRI internals then help would be most welcome.
>
> Signed-off-by: Alan Cox <alan@linux.intel.com>
Great to see progress here!
Before I start looking at the code, one high-level question: How much of
the code in the gma500 driver would be shared with SOCs from other people
(ARM based, typically) that use the PowerVR SGX core?
IOW, is this driver only for parts that Intel (or whoever) has put around
the licensed 3D core, or is it actually the same code that the others would
use for a non-3D SGX driver?
Arnd
next prev parent reply other threads:[~2011-02-22 17:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 12:17 [PATCH] gma500: Intel GMA500 staging driver 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 [this message]
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
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=201102221809.50716.arnd@arndb.de \
--to=arnd@arndb.de \
--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