From: Michael Buesch <mb@bu3sch.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-wireless@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: drivers/net/wireless/b43legacy/ on mips
Date: Tue, 4 Mar 2008 16:26:03 +0100 [thread overview]
Message-ID: <200803041626.03830.mb@bu3sch.de> (raw)
In-Reply-To: <20080303233651.82c592a4.akpm@linux-foundation.org>
On Tuesday 04 March 2008 08:36:51 Andrew Morton wrote:
>
> ERROR: "__ucmpdi2" [drivers/net/wireless/b43legacy/b43legacy.ko] undefined!
> ERROR: "__ucmpdi2" [drivers/net/wireless/b43/b43.ko] undefined!
>
> int b43legacy_dma_init(struct b43legacy_wldev *dev)
> {
> struct b43legacy_dma *dma = &dev->dma;
> struct b43legacy_dmaring *ring;
> int err;
> u64 dmamask;
> enum b43legacy_dmatype type;
>
> dmamask = supported_dma_mask(dev);
> switch (dmamask) {
> default:
> B43legacy_WARN_ON(1);
> case DMA_30BIT_MASK:
> type = B43legacy_DMA_30BIT;
> break;
> case DMA_32BIT_MASK:
> type = B43legacy_DMA_32BIT;
> break;
> case DMA_64BIT_MASK:
> type = B43legacy_DMA_64BIT;
> break;
> }
>
> because some versions of gcc emit a __ucmpdi2 call for switch statements.
> It might be fixable by switching to an open-coded if/compare/else sequence.
I guess that's only done for a 64bit data type, right?
> Or maybe my mips compiler (gcc-3.4.5) is just too old..
Well yeah. b43 uses exactly the same code and we use that in openwrt
on the bcm47xx mips platform with some 4.x compiler.
Can we switch off the generation of the __ucmpdi2 call somehow?
Or can we insert an implementation for it? Probably #ifdefed by the
compiler version.
--
Greetings Michael.
prev parent reply other threads:[~2008-03-04 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 7:36 drivers/net/wireless/b43legacy/ on mips Andrew Morton
2008-03-04 9:02 ` Ralf Baechle
2008-03-04 9:19 ` Andrew Morton
2008-03-04 15:26 ` Michael Buesch [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=200803041626.03830.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=akpm@linux-foundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=ralf@linux-mips.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;
as well as URLs for NNTP newsgroup(s).