Search Linux Wireless

Re: ath5k: bad udelay call, build failure on ARM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* John W. Linville <linville@xxxxxxxxxxxxx> [2008-08-25 15:08]:
> There are "udelay(2300)" calls in phy.c and hw.c.  How important is
> that exact number?  Could those be replaced by mdelay(3) instead?
> 
> Of course, looking in include/linux/delay.h, mdelay(3) may still
> translate to __bad_udelay on arm.

mdelay(3) compiles on ARM, so replacing the udelay(2300) with
mdelay(3) might be an option. (I don't have the hardware to test
though.)
-- 
Martin Michlmayr
http://www.cyrius.com/
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux