On Wed, 2008-07-23 at 05:13 -0700, Luis R. Rodriguez wrote:
> > Maybe MacBook Pro's card has different eeprom's contents? Anyway the
> > card now works fine, and it also appears quite stable! ;-)
> > Thank you very much for your work!
>
> I believe your last patch may have been "Use skb_end_pointe
cleanup the rates structures used by ath5k. instead of separate driver and
mac80211 rate structures we now setup a static ieee80211_rate array and use it
directly. no conversion between two different rate structures has to be done
any more. a lot of unused and confusing junk was deleted.
renamed a
On Wed, Jul 23, 2008 at 7:17 AM, Jiri Slaby <[EMAIL PROTECTED]> wrote:
> Commit 9d139c810a2aa17365cc548d0cd2a189d8433c65 introduced
> AA deadlock -- ath5k_config_interface(); holds sc->lock
> and it calls ath5k_beacon_update(); which tries to grab the
> lock again.
I already posted a patch for thi
On Tue, Jul 22, 2008 at 2:53 PM, Davide Pesavento <[EMAIL PROTECTED]> wrote:
> Great news!
>
> Today I applied ath9k patches on top of linux-wireless git tree on a
> MacBookPro2,2 and I found that it works! (after a little bit of
> hacking...)
>
> First of all, my hardware is the following:
>
> # l
On Wed, Jul 23, 2008 at 2:35 AM, YanBo <[EMAIL PROTECTED]> wrote:
> On Wed, Jul 23, 2008 at 5:24 PM, David Goodenough
> <[EMAIL PROTECTED]> wrote:
>> I have recently noticed mention of ath9k, but on the madwifi home page
>> there is only mention of ath5k. Even a search of the madwifi wiki brings
>
There were 3 code copy and pastes of reset. Unify the resets and place
in separate function.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
Cc: Nick Kossifidis <[EMAIL PROTECTED]>
Cc: Luis R. Rodriguez <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath5k/base.c | 124 +--
Commit 9d139c810a2aa17365cc548d0cd2a189d8433c65 introduced
AA deadlock -- ath5k_config_interface(); holds sc->lock
and it calls ath5k_beacon_update(); which tries to grab the
lock again.
Don't grab the lock in beacon update, since only caller is
config iface for now.
Signed-off-by: Jiri Slaby <[E
Mask out previously demanded interrupt flags because we set
new ones. Don't allow mixing them after switch from sta to
ibss and vice versa.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
Cc: Nick Kossifidis <[EMAIL PROTECTED]>
Cc: Luis R. Rodriguez <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath5
On Friday 18 July 2008 20:19:06 Nick Kossifidis wrote:
> 2008/7/17 Bruno Randolf <[EMAIL PROTECTED]>:
> > hi!
> >
> > this is just a preview and a RFC. i would like to know what you think
> > about the general approach and will send a cleaned up version for final
> > review later.
>
> I fully agree
On Wed, Jul 23, 2008 at 5:24 PM, David Goodenough
<[EMAIL PROTECTED]> wrote:
> I have recently noticed mention of ath9k, but on the madwifi home page
> there is only mention of ath5k. Even a search of the madwifi wiki brings
> up no hits.
>
> I presume it is an evolution of ath5k, or was it found
I have recently noticed mention of ath9k, but on the madwifi home page
there is only mention of ath5k. Even a search of the madwifi wiki brings
up no hits.
I presume it is an evolution of ath5k, or was it found that atheros had
produces a new generation of chips that required a rewrite?
David
__
Great news!
Today I applied ath9k patches on top of linux-wireless git tree on a
MacBookPro2,2 and I found that it works! (after a little bit of
hacking...)
First of all, my hardware is the following:
# lspci -v
03:00.0 Network controller: Atheros Communications Inc. AR5418
802.11abgn Wireless P
12 matches
Mail list logo
