Date: Tue, 1 Dec 2009 16:40:56 +0100 From: Paul B Mahol <onemda@gmail.com> To: John Hay <jhay@meraka.org.za> Cc: freebsd-net@freebsd.org Subject: Re: wlan adhoc mode crash Message-ID: <3a142e750912010740wc69464btbdeea834b0d4e516@mail.gmail.com> In-Reply-To: <20091201104951.GA42629@zibbi.meraka.csir.co.za> References: <20091201104951.GA42629@zibbi.meraka.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/1/09, John Hay <jhay@meraka.org.za> wrote: > Hi, > > I'm not sure if this is the best list. > > I'm trying to get our Avila (arm) boards with atheros wireless cards > upgraded from 7.2 to 8.0. We use adhoc mode and I get a panic in > ieee80211_getcapinfo() because the chan pointer is 0xffff which seems > to mean IEEE80211_CHAN_ANY in other places. So the question is, should > ieee80211_getcapinfo() never be called with chan being 0xffff or should > it know how to handle that case? IEEE80211_CHAN_ANY is there to mean no channel is selected, so you can not call getcapinfo with such argument.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750912010740wc69464btbdeea834b0d4e516>