From: Clemens Ladisch <clemens@ladisch.de>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Mike Frysinger <vapier@gentoo.org>,
Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org,
uclinux-dist-devel@blackfin.uclinux.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] firmware: Make firmware drivers generally available
Date: Fri, 17 Jun 2011 15:16:35 +0200 [thread overview]
Message-ID: <4DFB53B3.8070806@ladisch.de> (raw)
In-Reply-To: <1308310831-27861-1-git-send-email-lars@metafoo.de>
Lars-Peter Clausen wrote:
> Currently only x86, ia64 and blackfin architectures include
> drivers/firmware/Kconfig, as a result firmware drivers are only available on
> these platforms. This has not been a problem historically, because all of the
> firmware drivers were architecture specific.
>
> But this has changed with the addition of the SigmaStudio firmware loader
> (commit e359dc24 "sigma-firmware: loader for Analog Devices' SigmaStudio"),
> which is used to parse and load firmware files for Analog Devices' SigmaDSP
> processors.
It looks as if sigma.c doesn't actually belong into drivers/firmware.
That directory is for code that lets the kernel access the firmware
of the platform that the kernel itself runs on.
The request_firmware() stuff is usually part of the actual driver that
needs it.
Regards,
Clemens
next prev parent reply other threads:[~2011-06-17 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110617103218.GA29723@opensource.wolfsonmicro.com>
2011-06-17 11:40 ` [PATCH] firmware: Make firmware drivers generally available Lars-Peter Clausen
2011-06-17 13:16 ` Clemens Ladisch [this message]
2011-06-17 15:56 ` Mike Frysinger
2011-06-17 18:11 ` Clemens Ladisch
2011-06-17 18:25 ` Mike Frysinger
2011-06-21 0:35 ` Mark Brown
2011-06-21 1:45 ` [uclinux-dist-devel] " Mike Frysinger
2011-06-17 15:56 ` Mike Frysinger
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=4DFB53B3.8070806@ladisch.de \
--to=clemens@ladisch.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=lars@metafoo.de \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.org \
--cc=x86@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