Use doubletagging to disable ramips_esw vlan by default, it seems
more reliable.
Daniel Golle found an issue where sometimes (possibly only for
RT3352) the default vlan disable method (clearing en_vlan, untag,
doubletag and putting all ports into vlan 0) doesn't work and the
packets get sent out vlan-tagged with vlan 0.
Instead switch to using the doubletagging method (allow doubletagged
packets, put all ports into vlan 0 with untag enabled) by default.
Unless someone figures out a way to really globally disable vlan for
this switch, this seems like the best (most reliable) option.
I did some tests regarding maximum packet size and did not see any
difference between the two methods, both allow for slightly bigger packets
than the ramips_main.c ethernet driver (ping stops going through
above "ping -s 1472" (1514 bytes), on the switch packets are recv_good until
"ping -s 1490", or about 1532 bytes).
Signed-off-by: Tobias Diedrich <ranma+openwrt@tdiedrich.de>
SVN-Revision: 33321
Power down phy on disabled switch ports.
Haven't measured this myself yet, but according to this
http://www.8devices.com/community/viewtopic.php?f=6&t=156
it can save about 300mW of power.
[juhosg: fix checkpatch warning]
Signed-off-by: Tobias Diedrich <ranma+openwrt@tdiedrich.de>
SVN-Revision: 33304
Add support for 8devices Carambola dev board.
The Carambola is a small RT3050-based development board with two
ethernet ports, on-board chip antenna, usb and plenty of accessible
gpio ports, sold by 8devices.
Signed-off-by: Tobias Diedrich <ranma+openwrt@tdiedrich.de>
SVN-Revision: 33303
Rename POC registers.
The current code uses POC1-POC3.
The datasheet uses:
POC1: Port Control 0
POC1: Port Control 1
POC2: Port Control 2
So the first POC1 is a typo that should have been POC0, rename the
registers to POC0-POC2 accordingly.
Signed-off-by: Tobias Diedrich <ranma+openwrt@tdiedrich.de>
SVN-Revision: 33302
Stop handling VLAN setup in the kernel.
Removes the obsolete RT305X_ESW_VLAN_CONFIG_BYPASS option I added for
WL-351 and add some extra comments.
Also removes the en_vlan per-port flag that isn't very useful really, it now
is only controlled by the global enable_vlan flag.
Signed-off-by: Tobias Diedrich <ranma+openwrt@tdiedrich.de>
SVN-Revision: 33301
Add switch setup to uci network defaults.
The 'lan' attribute is used to decide into which vlan to put the
port.
Currently 'disable' is never set, but the intention is to use this
for devices like the 8devices Carambola, which only has two ports
hooked up to the SoC.
Signed-off-by: Tobias Diedrich <ranma+openwrt@tdiedrich.de>
SVN-Revision: 33300
Add swconfig support to ramips_esw.c
This patch adds swconfig support for ramips_esw:
Tested on both D-LINK DIR-300 B1 and Sitecom WL-351 (external
rtl8366rb on internal port 5).
I've made sure that in the enable_vlan=0 case it behaves like a dumb
switch, so external switches should work fine with vlans and
verified this on the WL-351.
The current state shown by swconfig is always read directly from HW
registers, new settings only show after 'swconfig dev rt305x set apply'.
Signed-off-by: Tobias Diedrich <ranma+openwrt@tdiedrich.de>
SVN-Revision: 33299
Minor indentation cleanup.
Prepare for the main swconfig patch by cleaning up indentation a bit.
Signed-off-by: Tobias Diedrich <ranma+openwrt@tdiedrich.de>
SVN-Revision: 33298
An improved LED support for Buffalo WZR-HP-AG300H.
There will be two new packages to go with this patch
(ar922x-led-fix-hotplug and ar922x-led-fix-init).
These packages essentially perform the same task of
disabling "JTAG over GPIO pins" function which is
currently required for LEDs on AR922x emac GPIO to work,
and are both considered a temporary fix that circumvent
this problem.
[juhosg: add the hotplug script from the proposed
ar922x-led-fix-hotplug package to ar71xx/base-files]
Signed-off-by: Yoichi Shinoda <shinoda@jaist.ac.jp>
SVN-Revision: 33294
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
OpenWRT runs in a eSATA sheevaplug like a charm. This patch just enables
CONFIG_MACH_ESATA_SHEEVAPLUG so the proper MACHINE_START definition
is compiled in.
Signed-off-by: Unai Uribarri <unaiur@gmail.com>
SVN-Revision: 33266
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
Generate image for the ALL0239-3G which can be flashed through the
chipset-vendor SDK based firmware's web-interface and bootloader.
The bootloader seems to ignore uImage checksum errors, but does complain about
them once the 0xDEADC0DE was replaced by an actual JFFS2 page.
I'm working on implementing fixtrx for uImage in the mtd package to solve this.
Signed-off-by: Daniel Golle <dgolle@allnet.de>
SVN-Revision: 33206
rt2x00 still needs some patching as the radio doesn't come to life.
Installation via webflash.
[juhosg: fix whitespace issues, remove rt305x_register_usb
from machine setup because the board has no USB port]
Signed-off-by: Mikko Hissa <mikko.hissa@uta.fi>
SVN-Revision: 33205
* Creation of uImage for WNR854T only done once (before 2x for jffs2 build and 1x for squashfs build)
* Got rid of unneccessary padding of rootfs partition
* ARM zImages always need a machine id, therefore do not copy generic (=no id) uImage to BIN_DIR, instead copy zImage
* Generalized functions for easier re-using and enhancing (e.g. D-Link DNS 323 implementation would be only a couple lines)
* Copy rootfs partitions to BIN_DIR, just like it is done for D-Link DNS 323
* Use variables to allows easily changing for custom builds, e.g. kernel mtd size for symbols
* Size check of kernel files to avoid builds that break devices
* Use for "-sysupgrade" and "-factory" in image names (like ar71xx, brcm63xx, etc.) to avoid questions about which image to use
Signed-off by: Matthias Buecher <mail@maddes.net>
SVN-Revision: 33174
In order to get OHCI/EHCI working on the Rt3352, the platform device must be
named so rt3883-?hci will recognize it.
Signed-off-by: Daniel Golle <dgolle@allnet.de>
SVN-Revision: 33145
As the userspace has no means to determine the maximum possible timeout, use
that as the default and let the userspace lower it when necessary.
As the result the usual OpenWrt install (with busybox's watchdog trying to set
the timeout to 60s on start) is using a 33s timeout on an RT3052 clocked at
384MHz instead of the current 20s default.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
SVN-Revision: 33144
D-Link's DIR-620 allows to flash a uImage directly from its web-interface but
for that the image name should be set to DIR_620.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
SVN-Revision: 33143
Full functionality runtime tested, installation via OEM web-interface requires
a follow-up patch.
Thanks go to Sergey Vasilyugin for his patch that pointed me at the missing
bits (including the antiparallel wps led).
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
SVN-Revision: 33142
Fixes this section mismatch warning:
WARNING: vmlinux.o(.meminit.text+0xb14): Section mismatch in reference
from the function memblock_insert_region() to the function
.init.text:crashlog_init_memblock()
The function __meminit memblock_insert_region() references
a function __init crashlog_init_memblock().
If crashlog_init_memblock is only used by memblock_insert_region then
annotate crashlog_init_memblock with a matching annotation.
Also, remove the __init annotations from 'include/linux/crashlog.h'
SVN-Revision: 33137