On 06-08-15 18:38 Michael Buesch wrote: > On Tuesday 15 August 2006 18:29, Dan Williams wrote: > > o Separate attributes for channel and frequency > > No, channel and freq is the same. It's just another name > for the same child. I would say we only want to deal with channel numbers > in the API. That's much easier, as we don't have to deal with this > fixed-point (or even floating point) mess. Look at WE for the > fixed-point mess. > The userspace tools can easily convert freq to channel and back. > And in the kernel, we can easily provide some small function > to convert from channel to khz and back, for example. But I would > like to see the fixed-point stuff in the API vanish. > > > o Method of finding out channel <-> frequency mapping (not all drivers > > support this in the SIOCGIWRANGE handler now) > > Yes, that would be a good idea. > Comes next to the conversion function (see above).
Channel to frequency mapping is defined by 802.11. So we could get rid of frequencies totally in the user interface and it will also help with compliance to regulatory rules. Or are here people, who really want to freely transmit on all frequencies their RF might be able to generate? -- Uli Kunitz - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
