That function provides a slightly improved sanity check than the
currently used solution.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38967
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: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38966
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: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38965
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: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38964
- partitions on factory fw are a bit strange
- unknown contained some strings in factory
- unknown2 contains some atheros (2nd art ?)
Signed-off-by: Dirk Neukirchen <dirkneukirchen@web.de>
Patchwork: http://patchwork.openwrt.org/patch/4149/
[juhosg: edit commit message]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38954
There was no way to determine a working config, because
the switch (ar8337) was not working previously.
Signed-off-by: Dirk Neukirchen <dirkneukirchen@web.de>
Patchwork: http://patchwork.openwrt.org/patch/4470/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38953
The device has three extra LEDs which indicate the quality
of the wireless link. Thanks to rssileds, this feature now
works out of the box.
Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
Patchwork: http://patchwork.openwrt.org/patch/4462/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38950
This patch improves support for the device considerably.
1. The wifi didn't work in the initial release. This was because
the WMAC of the AR9340 is not connected to the antennas.
(However, it can pick up wifi signals, if they are strong enough!)
Instead there's a dedicated AR9300 chip on the same board, which
works.
2. Ethernet throughput is improved. iperf shows that the hardware
can sustain more than 200Mbit/s and no longer drops any packages
when the link is under load.
Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
Patchwork: http://patchwork.openwrt.org/patch/4461/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38949
The F1E Phy (AR8035?) requires additional bits to be
set in order to provide a fast and reliable connection
over gigabit links.
When enabled, the link doesn't suffer anymore from a small
package loss under load and the performance is improved
quite a bit as well. (203 mbit/s vs 112 mbit/s, iperf tcp).
Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
Patchwork: http://patchwork.openwrt.org/patch/4460/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38948
Small update to uci_defaults/01_leds, to support the usb led
Signed-off-by: Martijn Zilverschoon <thefriedzombie@gmail.com>
Patchwork: http://patchwork.openwrt.org/patch/4426/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38947
Just a small oversight my part, added the support for the USB led
Signed-off-by: Martijn Zilverschoon <thefriedzombie@gmail.com>
Signed-off-by: Martijn Zilverschoon <thefriedzombie@gmail.com>
Patchwork: http://patchwork.openwrt.org/patch/4425/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38946
Patch to add the profile for the TP-LINK WR842N/ND v2
Small update, because of a change in the Makefile.
Signed-off-by: Martijn Zilverschoon <thefriedzombie@gmail.com>
Patchwork: http://patchwork.openwrt.org/patch/4382/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38815
Patch to add the user space support for the TL-WR842N/ND v2
Signed-off-by: Martijn Zilverschoon <thefriedzombie@gmail.com>
Patchwork: http://patchwork.openwrt.org/patch/4354/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38814
Get the factory assigned mac addresses stored in the caldata
partition and asign them to lan and wan interfaces. Also put
the correct mac addresses into the WiFi eeprom files to ensure
that the ath9k driver will use the correct ones.
Signed-off-by: Stefan Agner <stefan@agner.ch>
Patchwork: http://patchwork.openwrt.org/patch/4350/
[juhosg:
- move WiFi MAC address setup to the firmware hotplug file,
- use the official MAC address for the 2.4GHz as well,
- remove uci-defaults.sh modifications,
- update commit message]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38812
The current implementation of mtd will not append the backup
file created by sysupgrade to the correct partition, as mtd will append
the data to first jffs2 partition it finds. As the kernel is also
stored on a jffs2 partition (which resides before the overlay
partition), the data will be appended to this partition.
To fix this problem, a new option
-s <number> skip the first n bytes when appending data to the jffs2 partiton, defaults to "0"
is added to mtd.
Signed-off-by: Peter Wagner <tripolar@gmx.at>
SVN-Revision: 38807
Patch to add user space support for the TL-WA750RE/WA850RE range extender
Signed-off-by: Martijn Zilverschoon <thefriedzombie@gmail.com>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38718
Patch to add kernel support for the TP-LINK WA750RE and the WA850RE
range extender
Signed-off-by: Martijn Zilverschoon <thefriedzombie@gmail.com>
[juhosg: rename and refresh kernel patch]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38717
In particular, phy_connect before register_netdev. This is because
register_netdev runs the netdev notifiers, which can race with the rest of
the initialization in ag71xx_probe. In my case this manifested in two ways:
1) If ag71xx is compiled as a module and inserted after netifd has started,
netifd is notified by register_netdev before the call to
ag71xx_phy_connect. netifd tries to bring the interface up, which calls
ag71xx_open, which in turn enters ag71xx_phy_start. This keys off
ag->phy_dev (which is still NULL) and thinks this is a fixed-link board,
and enters ag71xx_link_adjust. This looks at ag->speed which is not yet
initialized and hits the BUG() in the switch (ag->speed) in
ag71xx_link_adjust.
This is the wrong code path for ag71xx_phy_start - my board has PHYs that
need to be brought up with phy_start. Doing ag71xx_phy_connect before
register_netdev ensures that ag->phy_dev is non-NULL before
ag71xx_phy_start is ever called.
2) When ag71xx is built into the kernel, and netconsole is enabled, there
is a gap in the initial burst of replayed printks right after the netdev
comes up. My assumption is that netconsole is also triggered by a netdev
notifier, and part of this printk burst happens before the call into
ag71xx_phy_connect, so part of the burst is lost while the PHY comes up.
This patch fixes the gap - all the printks before eth0 comes up are bursted
in full when netconsole initializes.
ag71xx_phy_connect_xxx no longer runs with a registered netdev, so the
logging has been adjusted accordingly to avoid "unregistered net_device" or
"eth%d" messages in dmesg.
Signed-off-by: Catalin Patulea <cat@vv.carleton.ca>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38689
Patchwork: http://patchwork.openwrt.org/patch/4281/
Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
[juhosg:
- remove the Image/Build/CyberTANLZMA/loader macro, it is not used
- move the MYNETREXT SingleProfile definition to the correct place]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38688
This patch adds a new device definition for a
Western Digital device. The hardware seems to
be based on Qualcomm Atheros DB120 design.
Patchwork: http://patchwork.openwrt.org/patch/4281/
Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
[juhosg: refresh kernel patch]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38686
Append EOF markers to the END of the UBI image
file. This forces the kernel to erase all blocks
after the marker even if those blocks are not
empty.
Additionally, the resulting image can be flashed
from the original web UI now, so use '-factory'
suffix for that.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38683
Extended the Makefile to generate a working factory reset image
for Netgear WNDR4300. The image uses UBI with two volumes squashfs
(rootfs) and JFFS2 (rootfs_data). In order to make stock U-Boot
happy, a fake rootfs image is placed into the last erase block
of the kernel partition.
Signed-off-by: Stefan Agner <stefan@agner.ch>
[juhosg:
- restore the NetgearNAND/initramfs macro,
- remove unused {Squash,Ubi}fsTemplate macros,
- remove board specific mtd options from CONFIG_CMDLINE, append the
board specific ubi.mtd parameter to the kernel command line instead,
- increase kernel partition size to 2MiB,
- use board specific ini file for ubinize,
- put jffs2 eof mark into the rootfs_data ubi volume,
- use KDIR_TMP for temporary images,
- use the squashfs-raw image,
- increase kernel partition size to 2MiB,
- use a local ubinize macro,
- fix macro parameter comments,
- put the fake rootfs into the last erase block of the kernel
partition,
- move Image/Build/NetgearNAND/buildkernel macro before
define Image/Build/NetgearNAND,
- don't use the wndr3700 utility, use '-M' parameter of mkimage to set
the uImage magic,
- use '-recovery' suffix for the generated image, it is only usable via
the fw_recovery function of the bootloader,
- update commit log]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38655
Add new subtarget nand with UBI/UBIFS including GLUEBI and squashfs.
This target will be used for NAND based router which make use of
UBI (and maybe UBIFS later on) in order to provide proper NAND
support.
Signed-off-by: Stefan Agner <stefan@agner.ch>
[juhosg:
- tweak target.mk:
change BOARDNAME variable,
improve Target/Description,
remove targz and ubifs from FEATURES and add broken flag,
- optimize kernel configuration:
disable ubifs, it is not used yet,
disable unused MTD options,
disable SPI support
disable unused network drivers,
tune kernel command line,
- remove image/ubinize.cfg, it will be in a follow-up patch
- move profile modifications into a separate patch]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38646
Ensures that the 'Default' images are generated
even if the subtarget has no profiles.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38635
Patchwork: http://patchwork.openwrt.org/patch/4183/
Signed-off-by: Terry Yang <yangbo@bhunetworks.com>
[juhosg:
- remove MultiProfile, it makes no sense for a single board
- move SingleProfile call and the mtdlayout to a different
location keep things sorted (well, almost)]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38593
BXU2000n-2 A1 is a BHU Networks WLAN board, use ar9341 chip.
Patchwork: http://patchwork.openwrt.org/patch/4183/
Signed-off-by: Terry Yang <yangbo@bhunetworks.com>
[juhosg:
- rename and refresh kernel patch,
- fix some checkpatch warnings and adjust whitespaces in
mach-bhu-bxu2000n2-a.c]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38591
This patch adds support for DRAGINO2 board (used by
Meshpotato v2). Most of the files included can be
found in the official svn repository provided by the
company [1]. I have just adapt it to the last OpenWrt
trunk revision (Fri Oct 4 10:49:47 2013).
1. http://svn.dragino.com/dragino2
Patchwork: http://patchwork.openwrt.org/patch/4234/
Signed-off-by: Pau Escrich <p4u@dabax.net>
[juhosg:
- rename and refresh kernel patch,
- fix checkpatch warnings in mach-dragino2.c]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38587
It is for Mikrotik devices only, rename the subtarget
to reflect that. Also fix the wget2nand script to use
the new image names.
Based on the patch by Stefan Agner:
http://patchwork.openwrt.org/patch/4123/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38509
The nand subtarget supports Mikrotik boards only. Change
the title and the description to reflect that.
Based on the patch by Stefan Agner:
http://patchwork.openwrt.org/patch/4123/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38508
Ensure that menuconfig shows the correct help text for
subtargets.
Based on the patch by Stefan Agner:
http://patchwork.openwrt.org/patch/4123/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38507
Both Allnet and OpenMesh sysupgrade uses fw_setenv from uboot-envtools to
change different settings in the uboot environment. uboot-envtools version
2013.01 introduced a filesystem lock "/var/lock/fw_printenv.lock" to guarantee
mutually exclusive access to the uboot environment. But the path /var doesn't
exist on the sysupgrade ramfs.
An upgrade on these devices fails since r36033 ("[package] uboot-envtools:
upgrade to version 2013.01.01") with following messages:
Error opening lock file /var/lock/fw_printenv.lock
failed to update U-Boot environment
Creating the "/var/lock" path before running fw_setenv is therefore a
requirement unless the locking functionality in fw_setenv is removed or
replaced with optional locking.
Signed-off-by: Sven Eckelmann <sven@open-mesh.com>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38483
Fixes the 5 GHz LED.
The same function has no effect on the 2.4 GHz LED at all, so we might
as well remove it.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38482
Fix the image building code so that the kernel correctly
distinguishes between hardware revisions.
Signed-off-by: Mads Hansen <d@taba.se>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38192
This patch adds support for the hardware slide switch on
the TL-MR3040 v2.
Signed-off-by: Mads Hansen <d@taba.se>
[juhosg: use EV_SW instead of EV_KEY]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38190
Remove the kernel and rootfs partitions. The Seama
parser can find those automatically:
0x000000070000-0x000000ff0000 : "firmware"
2 seama-fw partitions found on MTD device firmware
0x000000070000-0x0000001b0000 : "kernel"
0x0000001b0000-0x000000ff0000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
1 squashfs-split partitions found on MTD device rootfs
0x000000360000-0x000000ff0000 : "rootfs_data"
0x000000ff0000-0x000001000000 : "radiocfg"
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38155
- append the root squashfs directly after the kernel,
- use the 64kraw/128kraw template instead of the 64k/128k,
- ensure that the generated images have enough erase blocks
for JFFS2 garbage collection,
Tested on WZR-HP-G300NH and WZR-600DHP boards.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38153
The Image/Build/WZRHP64K and the Image/Build/WZRHP128K macros
are similar. Move the common stuff into the Image/Build/WZRHP
macro and update the orignal macros to use that.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38152
- append the root squashfs directly after the kernel,
- use the 64kraw template instead of the 64k,
- ensure that the generated images have enough erase blocks
for JFFS2 garbage collection,
Tested on a TEW-673GRU board.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38151
The Image/Build/DIR825B1 and the Image/Build/DLRTDEV macros
are identical. Merge those into a new Image/Build/CameoAP94
macro, and update the device profiles to use the new macro.
Also rename the dir825b1_* mtdlayout macros to cameo_ap94_*.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38150
- append the root squashfs directly after the kernel,
- use the 64kraw template instead of the 64k,
- ensure that the generated images have enough erase blocks
for JFFS2 garbage collection,
Tested on a WispStation M5 board.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38148
The firmware generation part is the same for both
macros. Move that into a separate macro and use the
new macro for Image/Build/UB{NTXM,DEV}.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38146
- append the root squashfs directly after the kernel,
- use the 64kraw template instead of the 64k
- ensure that the generated images have enough erase blocks
for JFFS2 garbage collection,
Tested on the WHR-G301N board only.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38141
- remove the 'kernel' and 'rootfs' partitions from the mtd layout,
- move the .okli image into the uImage,
- append the root squashfs directly after the kernel,
- use the 64kraw template instead of the 64k
- ensure that the generated images have enough erase blocks
for JFFS2 garbage collection,
Tested on the MZK-W300NH board only.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38139
- append the root squashfs directly to the kernel,
- use the 64kraw-nojffs template instead of sqashfs-only
- ensure that the generated images have enough erase blocks
for JFFS2 garbage collection,
Tested on a TEW-712BR devices only.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38130
- append the root squashfs directly to the kernel,
- use the 64kraw/64kraw-nojffs template instead of 64k/squashfs-only,
- ensure, that the signature is placed at the correct offset in
the *-factory images,
- ensure that the generated images have enough erase blocks
for JFFS2 garbage collection,
Tested on DIR-600-A1 and TEW-632BR devices only.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38129
The MTD layout of the AP99 based devices is different.
Add new macros to reflect that and use the new macros
for the DIR-615-E4 board.
This prevents overwriting of the 'mac' partition which
contain vital informations. The disadvantage of the change
is that the usable space is reduced by 192KiB. Blame the
vendors for the unfriendly partition layout.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38128
Also remove the similar code from the Netgear
profile and use the new feature instead.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38126
- remove the kernel and rootfs partitions from the mtd layout,
the kernel creates those automatically,
- remove estimation step, it is not needed anymore
- put the root squashfs directly after the kernel
- use the 64kraw template
With the default configuration, this allows to use more space for
rootfs_data with 64KiB. Tested on WNDR3700 v1 only.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38120
The new macro will be used to determine the firmware
partition size from an MTD layout.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38117
Enable the wlan2g led in the default configuration of dir-825-c1.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Patchwork: http://patchwork.openwrt.org/patch/4079/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38106
This patch
- changes the color names from orange to amber
- changes the name of GPIO 13 from WIFI_BGN (wifi_bgn) to WLAN_2G
(wlan2g) to be more consistent with the other routers' files
- changes the descriptions of the hardware keys to be a tad more
explicit
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Patchwork: http://patchwork.openwrt.org/patch/4081/
[juhosg: update the LED migration script as well]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38105
Enable GPIO 20. This hands off control of the blue planet led to the
integrated switch. Consequently, remove the led configuration for the
blue planet led.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Patchwork: http://patchwork.openwrt.org/patch/4080/
[juhosg: whitespace fixup]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38096
This allows to build images for other boards, even if
the image is too big for Cameo devices.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38095
This patches fixes the lan led configuration. The new configuration is
identical to the one in mach-db120.c and it works. The previous one
didn't work at all.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38094
The goal is to set the WAN MAC address to the one on the
sticker on the bottom of the unit. Currently it is not
used at all. But some users expect the WAN interface to
have the MAC address that is written on the sticker.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38091
Rename the function and extend it in order to make it
usable from board setup code.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38085
Change some flow-level unctions to return with an
error code in order to be able to report errors
to the core code.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38068
This patch adds support for TP-Link TL-MR13U router with built-in 10AH
rechargeable battery.
The patch is based on kamwanlai's patch:
https://forum.openwrt.org/viewtopic.php?pid=206746#p206746
Updated to accommodate recent changes introduced with:
ar71xx: remove fs_* variables from image/Makefile
Signed-off-by: Oleg Titov <oleg.titov@gmail.com>
Patchwork: http://patchwork.openwrt.org/patch/4063/
[juhosg:
- refresh and rename rename 930-add-tl-mr13u-support.patch =>
625-MIPS-ath79-add-tl-mr13u-support.patch]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38063
This patch adds OpenWRT support for the Netgear WNR2200 (N300)
wireless router with USB.
Technical details of this router can be found at
http://www.netgear.com/home/products/wirelessrouters/work-and-play/WNR2200.aspx
and http://wikidevi.com/wiki/Netgear_WNR2200
Signed-off-by: Aidan Kissane <aidankissane@googlemail.com>
Signed-off-by: Dirk Neukirchen <dirkneukirchen@web.de>
Patchwork: http://patchwork.openwrt.org/patch/4055/
[juhosg:
- add commit message and SoB line from the original patch
- remove dead code from mach-wnr2200.c
- refresh 624-MIPS-ath79-WNR2200-support.patch]
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38059
Add a new kernel config option for generic firmware partition
split support and change the uImage split support to depend on
the new option. Aslo rename the MTD_UIMAGE_SPLIT_NAME option to
MTD_SPLIT_FIRMWARE_NAME to make it more generic.
The patch is in preparation for multiple firmware format
support.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 38002
This patch adds support for building firmware images for the
TP-Link TL-MR3040 v2. Tested and working on v2.1 hardware.
Signed-off-by: Mads Hansen <d@taba.se>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 37964
I checked the GPL code drop from D-Link and tried to get the wireless
and LAN switch LEDs to light up. I found some references in
AthSDK/www/DIR-825_C1/bsp.h as well as
AthSDK/www/DIR-825_C1/rootfs/etc/sysconfig/S2gpio.sh, but in the end I
only got the led for 2.4GHz to work. Anyway, here's the patch.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 37963
When the squashfs and jffs2 images are generated
in the same turn, the compressed kernel images
are generated twice with the same parameters.
Move compressed kernel generation into a separate
phase to avoid that.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 37881
Those are not needed since we are generating the
initramfs images along with the others.
Remove the variables and use the template names
directly.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 37876
Initramfs images are not generated for profiles which
are using the squashfs-only template. Add the missing
'Image/Build/Template/squashfs-only/initramfs' to fix
that.
Also, 'Image/Build/Cameo933x/initramfs' uses wrong
parameters for 'MkuImageLzma/initramfs' due to a
misplaced commma. Remove that to fix the generated
initramfs images.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 37871
Apparently registering usb device on newest trunk causes
this AP not to boot...
Since there is no USB socket in that device anyway this
can be simply removed (and device boots then no problem).
[juhosg:
- tweak subject line and description,
- remove #include "dev-usb.h",
- remove 'select ATH79_DEV_USB' from Kconfig]
Signed-off-by: Jacek Kikiewicz <jaceq@aol.pl>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 37844
Based on the original firmware, the file must have the tag
HORNET-PACKET-DIR505A1-3, not HORNET-RT-DIR505A1-3.
http://patchwork.openwrt.org/patch/3945/
Signed-off-by: Cezary Jackiewicz <cezary.jackiewicz@gmail.com>
SVN-Revision: 37781
This patch fixes the code of the buttons for TP-Link WA901ND.
Signed-off-by: Rocco Folino <lordzen@autistici.org>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 37696
Small router sold in EU: AR9330@400MHz, 1x USB2.0,
2x ethernet, 8MB flash, 32MB ram, one led, one button.
See: http://galeria.tech-blog.pl/TP-Link_TL-WR710N-EU/
[juhosg: use a separate kernel patch]
Signed-off-by: Cezary Jackiewicz <cezary.jackiewicz@gmail.com>
Patchwork: http://patchwork.openwrt.org/patch/3873/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 37572
Mercury MW4530R is a TP-Link TL-WDR4310 clone but
with a much lower price tag (~ $40). This patch
is tested to work at trunk r37525.
Signed-off-by: Leon Xu <ylxu72@gmail.com>
Patchwork: http://patchwork.openwrt.org/patch/3856/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 37571
Mercury MW4530R is a TP-Link TL-WDR4310 clone but
with a much lower price tag (~ $40). This patch
is tested to work at trunk r37525.
Signed-off-by: Leon Xu <ylxu72@gmail.com>
Patchwork: http://patchwork.openwrt.org/patch/3856/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 37570
Looks like trunk@37090 has changed the logic that determines
if router's button was pressed. This resulted in TEW632BRP
always booting into failsafe mode because it detected pressed
button (which was not pressed).
Measure with voltmeter has shown that buttons on this router
are actually active-low. This patch reflects this fact in
board configuration and fixes 'load info failsafe mode' issue.
Note: it looks like Trendnet TEW632BRP and a close relative
to TEW-652BRP V1.0 and D-Link DIR-615C1, so same problem may
exist on those routers as well. This patch doesn't affect
routers other than 632BRP and unfortunately I do not have
hardware to test this issue with other routers.
This patch fixes#13893 and is tested on actuall Trendnet
TEW632BRP.
Signed-off-by: Nikolay Martynov <mar.kolya@gmail.com>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 37569
Create a separate board profile and update the profile
name in image/makefile. Also use the correct machtype
string in kernel command line.
Based on andelf's patch:
http://andelf.diandian.com/post/2013-05-22/40050677370
Signed-off-by: Oleg Titov <oleg.titov@gmail.com>
Patchwork: http://patchwork.openwrt.org/patch/3840/
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 37550
This reverts r37477. A generic patch is used to fix
this globally, so revert the ar71xx specific change.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 37480
Drop the local get_mtd_part_size implementation and use
the equivalent function provided by lib/functions.sh.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 37476
