From: Borislav Petkov <bp@alien8.de>
To: anish kumar <anish198519851985@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
alsa-devel@alsa-project.org
Subject: Re: Firmware during bootup
Date: Mon, 21 Nov 2011 16:39:47 +0100 [thread overview]
Message-ID: <20111121153947.GA8102@x1.osrc.amd.com> (raw)
In-Reply-To: <1321889298.1760.8.camel@anish-Inspiron-N5050>
On Tue, Nov 22, 2011 at 12:28:18AM +0900, anish kumar wrote:
> Hello Everyone,
>
> I have a hardware(Noise processing chip) for which I am
> writing the driver.Is it a good idea to download the
> firmware in probe function by spawing kthread?I can't download
> the firmware using request_firmware api as this hardware
> is required during bootup for boot-up sound and request_firmware
> is out of question because of no support in user-space.
>
> Am i missing something?I am bit concerned about boot-up time
> as well.
You could build it into the kernel, see CONFIG_EXTRA_FIRMWARE Kconfig
help for this.
--
Regards/Gruss,
Boris
next prev parent reply other threads:[~2011-11-21 15:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 15:07 [PATCH] arm/tegra: convert tegra20 to GIC devicetree binding Peter De Schrijver
2011-11-17 15:44 ` Rob Herring
2011-11-17 15:54 ` Peter De Schrijver
[not found] ` <CACxGe6ub2QBO0ZLwNdSvMxP1U087pqL-qL+dfWAbn-08gBQyvg@mail.gmail.com>
2011-11-17 17:15 ` Rob Herring
2011-11-17 20:41 ` Grant Likely
2011-11-17 18:51 ` Stephen Warren
2011-11-18 12:03 ` Peter De Schrijver
2011-11-18 12:03 ` Peter De Schrijver
2011-11-18 16:25 ` Stephen Warren
2011-11-21 12:22 ` Peter De Schrijver
2011-11-21 15:28 ` Firmware during bootup anish kumar
2011-11-21 15:39 ` Borislav Petkov [this message]
2011-11-21 18:01 ` Denis Kuzmenko
2011-11-21 17:20 ` [PATCH] arm/tegra: convert tegra20 to GIC devicetree binding Stephen Warren
2011-11-23 5:00 ` Peter De Schrijver
2011-11-23 17:25 ` Stephen Warren
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=20111121153947.GA8102@x1.osrc.amd.com \
--to=bp@alien8.de \
--cc=alsa-devel@alsa-project.org \
--cc=anish198519851985@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