From: Denis V. <vd...@il...> - 2006-01-07 19:43:12
|
On Saturday 07 January 2006 21:30, Andreas Mohr wrote: > Hi, > > On Sat, Jan 07, 2006 at 04:49:34PM +0200, Matan Peled wrote: > > Denis Vlasenko wrote: > > >There was, among other changes, this one: > > > > > > priv->scan_duration = 100; > > >- priv->scan_probe_delay = 200; > > >+ priv->scan_probe_delay = priv->cfgopt.probe_delay; > > > priv->scan_rate = ACX_SCAN_RATE_1; > > > > > >Try reverting it. > > >-- > > >vda > > > > > > > Yup, that worked just fine! common.c, line 2140 or so. > Then we definitely need to log probe_delay in parse_configopt, too, > and then later once it's known what values can occur in EEPROMs > limit it within sane limits. EEPROM even says "acx100" on practically all acx111's. Can it be trusted at all? -- vda |