[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080825120502.GA13700@deprecation.cyrius.com>
Date: Mon, 25 Aug 2008 15:05:02 +0300
From: Martin Michlmayr <tbm@...ius.com>
To: Florian Fainelli <florian.fainelli@...ecomint.eu>,
Sten Wang <sten.wang@....com.tw>
Cc: netdev@...r.kernel.org
Subject: r6040: bad udelay call, build failure on ARM with R6040=m
r6040 fails to build on ARM with:
ERROR: "__bad_udelay" [drivers/net/r6040.ko] undefined!
make[1]: *** [__modpost] Error 1
__bad_udelay is specifically designed on ARM to fail when udelay is
called in a bad way. arch/arm/include/asm/delay.h has this to say
about __bad_udelay:
/*
* This function intentionally does not exist; if you see references to
* it, it means that you're calling udelay() with an out of range value.
*
* With currently imposed limits, this means that we support a max delay
* of 2000us. Further limits: HZ<=1000 and bogomips<=3355
*/
extern void __bad_udelay(void);
Can you check why your driver is calling udelay() with a value > 2000?
--
Martin Michlmayr
http://www.cyrius.com/
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists