Searched full:wildly (Results 1 – 22 of 22) sorted by relevance
15 because sometimes these LED drivers are used for wildly different things than
67 * are wildly different...
10 * depends wildly on alignment on many x86 processors. The additional
289 /* Danger! My arms are flailing wildly! You *must* set lp->reg_offset in mac_onboard_sonic_probe()454 /* Danger! My arms are flailing wildly! You *must* set lp->reg_offset in mac_sonic_nubus_probe_board()
198 However, because the devices vary wildly, you might happen to have a
299 * because the symbol error count will increment wildly if there in igc_init_hw_base()
97 what happens then. The screen will be probably flashing wildly for some time and
203 up of the driver was tuned to handle slaves with wildly different
165 * on hardware pages present on the Mac web site. Possibly wildly
822 * because the symbol error count will increment wildly if there in e1000_init_hw_80003es2lan()
1129 * because the symbol error count will increment wildly if there in e1000_init_hw_82571()
4900 * because the symbol error count will increment wildly if there in e1000_init_hw_ich8lan()
1195 * wildly and even change during runtime when the underlying devices are
216 * Without this bit of weirdness moving up gives wildly in psmouse_process_byte()
2095 * Except for wildly misbehaving hardware, or if it was disconnected in xillyusb_discovery()
998 * that is 16 times the baud rate -- and that is wildly outside the in r9a06g032_div_determine_rate()
1551 * because the symbol error count will increment wildly if there in igb_init_hw_82575()
1258 * have also wildly different syntax and how nesting of them are done. See
148 /* reject a wildly large period */ in rvt_wss_init()
621 * because the symbol error count will increment wildly if there in e1000_init_hw()
295 reservation step due to wildly incorrect summary counters.
2894 * This function is wildly self concurrent; here be dragons.