aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/bcm53xx
diff options
context:
space:
mode:
authorNicolò Veronese <nicveronese@gmail.com>2017-06-16 12:12:25 +0000
committerMatthias Schiffer <mschiffer@universe-factory.net>2018-04-05 15:28:56 +0200
commitd265a8f2ca49a67a46493cf57de7c265855b317f (patch)
tree65b5d6c1c7960d468d877ea90b3724418bc2c141 /target/linux/bcm53xx
parent0d8a0a6a17ea203527a5c61241ea19d763aed567 (diff)
downloadupstream-d265a8f2ca49a67a46493cf57de7c265855b317f.tar.gz
upstream-d265a8f2ca49a67a46493cf57de7c265855b317f.tar.bz2
upstream-d265a8f2ca49a67a46493cf57de7c265855b317f.zip
ar71xx: Add support for D-Link DAP-1330 a1
D-Link DAP-1330 rev. A1 is a wall-plug N300 Wi-Fi range extender, based on Qualcomm/Atheros QCA9533 v2. Short specification: - 650/393/216 MHz (CPU/DDR/AHB) - 1x 10/100 Mbps Ethernet - 64 MB of RAM (DDR1) - 8 MB of FLASH - 2T2R 2.4 GHz - 2x external antennas - 6x LED (2 are bi-color), 2x button - 4 pin on pcb (looking from eth port and from left to right tx,rx,gnd,vcc) Flash instruction: use "factory" image directly in vendor GUI. This device has a recovery system that assign the ip addr of env variable "serverip" via dhcp to a pc, and the "ipaddr" value to itself. The recovery it's triggered by a not bootable firmware, or pressing the reset button during the bootloader startup (first 30 seconds). The recovery uses a http page to restore the firmware, and it's checking the firmware image header, so use the "factory" image to restore or the original firmware. You can access vendor firmware over serial using: - login: root - password: linuxrocks Image was tested only in EU version of the device, but should work also with the same device version sold in other countries. Signed-off-by: Nicolò Veronese <nicveronese@gmail.com>
Diffstat (limited to 'target/linux/bcm53xx')
0 files changed, 0 insertions, 0 deletions