lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201102221809.50716.arnd@arndb.de>
Date:	Tue, 22 Feb 2011 18:09:50 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Alan Cox <alan@...ux.intel.com>
Cc:	greg@...ah.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] gma500: Intel GMA500 staging driver

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@...ux.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ