- Nov 12, 2013
-
-
nbd authored
Signed-off-by:
Felix Fietkau <nbd@openwrt.org> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38783 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
nbd authored
hostapd: remove #ifdef MULTICALL around ap+sta support code (to support separately installed supplicant+hostapd) Signed-off-by:
-
wigyori authored
- enable building uboot for imx23 along sbImage by default - (doc updated) Signed-off-by:
Zoltan HERPAI <wigyori@uid0.hu> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38781 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
wigyori authored
- remove DCP patch as it's in mainline now (dts patch will stay) - refresh Duckbill patch - update kmod-usb-chipidea Signed-off-by:
-
jow authored
Fixes #14325 Signed-off-by:
Nikolay Martynov <mar.kolya@gmail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38779 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
jow authored
Signed-off-by:
-
wigyori authored
Signed-off-by:
Michael Heimpold <mhei@heimpold.de> Signed-off-by:
-
wigyori authored
Signed-off-by:
-
wigyori authored
Signed-off-by:
-
wigyori authored
Signed-off-by:
-
wigyori authored
Signed-off-by:
Harald Geyer <harald@ccbib.org> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38773 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
wigyori authored
Signed-off-by:
-
luka authored
Fixes failsafe issues with switches after r38725. Signed-off-by:
Luka Perkov <luka@openwrt.org> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38770 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
hauke authored
This was observed on the Belkin Share F7D7302. git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38769 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
hauke authored
Signed-off-by:
Cody P Schafer <devel@codyps.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38768 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
hauke authored
boardnum is unstable, so allow using NULL to make it unchecked. A method for differentiating F7D3301 from F7D3302 using nvram is unknown at this point. Reading the first 32bits of magic from the "linux" mtd partition would do the trick, but these 2 are similar enough that we don't need separate led/button definitions. Not knowing which one you have is only a usability issue for upgrading the device: they expect different magic numbers for their trx images. Signed-off-by:
-
- Nov 11, 2013
-
-
hauke authored
Signed-off-by:
Nathan Hintz <nlhintz@hotmail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38766 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
hauke authored
Signed-off-by:
-
hauke authored
Signed-off-by:
-
hauke authored
'nas' requires probe of 'wds' devices to be successful; so don't fail them. Signed-off-by:
-
hauke authored
When enabling multiple VIFS, the driver sometimes crashes. The frequency of the crash increases as more VIFS are enabled. Signed-off-by:
-
hauke authored
Signed-off-by:
-
wigyori authored
Signed-off-by:
-
hauke authored
Read the number of virtual interfaces to support from the device capabilities; as some newer devices can support up to 16. Signed-off-by:
-
hauke authored
Move all device cleanup to "disable_broadcom". Signed-off-by:
-
hauke authored
Some devices initialize with a default address (common to all H/W). The address needs to be changeable so that a unique address can be assigned to each AP. Signed-off-by:
-
hauke authored
Signed-off-by:
-
hauke authored
Specify variables as 'local' where appropriate Signed-off-by:
-
hauke authored
Default gmode to "GOnly" unless explicitly overwridden. This corrects processing for 11ng to specify "GOnly" for gmode instead of "Auto" (which translated to "bg"). Signed-off-by:
-
hauke authored
'nas' must be shutdown independently for each 'wl' device to properly support devices with multiple radios. Do the shutdown when the device is disabled instead of when it is brought up. Signed-off-by:
-
hauke authored
A single instance of 'nas' can support multiple interfaces; there's no need to run multiple instances. Signed-off-by:
-
hauke authored
Signed-off-by:
-
hauke authored
Update descriptions for 'phytype' and 'band'. Signed-off-by:
-
hauke authored
Modify the band reporting for broadcom devices to correctly report HW capability. Currently, 802.11na devices report "bgn"; but should be reporting "an". Signed-off-by:
-
hauke authored
'netifd' treats all devices with a "." in their name as vlan devices. Modify the name of virtual/WDS interfaces created by broadcom-wl to use a "-" instead of a ".", so they will be treated as simple devices by 'netifd'. Signed-off-by:
-
hauke authored
Delete the return value (nvram_exit is declared with a 'void' return). Signed-off-by:
-
hauke authored
The associations list for Broadcom WDS interfaces are duplicate to those reported by the corresponding AP interface; so there is no need to report them again. Signed-off-by:
-
hauke authored
Modify the hwmodelist reporting for broadcom devices to include proper reporting of 802.11n support. Signed-off-by:
-
hauke authored
It is a problem when phydev is not set at this position and not the other way around. Signed-off-by:
Hauke Mehrtens <hauke@hauke-m.de> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38744 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
jow authored
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38743 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
