Isn't Wifi supposed to be off by default?

[c_c]

Hi,
  Well, to experiment with what I have recently learnt here, I compiled my
own kernel after checking out origin/andy-tracking and got
uImage-moredrivers-GTA02_mystable_cd58517c962c0c65.bin.

  Booting with this kernel this gives me the usual 

Wakeups-from-idle per second : 533.6    interval: 5.0s

Top causes for wakeups:
  39.9% (212.6)       <interrupt> : s3c-mci 
  37.6% (200.6)       <interrupt> : S3C2410 Timer Tick 
  18.9% (100.6)    ksdioirqd/mmc1 : schedule_timeout (process_timeout) 
   1.8% (  9.8)            python : schedule_hrtimeout_range
(hrtimer_wakeup)
   0.5% (  2.6)       <interrupt> : s3c2410_udc
   0.2% (  1.0)        watchdog/0 : start_rt_bandwidth
(sched_rt_period_timer)
   0.2% (  1.0)     enlightenment : schedule_hrtimeout_range
(hrtimer_wakeup)
   0.2% (  1.0)            Xglamo : hrtimer_start (it_real_fn)
   0.2% (  1.0)       gsm0710muxd : schedule_hrtimeout_range
(hrtimer_wakeup)
   0.1% (  0.6)   <kernel module> : neigh_table_init_no_netlink
(neigh_periodic_timer)
   0.1% (  0.4)     <kernel core> : neigh_table_init_no_netlink
(neigh_periodic_timer)
   0.1% (  0.4)     <kernel core> : schedule_delayed_work_on
(delayed_work_timer_fn)
   0.1% (  0.4)            udhcpc : schedule_hrtimeout_range
(hrtimer_wakeup)
   0.0% (  0.2)          dropbear : sk_reset_timer (tcp_write_timer)
   0.0% (  0.2)      zzz-wireless : queue_delayed_work
(delayed_work_timer_fn)
   0.0% (  0.2)     <kernel core> : addrconf_mod_timer (addrconf_rs_timer)
   0.0% (  0.2)     <kernel core> : page_writeback_init (wb_timer_fn)
   0.0% (  0.2)            batget : schedule_hrtimeout_range
(hrtimer_wakeup)
   0.0% (  0.2)     <kernel core> : neigh_add_timer (neigh_timer_handler)
   0.0% (  0.2)           wifiget : do_nanosleep (hrtimer_wakeup)


But on doing rmmod ar6000, I get

Wakeups-from-idle per second : 219.0    interval: 5.0s

Top causes for wakeups:
  91.9% (201.0)       <interrupt> : S3C2410 Timer Tick 
   4.4% (  9.6)            python : schedule_hrtimeout_range
(hrtimer_wakeup)
   1.2% (  2.6)       <interrupt> : s3c2410_udc
   0.5% (  1.2)            Xglamo : hrtimer_start (it_real_fn)
   0.5% (  1.0)     enlightenment : schedule_hrtimeout_range
(hrtimer_wakeup)
   0.5% (  1.0)       gsm0710muxd : schedule_hrtimeout_range
(hrtimer_wakeup)
   0.3% (  0.6)   <kernel module> : neigh_table_init_no_netlink
(neigh_periodic_timer)
   0.2% (  0.4)     <kernel core> : schedule_delayed_work_on
(delayed_work_timer_fn)
   0.1% (  0.2)          dropbear : sk_reset_timer (tcp_write_timer)
   0.1% (  0.2)            Xglamo : schedule_hrtimeout_range
(hrtimer_wakeup)
   0.1% (  0.2)            batget : schedule_hrtimeout_range
(hrtimer_wakeup)
   0.1% (  0.2)     <kernel core> : page_writeback_init (wb_timer_fn)
   0.1% (  0.2)     <kernel core> : neigh_table_init_no_netlink
(neigh_periodic_timer)
   0.1% (  0.2)           wifiget : do_nanosleep (hrtimer_wakeup)
   0.1% (  0.2)                sh : get_transaction (commit_timeout)

That's quite an improvement. But S3C2410 Timer Tick is still going on at
200Hz. Is that normal?
-- 
View this message in context: http://n2.nabble.com/Isn%27t-Wifi-supposed-to-be-off-by-default--tp2154678p2157684.html
Sent from the Openmoko Kernel mailing list archive at Nabble.com.