Re: [OpenWrt-Devel] [PATCH 2/2] madwifi: make hal, bus and rate control configurable

2008-05-18 Thread Felix Fietkau
Axel Gembe wrote:
 This patch adds a number of configuration options to the MadWifi package. You 
 can
 now configure the HAL, bus, default rate control algorithm as well as the 
 debug
 mode from within make menuconfig. The goal is to be able to support hardware
 profiles with different HALs without messing around with the Makefile 
 directly.
I know the patch has been merged, but I'd still like to know: What would 
that be useful for? Just a hint: The next public HAL release will support 
all 5312+ and 2315+ SoC with a single binary. It seems to me that this adds 
unnecessary configuration complexity.

- Felix
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] [PATCH 2/2] madwifi: make hal, bus and rate control configurable

2008-05-18 Thread Axel Gembe
Felix Fietkau wrote:
 I know the patch has been merged, but I'd still like to know: What would 
 that be useful for? Just a hint: The next public HAL release will support 
 all 5312+ and 2315+ SoC with a single binary. It seems to me that this adds 
 unnecessary configuration complexity.
   
If this really bugs you, remove it. I can manage to have a local branch
with just AP43, but its not for the average user.
You're right about that it is unnecessary when the next HAL will support
all SoCs, I didn't know about this.
I mainly needed this for a DWL2100-AP which uses AP43.
Anyways, I still think the rate control configuration is useful for
experimenting with it.

 - Axel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] [PATCH 2/2] madwifi: make hal, bus and rate control configurable

2008-05-18 Thread Felix Fietkau
Axel Gembe wrote:
 If this really bugs you, remove it. I can manage to have a local branch
 with just AP43, but its not for the average user.
 You're right about that it is unnecessary when the next HAL will support
 all SoCs, I didn't know about this.
 I mainly needed this for a DWL2100-AP which uses AP43.
Support for changing the HAL is fine for now. I'll leave it in until the 
new HAL hits OpenWrt and madwifi.org (soon)
But why support for overriding the bus type?

 Anyways, I still think the rate control configuration is useful for
 experimenting with it.
ACK. Though after my changes, minstrel should perform a bit better than the 
alternatives.

- Felix
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] [PATCH 2/2] madwifi: make hal, bus and rate control configurable

2008-05-14 Thread Travis Kemen
Axel Gembe wrote:
 This patch adds a number of configuration options to the MadWifi package. You 
 can
 now configure the HAL, bus, default rate control algorithm as well as the 
 debug
 mode from within make menuconfig. The goal is to be able to support hardware
 profiles with different HALs without messing around with the Makefile 
 directly.
 
 Signed-off-by: Axel Gembe [EMAIL PROTECTED]
 ---
  package/madwifi/Config.in |  152 
 +
  package/madwifi/Makefile  |  144 --
  2 files changed, 261 insertions(+), 35 deletions(-)
  create mode 100644 package/madwifi/Config.in
 
 diff --git a/package/madwifi/Config.in b/package/madwifi/Config.in
 new file mode 100644
 index 000..d2bc4e0
 --- /dev/null
 +++ b/package/madwifi/Config.in
 @@ -0,0 +1,152 @@
 +# MadWifi configuration
 +
 +config MADWIFI_DEBUG
 + bool Enable compilation of debugging features
 + depends on EXPERIMENTAL
 + default n
 +
 +choice
 + prompt Bus selection
 + default MADWIFI_BUS_DEFAULT
 + help
 +   This option controls how MadWifi communicates with the hardware.
 +
 +config MADWIFI_BUS_DEFAULT
 + bool Use default bus
 + help
 +   This makes MadWifi determine the needed bus based on the target
 +   hardware. This will generally work most of the time, but there are 
 some
 +   cases where you need to override it.
 +
 +config MADWIFI_BUS_PCI
 + bool Use PCI bus
 + depends on PCI_SUPPORT
 +
 +config MADWIFI_BUS_AHB
 + bool Use AHB bus
 + depends on TARGET_atheros
 +
 +endchoice
 +
 +choice
 + prompt HAL selection
 + default MADWIFI_HAL_DEFAULT
 + help
 +   This option controls how MadWifi communicates with the hardware.
 +
 +config MADWIFI_HAL_DEFAULT
 + bool Use default HAL
 + help
 +   This makes MadWifi determine the needed HAL based on the target
 +   hardware. This will generally work most of the time, but there are 
 some
 +   cases where you need to override it.
 +
 +config MADWIFI_HAL_MIPS_BE_ELF
 + bool Use MIPS big endian ELF HAL
 + depends on mips
 + depends on BIG_ENDIAN
 +
 +config MADWIFI_HAL_MIPS_LE_ELF
 + bool Use MIPS little endian ELF HAL
 + depends on mips
 + depends on !BIG_ENDIAN
 +
 +config MADWIFI_HAL_I386_ELF
 + bool Use i386 ELF HAL
 + depends on TARGET_x86
 +
 +config MADWIFI_HAL_XSCALE_BE_ELF
 + bool Use XScale big endian ELF HAL
 + depends TARGET_ixp4xx
 + depends on BIG_ENDIAN
 +
 +config MADWIFI_HAL_XSCALE_LE_ELF
 + bool Use XScale little endian ELF HAL
 + depends TARGET_iop32x
 + depends on !BIG_ENDIAN
 +
 +config MADWIFI_HAL_ARMV4_LE_ELF
 + bool Use ARMV4 little endian ELF HAL
 + depends TARGET_storm
 + depends on !BIG_ENDIAN
 +
 +config MADWIFI_HAL_AP30
 + bool Use AP30 HAL
 + depends on TARGET_atheros
 +
 +config MADWIFI_HAL_AP43
 + bool Use AP43 HAL
 + depends on TARGET_atheros
 +
 +config MADWIFI_HAL_AP51
 + bool Use AP51 HAL
 + depends on TARGET_atheros
 +
 +config MADWIFI_HAL_AP61
 + bool Use AP61 HAL
 + depends on TARGET_atheros
 +
 +endchoice
 +
 +choice
 + prompt Rate control algorithm selection
 + default MADWIFI_RCA_MINSTREL
 + help
 +   This option controls how MadWifi chooses its bitrate.
 +
 +config MADWIFI_RCA_MINSTREL
 + bool Use the Minstrel rate control algorithm
 + help
 +   This code is takes a wandering minstrel approach. Wander around the
 +   different rates, singing wherever you can. And then, look at the
 +   performance, and make a choice. Note that the wandering minstrel will
 +   always wander in directions where he/she feels he/she will get paid
 +   the best for his/her work.
 +
 +config MADWIFI_RCA_ONOE
 + bool Use the Onoe rate control algorithm
 + help
 +   Onoe is a credit based RCA where the value of the credit is determined
 +   by the frequency of successful, erroneous and retransmissions
 +   accumulated during a fixed invocation period of 1000 ms. If less than
 +   10% of the packets need to be retransmitted at a particular rate, Onoe
 +   keeps increasing its credit point till the threshold value of 10 is
 +   reached. At this point, the current transmission rate is increased to
 +   the next available higher rate and the process repeated with credit
 +   score of zero. Similar logic holds for deducting the credit score and
 +   moving to a lower bit-rate for failed packet
 +   transmission/retransmission attempts. However, once a bit-rate has
 +   been marked as failure in the previous attempt, Onoe will not attempt
 +   to select that bit-rate until 10 seconds have elapsed since the last
 +   attempt. Due to the manner in which it operates, Onoe is conservative
 +   in rate selection and is less sensitive to individual packet failure.
 +
 +config MADWIFI_RCA_AMRR
 + bool Use the