From: Clemens Ladisch <clemens@ladisch.de>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Takashi Iwai <tiwai@suse.de>,
linux-arch@vger.kernel.org, linux-mips@linux-mips.org,
alsa-devel@alsa-project.org, florian@linux-mips.org,
"David S. Miller" <davem@davemloft.net>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel@vger.kernel.org,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
sparclinux@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Matt Turner <mattst88@gmail.com>,
Florian Fainelli <florian@openwrt.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [alsa-devel] SB16 build error.
Date: Thu, 30 Jun 2011 15:10:21 +0200 [thread overview]
Message-ID: <4E0C75BD.1050103@ladisch.de> (raw)
In-Reply-To: <20110630105254.GA25732@linux-mips.org>
Ralf Baechle wrote:
> I have no idea how big the soundblaster microcode being loaded actually is,
> that is if the reduced size of 0x1f00 will be sufficient.
The biggest file is WFM0001A.CSP with 0x2df0 bytes.
> I don't see how the old ioctl can possibly have been
> used before so there isn't a compatibility problem.
The code uses SNDRV_SB_CSP_MAX_MICROCODE_FILE_SIZE but doesn't care what
the size field of the ioctl code is, so we could use any random value on
those architectures.
> Or you could entirely sidestep the problem and use request_firmware()
> but I guess that's more effort than you want to invest.
The driver already implements this for a bunch of predefined CSP code
blobs. I'm not sure whether anybody has ever loaded additional .csp
files.
Regards,
Clemens
prev parent reply other threads:[~2011-06-30 13:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 9:17 SB16 build error Ralf Baechle
2011-06-30 10:15 ` Takashi Iwai
2011-06-30 10:52 ` Ralf Baechle
2011-06-30 11:05 ` Takashi Iwai
2011-06-30 11:28 ` Takashi Iwai
2011-06-30 12:32 ` Ralf Baechle
2011-06-30 12:38 ` Takashi Iwai
2011-06-30 12:43 ` Ralf Baechle
2011-06-30 13:14 ` Takashi Iwai
2011-07-01 15:31 ` David Howells
2011-06-30 12:54 ` Arnd Bergmann
2011-06-30 13:10 ` Clemens Ladisch [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=4E0C75BD.1050103@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=florian@linux-mips.org \
--cc=florian@openwrt.org \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mattst88@gmail.com \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=rth@twiddle.net \
--cc=sparclinux@vger.kernel.org \
--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