All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 40952] R100 firmware no longer loads
Date: Wed, 24 Aug 2011 21:57:55 GMT	[thread overview]
Message-ID: <201108242157.p7OLvtWc020757@demeter1.kernel.org> (raw)
In-Reply-To: <bug-40952-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=40952





--- Comment #4 from Linus Torvalds <torvalds@linux-foundation.org>  2011-08-24 21:57:45 ---
On Wed, Aug 24, 2011 at 2:04 PM,  <bugzilla-daemon@bugzilla.kernel.org> wrote:
>
> --- Comment #3 from Michel Dänzer <michel@daenzer.net>  2011-08-24 21:03:48 ---
> From Elimar Riesebieter (riesebie at lxtec.de):
>
> bisecting brought me to commit
> 288d5abec8314ae50fe6692f324b0444acae8486. Reverting seems to work as
> microcode is loaded with compiled in firmware and radeon kms driver.

Grr.

So _request_firmware() does this:

        if (WARN_ON(usermodehelper_is_disabled())) {
                dev_err(device, "firmware: %s will not be loaded\n", name);
                return -EBUSY;
        }

which is reasonable, but it does mean that it will warn even if the
firmware is built into the kernel.

On the one hand, that's really nice, because it implies a driver does
a firmware load too early, at a point where it cannot do the generic
firmware load.

On the other hand, it sucks, because it does disallow this situation
that used to work, now that we actually do the sane thing and don't
allow usermode helpers before init has been set up.

So I bet the attached patch fixes the R100 problem, but I'm not 100%
happy with it.

Comments?

                               Linus

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2011-08-24 21:57 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 [this message]
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
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=201108242157.p7OLvtWc020757@demeter1.kernel.org \
    --to=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.