From: Ralf Baechle <ralf@linux-mips.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
linux-mips@linux-mips.org, florian@linux-mips.org,
Florian Fainelli <florian@openwrt.org>,
linux-arch@vger.kernel.org, Richard Henderson <rth@twiddle.net>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Matt Turner <mattst88@gmail.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
"David S. Miller" <davem@davemloft.net>,
sparclinux@vger.kernel.org
Subject: Re: SB16 build error.
Date: Thu, 30 Jun 2011 11:52:54 +0100 [thread overview]
Message-ID: <20110630105254.GA25732@linux-mips.org> (raw)
In-Reply-To: <s5h8vsjy68z.wl%tiwai@suse.de>
On Thu, Jun 30, 2011 at 12:15:56PM +0200, Takashi Iwai wrote:
> At Thu, 30 Jun 2011 10:17:54 +0100,
> Ralf Baechle wrote:
> >
> > Found on a MIPS build but certain other architectures will have the same
> > issue:
> >
> > CC sound/isa/sb/sb16_csp.o
> > sound/isa/sb/sb16_csp.c: In function ‘snd_sb_csp_ioctl’:
> > sound/isa/sb/sb16_csp.c:228: error: case label does not reduce to an integer constant
> > make[1]: *** [sound/isa/sb/sb16_csp.o] Error 1
> > make: *** [sound/isa/sb/sb16_csp.o] Error 2
> >
> > This error message is caused by the _IOC_TYPECHECK() error check triggering
> > due to excessive ioctl size on Alpha, PowerPC, MIPS and SPARC which define
> > _IOC_SIZEBITS as 13. On all other architectures define it as 14 so struct
> > snd_sb_csp_microcode with it's little over 12kB will just about fit into
> > the 16kB limit.
>
> What about the patch below?
I have no idea how big the soundblaster microcode being loaded actually is,
that is if the reduced size of 0x1f00 will be sufficient. Aside of that I
don't see a problem - I don't see how the old ioctl can possibly have been
used before so there isn't a compatibility problem.
Or you could entirely sidestep the problem and use request_firmware() but
I guess that's more effort than you want to invest.
> This is an old ISA driver, so the impact must be very low.
True. I notice that sort of stuff in automated mass builds - not
necessarily the sort of kernels one would actually use. Still build errors
are annoying :)
Ralf
next prev parent reply other threads:[~2011-06-30 10:53 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 [this message]
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 ` [alsa-devel] " Clemens Ladisch
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=20110630105254.GA25732@linux-mips.org \
--to=ralf@linux-mips.org \
--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=perex@perex.cz \
--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