From: Greg KH <gregkh@linuxfoundation.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Dave Jones <davej@redhat.com>, Ming Lei <ming.lei@canonical.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: dell_rbu: Select CONFIG_FW_LOADER_USER_HELPER explicitly
Date: Mon, 8 Jul 2013 09:49:33 -0700 [thread overview]
Message-ID: <20130708164933.GB12670@kroah.com> (raw)
In-Reply-To: <s5h4nc5bewf.wl%tiwai@suse.de>
On Mon, Jul 08, 2013 at 11:05:20AM +0200, Takashi Iwai wrote:
> The reason is that dell_rbu driver requires it. Without the kconfig
> option, this driver won't work at all. So, it's a right fix for
> dell_rbu.
>
> AFAIK, the consensus in the kernel side is that this too long fw
> loading time is basically a regression of user-space (udev or
> whatever). There is no change in the kernel behavior. The problem
> must exist even with the older kernels.
>
> But, looking at the development, we can't expect that udev will be
> fixed soon, and this breakage persists already way too long. Maybe a
> better solution is to kill the fallback to udev for normal f/w loading
> (i.e. for distro kernels).
I thought udev was already fixed for this issue, so why would a "modern"
distro need to worry about this?
> The patch below is an untested quick hack. It adds a new Kconfig and
> a new function request_firmware_via_user_helper(). Distro kernels may
> set CONFIG_FW_LOADER_USER_HELPER_FALLBACK=n for avoiding 60 seconds
> stall for non-existing firmware file access -- as distributions know
> that the firmware files should be placed in the right path.
>
> Thoughts?
There's no way we can just fix up the driver instead of doing this in
the firmware core?
thanks,
greg k-h
next prev parent reply other threads:[~2013-07-08 16:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130702192749.A2E7E660D9B@gitolite.kernel.org>
2013-07-06 22:14 ` Dave Jones
2013-07-06 22:30 ` Greg KH
2013-07-08 9:05 ` Takashi Iwai
2013-07-08 16:49 ` Greg KH [this message]
2013-07-08 17:52 ` Takashi Iwai
2013-07-09 3:15 ` Ming Lei
2013-07-09 5:33 ` Takashi Iwai
2013-07-09 8:43 ` Ming Lei
2013-07-09 13:32 ` Takashi Iwai
2013-07-09 14:39 ` Ming Lei
2013-07-09 14:45 ` Takashi Iwai
2013-07-09 15:06 ` Ming Lei
2013-07-09 15:13 ` Takashi Iwai
2013-07-09 15:22 ` Ming Lei
2013-07-09 15:26 ` Takashi Iwai
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=20130708164933.GB12670@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®