On Tue, Mar 24, 2009 at 1:03 PM, Bob Copeland <me@xxxxxxxxxxxxxxx> wrote:
> On Tue, Mar 24, 2009 at 2:41 PM, Luis R. Rodriguez
> <lrodriguez@xxxxxxxxxxx> wrote:
>> Do any of you guys have time to pick it up?
>
> Well my patch #2 is pretty similar to what Christian has, and I'd like to
> upstream the first few patches soon (especially the ath.ko creation, it is a
> beast to rebase as you saw). That would bring up the first contentious
> point of the merge: is "ath/ath.ko" ok with everyone?
Yes.
> ath5k/9k specific
> bits can eventually go in ath/{5k,9k} subdirs... not sure where 9170
> lives then :)
Wherever Christian wants it. If he finds re-usable bits then great.
> I probably can't get to it until the weekend, but if you have more time,
> Christian, feel free to adopt whatever you want from mine. Otherwise I'll
> pick up where Luis left off on the weekend.
>
> I didn't push it yet because ath5k was having problems once I turned it
> on for ath5k,
So this is why I recommend to trim the channel list down of ath5k. The
other reason is you won't have users spending what may be 3/4 of their
time scanning on channels that they won't ever find APs in. What can
be done here is add flag or command as we had reviewed a while back
to allow the user to enable these channels if he knows what he is
doing so that way we know we don't mind bothering scanning on the
gazillion channels. But that is just my advice. My concern first is to
get users working happily and quickly associated to an AP and I think
that parallels those goals and puts as secondary the bells and
whistles of adding every single possible channel.
> and I have no other hardware to test with so wanted to
> figure out what was broken first.
> Channel list is a good hint, maybe
> it's time to fix iw/nl80211 to send back all the channels :)
So that is the other option. I tried looking at that yesterday but
wasn't able to find a way to do this. I went through the netlink
documenation and even tried modifying the skb on the kernel side as
its a dump. Not sure what to do here to fix this.
So yes, both are possible options. Just keep in mind that without
being able to see the channel list with 'iw list' debugging regulatory
is a real royal pain in the ass. So I'd try to fix that first either
through channel reduction (you get another bonus enhancement for
scanning time for users) or through fixing this through iw/nl80211.
Johannes probably can advise best on the second path.
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
