Search Linux Wireless

Re: [ipw3945-devel] iwl3945 doesn't work

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

 



On 10/18/07, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote:
> On Thu, 2007-10-18 at 08:23 -0400, Stephen Clark wrote:
>
> > >>iwlist eth1 scan would report no scan results, I then switched to loading
> > >>the kernel module with
> > >>the option that tells  iwl3945 to do software scanning and it works
> > >>everytime now.
>
> > In my modprobe.conf file:
> > options iwl3945 disable_hw_scan=1
>
> Hah. Told you it wasn't mac80211's problem. Can somebody remind me again
> exactly why we have hardware scan offload when we parse each received
> packet anyway and the hardware doesn't even batch them so the CPU could
> wake up less?
>
1. Tuning to each channel is done internally by fw so you don't spend
cycles and it's is faster to switch channels so overall scanning take
less time. Sending probe responses is also offloaded.  Returning to
operational channel is more precisely matched to DTIM period as it is
handled by RT code.
2. There are also more advanced modes of scanning such as during voice
traffic etc.
3. Yes beacon batching will be nice, but there is a memory tradeoff.
Tomas

> johannes
>
>
-
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