- Dec 08, 2013
-
-
nbd authored
Signed-off-by:
Felix Fietkau <nbd@openwrt.org> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@39003 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
nbd authored
Signed-off-by:
-
nbd authored
Signed-off-by:
-
nbd authored
Signed-off-by:
-
- Dec 06, 2013
-
-
jow authored
Linaro GCC 4.6-2013.05 incorrectly pads the arpt_arp structure on at least the ar71xx target, resulting in a two bytes shorter struct in the kernel compared to what arptables userspace expects. When comparing sizeof(struct arpt_arp) in kernel and userspace, the former yields 162 byte, while the latter is 164 byte. As a consequence, the subsequent target_offset and next_offset members of the parent arpt_entry structure contain invalid values when processed by the arptables binary, leading to bad memory accesses in the populate_cache() procedure, subsequently causing a segfault. Signed-off-by:
Jo-Philipp Wich <jow@openwrt.org> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38999 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
jow authored
generic: fix occasional "execvp: /bin/sh: Argument list too long" is kernel header install phase (#12907) Signed-off-by:
-
kaloz authored
Signed-off-by:
Imre Kaloz <kaloz@openwrt.org> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38997 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
- Dec 05, 2013
-
-
cyrus authored
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38996 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
- Dec 04, 2013
-
-
nbd authored
Signed-off-by:
-
cyrus authored
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38994 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
- Dec 03, 2013
-
-
nbd authored
Signed-off-by:
-
nbd authored
netifd: update to the latest version, improves wireless status output and fixes some bridge handling issues Signed-off-by:
-
nbd authored
Signed-off-by:
-
- Dec 02, 2013
-
-
nbd authored
Signed-off-by:
-
nbd authored
Add a new "reload" command that reloads the netifd config as well Signed-off-by:
-
nbd authored
Signed-off-by:
-
nbd authored
Signed-off-by:
-
nbd authored
prepare for using /var/run/hostapd instead of /var/run/hostapd-phy* Signed-off-by:
-
nbd authored
wpa_supplicant: clean up hostapd control socket on exit to fix socket leak in ap+sta mode on wifi restarts Signed-off-by:
-
nbd authored
Signed-off-by:
-
nbd authored
Signed-off-by:
-
nbd authored
Signed-off-by:
-
nbd authored
Signed-off-by:
-
- Dec 01, 2013
-
-
hauke authored
Signed-off-by:
Hauke Mehrtens <hauke@hauke-m.de> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38980 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
hauke authored
The wait instruction is only broken on the BCM4706 and not on the other similar SoCs. Signed-off-by:
-
hauke authored
This sets both values to the OpenWrt default values. There is no reason to use some brcm47xx specific values here. Signed-off-by:
-
hauke authored
This is only needed by BCM4716 and not by BCM4706, I haven't seen any problems there. Adds the write flush for some more parts where the phy control regs are written. Signed-off-by:
-
hauke authored
DMI_EXACT_MATCH was added to the kernel in version 3.10.21 and collides with backports version. DMI_EXACT_MATCH is only used by the intel GPU driver which is not build by OpenWrt, so remove it. Signed-off-by:
-
hauke authored
This adds support for vectored interrupts in this SoC. This is supported by the 74K cpus. Signed-off-by:
-
hauke authored
bcm47xx misses cpu overwrites for the features of the CPUs used in these SoCs. Instead of manually checking, it is now known at compile time for some options and the compiler is able to remove the checks and optimize the code. Signed-off-by:
-
hauke authored
Some time ago, after switching to the mainline bcm47xxpart driver following patch has been applied: commit 03cef872 Author: hauke <hauke@3c298f89-4303-0410-b956-a3cf2f4a3e73> Date: Sat Apr 6 22:22:26 2013 +0000 brcm47xx: use old partition names again for kernel 3.8 This fixes sysupgrade. The partition names are used all over the Internet in various howtos. Thank you russell for spotting this problem. I propose to revert this change and make sysupgrade use "firmware" instead. This makes brcm47xx compatible with widely used ar71xx and after all "firmware" sounds like a much better name for... the firmware. This change doesn't affect "sysupgrade" usage, because it never takes a partition name as a parameter. This change only affects users using mtd tool directly. Hopefully there are not many howtos using "mtd" command. Signed-off-by:
Rafał Miłecki <zajec5@gmail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38973 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
juhosg authored
Signed-off-by:
Gabor Juhos <juhosg@openwrt.org> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38972 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
- Nov 30, 2013
-
-
luka authored
Signed-off-by:
Luka Perkov <luka@openwrt.org> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38971 3c298f89-4303-0410-b956-a3cf2f4a3e73
-
juhosg authored
Signed-off-by:
-
juhosg authored
Signed-off-by:
Martijn Zilverschoon <thefriedzombie@gmail.com> Signed-off-by:
-
juhosg authored
Signed-off-by:
-
juhosg authored
That function provides a slightly improved sanity check than the currently used solution. Signed-off-by:
-
juhosg authored
This patch enables the convenient sysupgrade feature for WD's Wi-Fi Range Extender. Signed-off-by:
Christian Lamparter <chunkeey@googlemail.com> Patchwork: http://patchwork.openwrt.org/patch/4341/ [juhosg: - rename 'mynet_rext_check_image' function to 'cybertan_check_image' and move that into platform.sh, - remove the the model specific 'platform_do_upgrade_mynet_rext' function, - drop the mynet-rext.sh script, - remove the image/Makefile change, - update commit message] [christian: - check all 8 bytes of the firmware/device magic] Signed-off-by:
-
juhosg authored
Make the Image/Build/CyberTAN macro more generic, and use simple wrappers for the GZIP/LZMA variants. This simplifies the Makefile a bit, and allows to build sysupgrade images for the devices which are using LZMA compressed uImages. Signed-off-by:
-
juhosg authored
In the current sysupgrade images, the CRC32 value of the TRX header covers the whole rootfs data. Due to this, the CRC value should be changed during sysupgrade otherwise the bootloader refuses to load the image on the next boot. Change the image generation to create sysupgrade images where the CRC32 value covers the kernel data only. This allows to skip the 'fixtrx' step during sysupgrade on the target. Signed-off-by:
-
