[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-id: <200809020113.24058.gene.heskett@gmail.com>
Date: Tue, 02 Sep 2008 01:13:23 -0400
From: Gene Heskett <gene.heskett@...il.com>
To: "Jaswinder Singh" <jaswinderlinux@...il.com>
Cc: "Dave Airlie" <airlied@...il.com>,
"Linux Kernel" <linux-kernel@...r.kernel.org>
Subject: Re: Linux-2.6.27-rc5, drm errors in log
On Monday 01 September 2008, Jaswinder Singh wrote:
>Hello Gene,
>
>On Sun, Aug 31, 2008 at 6:55 AM, Gene Heskett <gene.heskett@...il.com> wrote:
>> Yes I can, but how do I get that specific patch? Or is that the git # for
>> the patch I first applied to -rc2, which added the firmware/radeon stuff?
>> I'm familiar with patch, but not on a first name basis with git, sorry.
>>
>> So I'm going to do a bisect, my style. I will rebuild, starting with
>> -rc3, using only the -rcX patch and the firmware addition patch, which
>> applied to -rc3 as follows:
>> now applying [PATCH]radeon_cp-use-request_firmware
>
>This patch is not included in 2.6.27-rc5. Please do not mix this patch
>now, first resolve your problem and if you want then you can add this
>patch above of it.
>
I see. However, since the stuff in /lib/firmware is already there from
previous builds that did include this patch, and I didn't delete it, I noted
that the 2.6.27-rc5 I built last night, without that patch, still loaded the
r200 microcode according to the messages log, and dmesg. From dmesg:
[root@...ote /]# dmesg|grep drm
[ 1.389274] [drm] Initialized drm 1.1.0 20060810
[ 1.389707] [drm] Initialized radeon 1.29.0 20080528 on minor 0
[ 85.920881] [drm] Setting GART location based on new memory map
[ 85.920894] [drm] Loading R200 Microcode
[ 85.920944] [drm] writeback test succeeded in 1 usecs
>Thank you,
>
>Jaswinder Singh.
Thank you!
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Good leaders being scarce, following yourself is allowed.
--
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