On Fri, Sep 21, 2007 at 05:33:42PM -0400, Luis R. Rodriguez wrote:
> > > + * ieee80211_channel - internal structure definiton for an IEEE-802.11 channel
> > > + *
> > > + * This defines an ieee80211_channel. The IEEE-802.11 regulatory domain agent
> > > + * is in charge of filling most of these fields out. The low-level driver
> > > + * is expected to fill in, if needed, the val field. Note that val is already
> > > + * set by the regulatory agent to the same channel as in chan.
> >
> > Shouldn't you also set chan and freq in the driver?
[...]
> Initially I wanted to move mac80211 to use a linked list of channels
> instead of an array for each mode. As we discussed it over (you, me
> and a few others) we determined it wasn't best to do this (I have a
> patch that allows this just in case we later change our mind). But --
> previous to doing this I had a wrapper on ieee80211_channel as I
> wanted the central regdomain to have a linked list of reg domain
> channels. If we don't want a wrapper we have to add this to the
> ieee8021_channel struct. Otherwise I need to define my own channel
> struct which wraps around ieee80211_channel.
>
> > > +struct ieee80211_channel {
> > > + /* XXX change to u8 */
> > > + short chan;
> >
> > Not sure, is a u8 always enough? I thought 802.11a had huge channel
> > numbers?
>
> Not that huge :-) Highest I've heard is 220. u8 should suffice.
What's the idea of working with channels? Channels are non-uniq numbers.
Internally everything should work with center frequency and not with
channels. If necessary, information should be converted from channels
by the driver when reporting it into the stack. That way there also won't
be any problems if there ever is a channel 417.
ciao
Joerg
-
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
