Search Linux Wireless

Re: [ath5k-devel] [PATCH 1/1] ath5k: Cleanup after API changes patch

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

 



2008/2/1 Johannes Berg <johannes@xxxxxxxxxxxxxxxx>:
>
> > > What is cap_range and why should it be in struct wiphy?
> >
> > Its the device's frequency capability range on the bands.
>
> Well since we always need channels I decided to not have such a thing
> but rather require registering a channels array that is also used for
> bookkeeping about enabled/disabled channels etc.
>
> I guess you could add a helper function that allocates a channels array
> based on a frequency range.

This is true but also it would be nice as it is the end points which
drivers may want
to access every now and then. I think its worth the few bytes.

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