public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@gmail.com>
To: "Jaswinder Singh" <jaswinderlinux@gmail.com>
Cc: "Dave Airlie" <airlied@gmail.com>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Linux-2.6.27-rc5, drm errors in log
Date: Tue, 02 Sep 2008 01:13:23 -0400	[thread overview]
Message-ID: <200809020113.24058.gene.heskett@gmail.com> (raw)
In-Reply-To: <3f9a31f40809010951p15ed7359w48d2b18adf0ca20f@mail.gmail.com>

On Monday 01 September 2008, Jaswinder Singh wrote:
>Hello Gene,
>
>On Sun, Aug 31, 2008 at 6:55 AM, Gene Heskett <gene.heskett@gmail.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@coyote /]# 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.

  reply	other threads:[~2008-09-02  5:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <898503EB1E15BA4F944D1BE69D55AAC8AB540A@storexmb1.amd.com>
     [not found] ` <200808302219.45103.gene.heskett@verizon.net>
2008-08-31  6:40   ` Linux-2.6.27-rc5, drm errors in log Dave Airlie
2008-08-31 10:55     ` Gene Heskett
2008-08-31 11:57       ` Gene Heskett
2008-08-31 18:23       ` Gene Heskett
2008-08-31 20:56         ` Dave Airlie
2008-09-01  1:01           ` Gene Heskett
2008-09-01 16:51       ` Jaswinder Singh
2008-09-02  5:13         ` Gene Heskett [this message]
2008-08-30 18:52 Gene Heskett
2008-08-30 19:22 ` Arjan van de Ven
2008-09-01 17:15   ` Jaswinder Singh
2008-08-30 21:06 ` Dave Airlie
2008-09-01 16:34 ` Jaswinder Singh
2008-09-01 17:52   ` Jean Delvare
2008-09-01 18:40     ` Jaswinder Singh
2008-09-01 20:49       ` Dave Airlie
2008-09-02  5:06   ` Gene Heskett
  -- strict thread matches above, loose matches on Subject: below --
2008-08-30 17:39 Gene Heskett

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=200809020113.24058.gene.heskett@gmail.com \
    --to=gene.heskett@gmail.com \
    --cc=airlied@gmail.com \
    --cc=jaswinderlinux@gmail.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