#1781: [ath5k] Please add support for AR5418 (details included)
----------------------------------------+-----------------------------------
      Reporter:  [EMAIL PROTECTED]  |       Owner:                      
          Type:  task                   |      Status:  new                 
      Priority:  minor                  |   Milestone:                      
     Component:  ath5k                  |     Version:  trunk               
    Resolution:                         |    Keywords:  ath5k AR5418 MacBook
Patch_attached:  0                      |  
----------------------------------------+-----------------------------------
Comment (by anonymous):

 Replying to [comment:18 mrenzmann]:
 > Replying to [comment:16 anonymous]:
 > > Well, with the current "new-patch-speed" ath5k isn't going to replace
 madwifi in the next two years!
 >
 > What is your contribution again to speed up the development of ath5k?
 >
 Nothing. In fact I'm for the opposite direction, as there are lots
 of problems with the ath5k & mac80211 combo. And some of critical ones are
 in the mac80211-stack.

 e.g:
 - Regdomain/TPC/DFS (dot11d/dot11h) support is next to nil.
   Where is channel 13? What about the 5Ghz DFS/TPC frequencies?
   And this is a minefield! Especially since mac80211 doesn't
   enforce your countries limits, you could end with a big fine!
 - rate control algorithms?
   PID is a joke compared to minstrel or sample.
   Intel has even written their own rate code for their iwlwifi
   driver instead of "fixing the old one".
 - powersaving features don't exist either.
   Ask any laptop battery about PSPOLL/UAPSD.
 - MAC-ACL (iptables doesn't filter MLMEs) / WDS /
   VAPs (and not just cooked monitor devices!)
 - Accesspoint mode doesn't work at all if you last name isn't Berg,
   Busch, Wu, Slaby, Kossifidis or Rodriguez.
 - all the plugs for the nice bells and whistles like
   TurboG/A,FastFrame or eXtended Rates are missing.

 Most of this stuff has been in the net80211-stack for ages!

 So, good luck with your ongoing contributions, the problem
 isn't reverse engineering the driver (the HAL isn't really obfuscated and
 is much smaller than the blob from a
 green gfx maker.), but writing a good foundation!
 And don't tell me that it's hard to read the 802.11 specifications
 and write some lines of code for it!

-- 
Ticket URL: <http://madwifi.org/ticket/1781#comment:19>
madwifi.org <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets

Reply via email to