RE: HEADSUP: ath updates

From: van Schalkwyk, Andre {PGIN~Kaiseraugst} (andre.van_schalkwyk_at_roche.com)
Date: 12/10/04

  • Next message: Pierre DAVID: "Re: HEADSUP: updated net80211 layer committed"
    Date: Fri, 10 Dec 2004 15:51:10 +0100
    To: "Sam Leffler" <sam@errno.com>, <freebsd-current@freebsd.org>
    
    

    Any idea when the ath_hal will support atheros 5213 chips?

    -andre

    -----Original Message-----
    From: owner-freebsd-current@freebsd.org
    [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Sam Leffler
    Sent: Wednesday, December 08, 2004 8:10 PM
    To: freebsd-current@freebsd.org
    Subject: HEADSUP: ath updates

    I just committed updates for the ath driver and the ath hal. There are
    many
    changes to this code including a split of the tx rate control algorithm
    into
    a separate module. This means that when statically configuring the
    driver
    you now need to specify:

    device ath
    device ath_hal
    device ath_rate_onoe

    to get the previous functionality (i.e. the previous rate control
    algorithm).
    There is a second rate control algorithm that is slightly different from
    the
    onoe algorithm; you can try that with

    device ath_rate_amrr

    However both of these algorithms are still rather lame and a good
    algorithm is
    needed. I encourage folks to step up and work on this as a good tx rate

    control algorithm makes all the difference.

    The new hal should support all shipping Atheros parts. Operation should
    be
    noticeably better and the driver supports all the functionality of the
    revised net80211 layer. This includes the security protocols (WPA,
    802.11i,
    802.1x), the QoS/Multi-media protocols (WME/WMM), and more.

    One problem to beware of is that WME and WPA currently do not work
    together
    (for AP operation at least). If you want to test out WPA be sure to
    disable
    wme--this will require the new ifconfig that I'll be committing shortly.

    There's still a bunch of work to do on the driver. I'll be working
    fulltime
    on this stuff for the next few months; mainly on AP support.

            Sam
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to
    "freebsd-current-unsubscribe@freebsd.org"
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


  • Next message: Pierre DAVID: "Re: HEADSUP: updated net80211 layer committed"

    Relevant Pages

    • Re: Wireless hardware support
      ... > manpage for athsays it is a supported card. ... > panic randomly with the driver loaded. ... > least revision B3 of this card ALSO is not supported by the ath ... has noticeably older ath support than -current. ...
      (freebsd-stable)
    • Re: AES with SslStream
      ... I can't remember which version of Windows is supposed to get that support, ... my understanding is that the AES types are still ... Aes The Advanced Encryption Standard algorithm. ...
      (microsoft.public.dotnet.security)
    • US-NJ-Imaging Physicist
      ... data and image processing in an ISO 13485 environment with strict ... support transition to real-time C-code.· ... Prepare software and algorithm documentation as needed.· ... the FDA's Quality System Regulation and the company's ISO ...
      (sci.physics)
    • RE: Password encryption
      ... For password encryption, could you let me know more about your application ... Because we usually don't need to use symmetric algorithm to ... Microsoft Online Community Support ...
      (microsoft.public.dotnet.framework)
    • Re: Interesting driver modification in win2k
      ... a filter driver would work here....BUT windows acceleration algorithm is ... > Writing a filter driver is a best idea IMHO. ...
      (microsoft.public.development.device.drivers)