[juhosg:
- use 'PowerCloud Systems' instead of 'PCS' in the profiles
- sort SingleProfile instances in image/Makefile]
Signed-off-by: Daniel Dickinson <daniel@powercloudsystems.com>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 34195
Commit r33248 introduced a regression by passing the board name plus
'board=' in the third argument. The board name string has to be put
into the image as identifier of the image type.
[juhosg: fix OpenMesh template instead of use of string substitution]
Signed-off-by: Marek Lindner <lindner_marek@yahoo.de>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 33767
With these images, it is possible to use the 'unused'
partition of the flash. The 'fat' images can be installed
with the sysupgrade command. When a 'fat' image is
installed from a regular one, the platform specific
sysupgrade script copies the calibration data to the
end of the flash. Likewise, when a regular image is
installed from the 'fat' version the sysupgrade script
copies the calibration data back to the original location.
SVN-Revision: 33540
It should be implemmented in a cleaner way.
This reverts the following commits:
[ar71xx] dir-825-b1: Fix wholeflash images
[ar71xx] dir825b1: Add image for DIR-825-B1 that uses the whole flash"
SVN-Revision: 33459
Commit 48788063266ad99bdab03b53cbe7e1a564c2d9b3 (r33251) introduced a
regression with board= kernel command line parameter incorrectly
initialised.
The faulty builds propogated to the snapshots download area. This makes
the device unbootable and TP-Link users have to attach the serial to
recover.
Here is the q&d way i used to identify MIPS boards that didn't have a
corresponding entry in the image/Makefile:
for i in `find ../files/arch/mips/ath79/ -type f -exec cat {} \; \
| sed -n '/MIPS_MACHINE/ { s/^[^"]*"\([^"]*\)".*$/\1/; p; }'`; do
grep -q ,$i, Makefile || echo $i;
done > missing-boards.new
Reported-by: Casper on IRC
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
SVN-Revision: 33274
For the pure convenience of having a correctly named
image and system name in /proc/cpuinfo , until we can
do that by having system names in DTS...
Signed-off-by: Daniel Golle <dgolle@allnet.de>
SVN-Revision: 33224
The TL-WDR3600 is identical to the TL-WDR4300 with the exception that is has
only two antennas.
[juhosg: remove the custom machine type, change the board name instead]
Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
SVN-Revision: 33219
The patch set for Buffalo WLAE-AG300N initial support.
There is another patch for wireless led support that
is posted separately.
Note on serial console:
This unit has buffalo standard 4 pin console, but the unit may not power
on if some console apparatus is connected. This is probably due to some
electronic interaction between the unit's electronic power switch circuit
and the serial console apparatus. If this happens, it is required to power
on the unit without the console, then quickly (re-)attach it.
[juhosg: fix coding style]
Signed-off-by: Yoichi Shinoda <shinoda@jaist.ac.jp>
SVN-Revision: 32931
Pass the mtd_layout via the kernel command line instead.
Also increase the kernel partition size to 1024k, so current kernel can fit in.
Signed-off-by: Daniel Golle <dgolle@allnet.de>
SVN-Revision: 32585
Support for TP-Link TL-MR3040. Power LED not working - always on red, after
start should be green.
Signed-off-by: Cezary Jackiewicz <cezary.jackiewicz@gmail.com>
SVN-Revision: 31845
This patch adds support for D-LINK DIR-615 E4 board. It's mostly based
on the existing support for DIR-600 A1, with some changes in the leds
configuration.
It's an updated version of the patch that reliably works on my hw for
about a year (it was built from trunk on Jan 2011). When I decided to
update the firmware and checked for the current support for that device,
I also found previously posted patches by Alexey Loukianov that
mentioned some stability issues. I'm not sure where could be the
difference, the patches are very similar except the wmac led pin number
- I was using 1, and those patches used 17.
[juhosg: add 3.2 support]
Signed-off-by: Vadim Girlin <vadimgirlin@gmail.com>
SVN-Revision: 29973
Adds support for TL-MR11U, a portable router with very similar
hardware to the TL-WR703N and TL-MR3020, but with an onboard
2000mAh battery.
Tested, working:
All interfaces (Ethernet, 802.11n, USB)
WPS & Reset switches (Power appears to be a hardware slider)
Ethernet, Wifi, 3G LEDs (Power & charging LEDs hardware controlled)
Sysupgrade
[juhosg: fix indentations to use TABs instead of spaces, fix 3.2 patch
breakage]
Signed-off-by: Simon Taylor <simon.taylor.uk@gmail.com>
SVN-Revision: 29972
[juhosg: remove ath9k from the the profile package list, build WPE72
image with the Default profile as well]
Signed-off-by: Johnathan Boyce <jon.boyce@globalreach.eu.com>
SVN-Revision: 29914
This patch adds support for the TP-Link device TL-MR3020 which is very
similiar to the TL-WR703N.
The TL-MR3020 uses 5 LEDs, 1 push button and a switch with 3 positions.
Only four LEDs can be controlled via GPIO. The power LED is connected to
the power supply.
The WPS push button has been mapped to KEY_WPS_BUTTON. The two GPIO signals
of the sliding switch have been mapped to BTN_0 and BTN_1.
I have also setup a wiki page with details here:
http://wiki.openwrt.org/toh/tp-link/tl-mr3020
USB is working and has been tested with USB mass storage and USB UMTS
stick.
Wifi also seems to work.
Ethernet is working too.
Signed-off-by: Christian Cier-Zniewski <c.cier@gmx.de>
SVN-Revision: 29651
The WNDRMAC is a WNDR3700v2 (64MB RAM, 16MB flash) in a white case. The
WNDRMACv2 is a WNDR3800 (128MB RAM, 16MB flash) in a WNDRMAC case.
The WNDRMAC case doesn't have "holes" or labels for the 2.4GHz LED or
switch ports 2-4. The stock firmware uses a single LED (in the 5GHz
position) to indicate the status of both radios, and a single LED (in the
switch port 1 position) to indicate the status of all LAN ports. The
"missing" LEDs are present on the board, and easily shine through the
case. Unlike the stock firmware, OpenWrt will use these "hidden" LEDs.
I've tested the WNDRMACv2 image. I don't have a v1 WNDRMAC, but assume
that this is sufficient to build a fully-functional image.
Signed-off-by: Mark Mentovai <mark@moxienet.com>
SVN-Revision: 29513
Factory images for WNDR3700v2 and WNDR3800 should contain these model IDs
for the device: field in their DNI tags, not WNDR3700.
This regressed in r29434, which redid WNDR3x00 model detection. The sixth
parameter to Image/Build/Netgear is only used as the -B argument to
mkdniimg, which is used to set the device: field. In r29434, this was
erroneously changed to be WNDR3700 for all models. The tools to flash
factory images (U-Boot's TFTP server and the factory software's upgrade
utility) may refuse to honor images with incorrect device: fields in their
DNI tags.
Signed-off-by: Mark Mentovai <mark@moxienet.com>
SVN-Revision: 29473
With the default OpenWrt configuration, this increases the size
of the rootfs_data partition by 384KB/128KB on the older/newer
TP-Link models.
SVN-Revision: 29447
[juhosg: the name of the final image has been changed to
'openwrt-ar71xx-generic-om2p-squashfs-factory.bin']
Signed-off-by: Marek Lindner <lindner_marek@yahoo.de>
SVN-Revision: 29397
This fixes the machine name in /proc/cpuinfo and luci status page machine name.
Signed-off-by: Petri Rosenström <petri.rosenstrom@gmail.com>
SVN-Revision: 29326
With version 1.76 the upgrade may fail with newer Buffalo firmwares with
a message like this:
"You can not update the firmware because the firmware version is earlier
than 1.82. Please use 1.82 or later version for firmware update."
SVN-Revision: 28815
This adds support for the Netgear WNDR3800, it is almost the same as
the WNDR3700v2. It just has more RAM so the hd_id had to be adjusted.
Signed-off-by: Petri Rosenström <petri.rosenstrom@gmail.com>
SVN-Revision: 28597
