Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kuzmenko <linux@solonet.org.ua>
To: Borislav Petkov <bp@alien8.de>,
	anish kumar <anish198519851985@gmail.com>,
	"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 20:01:34 +0200	[thread overview]
Message-ID: <4ECA91FE.7010200@solonet.org.ua> (raw)
In-Reply-To: <20111121153947.GA8102@x1.osrc.amd.com>

On 11/21/2011 05:39 PM, Borislav Petkov wrote:
> 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.
> 

You can also put it into intramfs and use usual request_firmware call.

-- 
Best regards, Denis Kuzmenko.

      reply	other threads:[~2011-11-21 18:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1321542430-17971-1-git-send-email-pdeschrijver@nvidia.com>
     [not found] ` <74CDBE0F657A3D45AFBB94109FB122FF1740D74C1E@HQMAIL01.nvidia.com>
     [not found]   ` <20111118120352.GZ19069@tbergstrom-lnx.Nvidia.com>
     [not found]     ` <74CDBE0F657A3D45AFBB94109FB122FF1740D74E63@HQMAIL01.nvidia.com>
     [not found]       ` <20111121122212.GL19069@tbergstrom-lnx.Nvidia.com>
2011-11-21 15:28         ` Firmware during bootup anish kumar
2011-11-21 15:39           ` Borislav Petkov
2011-11-21 18:01             ` Denis Kuzmenko [this message]

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=4ECA91FE.7010200@solonet.org.ua \
    --to=linux@solonet.org.ua \
    --cc=alsa-devel@alsa-project.org \
    --cc=anish198519851985@gmail.com \
    --cc=bp@alien8.de \
    --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