Re: Atheros, hardware access layer, collisions

From: Sam Leffler (sam_at_errno.com)
Date: 07/26/05

  • Next message: jason henson: "using -ftracer stops buildworld at shutdown.c"
    Date: Tue, 26 Jul 2005 11:55:47 -0700
    To: David Malone <dwmalone@maths.tcd.ie>
    
    

    David Malone wrote:
    >>I just had a lengthy discussion with a couple of guys about the 802.11
    >>protocol. One had said that the random delays inserted before
    >>transmission was one of the *IFS delays (can't remember which
    >>now), and that it was a standard 802.11 number, not a random
    >>delay.
    >
    >
    > Yep - in 802.11b CWmin is fixed at 32 and the random number is
    > chosen between 0 and CWmin-1 (unless you have a collision). The
    > recent Atheros cards support adjusting CWmin as part of their
    > WME/802.11e support.

    Well "recent" is any 5212 or 5211 card so you're talking about any
    Atheros card except the 5210--which is not so recent. It may also be
    possible to program the 5210 but given how few of them are in use it's
    hardly worth the effort (and they'll never support WME).

    >
    >
    >>The thing he said was that if carrier sensing "sensed" that the channel
    >>was busy, it would not decrement the CW, effectively NOT transmitting
    >>this packet until the channel is clear.
    >
    >
    > That's correct, but it probably takes a few microseconds for the
    > carries sense to kick in (if there wasn't a delay there would
    > be almost no need for the random backoff). That's why you'll
    > also have to have your transmissions synchronised very closely.
    >
    >
    >>Is the carrier sensing something done in the HAL, or is it embedded
    >>in the hardware itself?
    >
    >
    > I'm afraid I don't know - Sam might.

    Hardware.

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


  • Next message: jason henson: "using -ftracer stops buildworld at shutdown.c"

    Relevant Pages

    • Re: 2.6.14-rc4-mm1
      ... hw_random hardware driver 1.0.0 loaded ... NET: Registered protocol family 23 ... # Firmware Drivers ... # ACPI Support ...
      (Linux-Kernel)
    • Re: A9 Home
      ... If it didn't support the USB 2 protocol it ... The if the driver of the USB 1.1 hardware ...
      (comp.sys.acorn.hardware)
    • Re: rt20 scheduling latency testcase and failure data
      ... The system was under heavy network load for some of the time, ... # Firmware Drivers ... # ACPI Support ... # ISDN4Linux hardware drivers ...
      (Linux-Kernel)
    • NMI watchdog doesnt know what hardware to touch
      ... NMI watchdog doesn't know what hardware to touch ... Linux 2.6.24-rc5-g4af75653 on x86_64 ... # SCSI support type ... # Input Device Drivers ...
      (Linux-Kernel)
    • Re: Linux 2.6.20-rc2
      ... corruption (either hardware or kernel induced) that could cause this. ... So my guess would still be memory corruption of some sort, ... # ACPI Support ...
      (Linux-Kernel)