From mboxrd@z Thu Jan  1 00:00:00 1970
From: batouzo <batouzo@gmx.com>
Subject: Re: [drm] [radeon] [3.1.4] slub memory corruption in
	drm_vblank_cleanup
Date: Wed, 14 Dec 2011 18:49:03 +0100
Message-ID: <jcanif$lbq$1@dough.gmane.org>
References: <jc8ftn$v3m$1@dough.gmane.org>	<20111213233157.GD2339@homer.localdomain>	<jc8nbg$j3j$1@dough.gmane.org>	<CAH3drwZnt1cLzc9rwnDPE6SBXdU-kDPDraCkVXq1KW5=eWBrPg@mail.gmail.com>	<CAH3drwZq2WvjgVEsq9-WeXTmckK6ZB9S++zCTq3j3KS6bokYxA@mail.gmail.com>	<jc9hhl$tjc$1@dough.gmane.org>	<CADnq5_PFWTt4CJHo1vhGvv41jVAN5i8eaHEUfUAWMZA7kWWyew@mail.gmail.com>	<jcaj21$iej$1@dough.gmane.org>	<CADnq5_MO73ZRpN29oy+oWxJ2AQLZ1n3_tfM7zo2v8hCAjkL1qw@mail.gmail.com>	<jcaldq$687$1@dough.gmane.org>	<CADnq5_MAeWCzhKEFGGuraHBst4eYrqOGzruAms=p3MmikG7=RA@mail.gmail.com>	<jcam9f$bi1$1@dough.gmane.org>
	<CADnq5_O5hdw5WBEksuWXfeO1V7JK2-6C1oxbeR+j4tLH_9CihA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org>
Received: from lo.gmane.org (lo.gmane.org [80.91.229.12])
	by gabe.freedesktop.org (Postfix) with ESMTP id 253419EB38
	for <dri-devel@lists.freedesktop.org>;
	Wed, 14 Dec 2011 09:49:18 -0800 (PST)
Received: from list by lo.gmane.org with local (Exim 4.69)
	(envelope-from <sf-dri-devel@m.gmane.org>) id 1Rasx9-0000iw-Qo
	for dri-devel@lists.freedesktop.org; Wed, 14 Dec 2011 18:49:15 +0100
Received: from ip-1-141.gemini.net.pl ([193.25.1.141])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <dri-devel@lists.freedesktop.org>; Wed, 14 Dec 2011 18:49:15 +0100
Received: from batouzo by ip-1-141.gemini.net.pl with local (Gmexim 0.1
	(Debian)) id 1AlnuQ-0007hv-00
	for <dri-devel@lists.freedesktop.org>; Wed, 14 Dec 2011 18:49:15 +0100
In-Reply-To: <CADnq5_O5hdw5WBEksuWXfeO1V7JK2-6C1oxbeR+j4tLH_9CihA@mail.gmail.com>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/dri-devel>
List-Post: <mailto:dri-devel@lists.freedesktop.org>
List-Help: <mailto:dri-devel-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=subscribe>
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org

On 12/14/2011 06:40 PM, Alex Deucher wrote:
> On Wed, Dec 14, 2011 at 12:27 PM, batouzo <batouzo@gmx.com> wrote:

> AMD develops and releases the ucode images.  No source is available.
> 
>>
>> This means that entire firmeware of GFX card is flashed on bootup?
>> Btw this is a form of virus protection you could say (or anyway such
>> firmware is volatile and lost on reboot?)
> 
> The ucode is volatile and is lost on reboot.  The different ucode
> images are used for different things.  The PFP and ME ucode images
> provide the acceleration API and the RLC ucode is required to make the
> interrupt controller work.  On newer asics, the MC ucode is used for
> the gddr5 controller on the chip and is required to link train the
> memory so it will run at full speed.

Thanks for explanation.

I hoped using radeon and KMS I'm choosing the "good" (secure / FOSS
philosophy etc) solution, but it seems to not be the case then.

What should one do to have 100% opensource, maximally secure X on radeon
cards?
Maybe I should disable firmware to achieve this goal at cost of
performance - or may disabling firmware actually introduce any
security/stability problems?

Would Intel build-in card be better for this use? Any particular family?