According to the calling convention of the o32 ABI the
caller function must reserve stack space for $a0-$a3
registers in case the callee needs to save its arguments.
The assembly startup code does not reserve stack space
for these registers thus when the main C function needs
to save its arguments, that will cause a stack overflow.
Fix the assembly code to reserve stack space for the
registers to avoid that.
Untested. It seems that the lzma-loader is not used at all?
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 49062
According to the calling convention of the o32 ABI the
caller function must reserve stack space for $a0-$a3
registers in case the callee needs to save its arguments.
The assembly startup code does not reserve stack space
for these registers thus when the main C function needs
to save its arguments, that will cause a stack overflow.
Fix the assembly code to reserve stack space for the
registers to avoid that.
Compile tested only.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 49061
The current code only partially invalidates both caches
because the cache size and cache-line size values are
incorrectly passed to the C code.
Fix the assembly code to pass the arguments in the correct
order.
Compile tested only.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 49060
The current code only partially invalidates both caches
because the cache size and cache-line size values are
incorrectly passed to the C code.
Fix the assembly code to pass the arguments in the correct
order.
Compile tested only.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 49058
The current code only partially invalidates both caches
because the cache size and cache-line size values are
incorrectly passed to the C code.
Fix the assembly code to pass the arguments in the correct
order.
Tested on RB532.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 49056
According to the calling convention of the o32 ABI the caller
function must reserve stack space for $a0-$a3 registers in case
the callee needs to save its arguments.
The assembly code of the loader does not reserve stack space for
these registers thus when the 'loader_main' function needs to save
its arguments, those will be stored in the 'workspace' area instead
of the stack.
Because the workspace area is also used by other part of the code, the
saved register values gets overwritten and this often leads to failed
kernel boots.
Fix the code to reserve stack space for the registers to avoid this
error.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 48279
On newer Mikrotik boards, the radio calibration data
is stored differently and uses LZO compression instead
of RLE.
Update the RouterBOOT helper code to support the new
format.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 45297
Platform device support has been removed from the gpio-74x164
driver in 3.14. Restore that.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 45203
Use the latest version of the yaffs code. Fetched from the
yaffs2 git tree and it is based on the following commit:
commit 7e5cf0fa1b694f835cdc184a8395b229fa29f9ae
Author: Charles Manning <cdhmanning@gmail.com>
Date: Thu Aug 7 11:25:05 2014 +1200
yaffs-direct: Basic tests. Add lpthread flag for background gc support
Signed-off-by: Charles Manning <cdhmanning@gmail.com>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 45188
The setting has been lost during the transition to 3.18.
The CONFIG_M25PXX_PREFER_SMALL_SECTOR_ERASE option is not
available anymore, so use CONFIG_MTD_SPI_NOR_USE_4K_SECTORS
instead.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 45161
The GL-Connect GL.iNet v1 router is basically a TP-Link TL-WR703N with
more DRAM/Flash, 2x Ethernet ports and console/GPIO header in the same
small form-factor:
<http://www.gl-inet.com/w/?lang=en>
Moreover, the manufacturer is promoting the OpenWrt usage to replace
the original firmware and proposing patches against both AA and trunk:
<http://www.gl-inet.com/w/?p=398&lang=en>
This is a clean up of the original manufacturer GPLv2 patch by alzhao,
proposed to the list by Mark Janssen.
Signed-off-by: Michel Stempin <michel.stempin@wanadoo.fr>
Signed-off-by: Mark Janssen <mark@sig-io.nl>
Signed-off-by: alzhao <alzhao@gmail.com>
Patchwork: http://patchwork.openwrt.org/patch/5273/
[juhosg:
- remove user-space and image generation support, will be included
from other patches,
- fix coding style and drop superfluous comment in mach-gl-inet.c,
- rename and refresh kernel patch,
- adjust subject]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 41618
The RB2011UiAS is almost exactly the same as the RB2011UAS, which is
already supported. Hardware-wise, it adds a passive power injector on
Eth10. Software-wise, Routerboot passes a different board name on the
kernel command line. Hence the need for a patch.
Not yet working:
* touchscreen: doesn't work on RB2011UAS either. The touchscreen itself
seems to be driven by an ADS7843-compatible IC, but figuring out which
GPIO pins it's connected to is work for the future.
* control of power injector: remains off. Probably also GPIO-controlled.
Signed-off-by: Soren Harward <stharward@gmail.com>
Patchwork: http://patchwork.openwrt.org/patch/5841/
[juhosg: rename and refresh the kernel patch]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 41617
The RB91x boards are suffering from ethernet packet loss after a cold
boot. The cause of the problem is that the AR8035 PHYs requires special
register settings to work reliably on these boards.
Enable the RGMII TX, RX delays and disable SmartEE functionality of
the AR8035 PHYs. Also enable the RXD delay in the ETH_CFG register
to fix the issue.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 40509
Add a patch for the at803x phy driver, in order to be able
to configure some register settings via platform data.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 40507
With this patch OpenWRT supports the following on the ZyXEL NBG 6716:
-WiFi 2G (ath9k)
-WiFi 5G (ath10k)
-NAND flash
-2 Ethernet interfaces
-USB 2.0
-LEDs including switch
-reasonale defaults at first boot
Signed-off-by: André Valentin <avalentin@marcant.net>
Patchwork: http://patchwork.openwrt.org/patch/5101/
[juhosg:
- rename and refresh kernel patch,
- fix a few typos,
- change button key codes,
- use zyxel prefix in LED names]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 40499
Apart from the wireless chip, the WNDR3700 v4 and the WNDR4300
is the same device. Indicate this in the kernel files.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 40479
The 5V power of the USB is controlled by a GPIO pin of
the external WiFi chip. Setup the GPIO bitmasks in the
platform data of the WiFi chip to ensure that the 5V
power gets enabled by the ath9k driver.
Based on the the WNDR3700v4 support patch from Ralph Perlich:
http://patchwork.openwrt.org/patch/4763/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 40478
The bootloader does not initializes the output function
correctly for all LEDs. DO that from the board setup code.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 40474
The hardware manual says amber so change the color part of
the LED names to reflect that. Also update the constant names.
Based on the the WNDR3700v4 support patch from Ralph Perlich:
http://patchwork.openwrt.org/patch/4763/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 40473
According to Christophe, the kernel boots on the Soekris net5501
board.
Reported-by: Christophe Prevotaux <cprevotaux@nltinc.com>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 40468
Move the comments out from the shell script to fix build
breakage introduced in r40464.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 40466
The C7v2 has 16 MB flash and QCA9880-BR4A rev 2 supported by ath10k driver.
The C7v1 had 8 MB flash and the unsupported QCA9880-AR1A rev 1.
Signed-off-by: Adam Serbinski <adam@serbinski.com>
Patchwork: http://patchwork.openwrt.org/patch/5071/
[juhosg:
- remove the v2 specific profile add the ath10k driver to the existing
Archer C7 profile instead. Although on v1 devices it does not change
the non-working behaviour, but the ath10k driver is useful for users
whom have replaced the wifi card with a supported one in their units.
- update image/Makefile to build firmware image for both boards if the
Archer C7 profile is selected]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 40463
Patch-by: Lars Bøgild Thomsen <lth@cow.dk>
Patchwork: http://patchwork.openwrt.org/patch/4922/
[juhosg:
- use a separate patch for kernel changes,
- reorder Kconfig and Makefile entries,
- change function and variable names to be lowercase only
and fix misaligned tabs in mach-gs-oolite.c,
... ]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 40032
The flash address passed to rb_init_info() is bogus,
use the predefined AR71XX_SPI_BASE macro instead.
Compile tested only.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39891
The ar71xx platform always uses the eth0 interface to provide
access to the device in failsafe mode. Due to this, failsafe
access is broken on devices where the LAN ports are connected
to the 'eth1' interface.
Update the relevant script to correctly set the ifname variable
for these devices.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 39752
Gabor Juhos