All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Bug 40952] R100 firmware no longer loads
Date: Fri, 26 Aug 2011 09:40:39 +0100	[thread overview]
Message-ID: <CAPM=9twr5RfwoTYedZ4k+NR4K1AUFxGg9cVGmZizEyr91FQZ8Q@mail.gmail.com> (raw)
In-Reply-To: <201108252244.p7PMi0Ye018477@demeter2.kernel.org>

> --- Comment #10 from Linus Torvalds <torvalds@linux-foundation.org>  2011-08-25 22:43:53 ---
> On Thu, Aug 25, 2011 at 2:25 PM,  <bugzilla-daemon@bugzilla.kernel.org> wrote:
>>
>> Interestingly, the RS780 managed to load its firmware (also all compiled into
>> the kernel) even w/o this patch.
>
> Does the R600+ driver perhaps load firmware only at open time?
>
> The problem with the r100 driver is that it loads firmware very early
> on, at driver init time. Generally it's *much* better if you request
> the firmware when the device is actually opened, rather than when the
> driver loads.

That doesn't make any sense for radeon graphics drivers, since the
firmware is required to initialise the engines on the GPU, which you
really want to do so you can turn on the screen and stuff.

Dave.

  reply	other threads:[~2011-08-26  8:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 17:07 [Bug 40952] New: R100 firmware no longer loads bugzilla-daemon
2011-08-17 23:11 ` [Bug 40952] " bugzilla-daemon
2011-08-18  0:08 ` bugzilla-daemon
2011-08-18  7:25 ` bugzilla-daemon
2011-08-24 21:04 ` bugzilla-daemon
2011-08-24 21:57 ` bugzilla-daemon
2011-08-24 23:05 ` bugzilla-daemon
2011-08-24 23:54 ` bugzilla-daemon
2011-08-25  0:00 ` bugzilla-daemon
2011-08-25  1:07 ` bugzilla-daemon
2011-08-25 21:25 ` bugzilla-daemon
2011-08-25 22:44 ` bugzilla-daemon
2011-08-26  8:40   ` Dave Airlie [this message]
2011-08-26  8:34 ` bugzilla-daemon
2011-08-26  8:40 ` bugzilla-daemon
2011-08-26 12:33 ` bugzilla-daemon
2011-08-28 18:59 ` bugzilla-daemon

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='CAPM=9twr5RfwoTYedZ4k+NR4K1AUFxGg9cVGmZizEyr91FQZ8Q@mail.gmail.com' \
    --to=airlied@gmail.com \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.