Reading from the flash chip on the TL-WR2543ND seems buggy.
If the SPI flash driver tries to read too much data in one
SPI transfer, the flash chip returns bogus values. This can
be caused by a buggy flash chip on my board, or it can
be a bug in our SPI driver.
Add a workaround to the m25p80 driver until I find out the
root cause of the problem. The patch allows to specify the
maximum numner of bytes which can be read safely withint
one SPI transfer.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29679 3c298f89-4303-0410-b956-a3cf2f4a3e73
* make clock delay configurable
* make read,write commands configurable
* use u16 for member and untag fields
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29677 3c298f89-4303-0410-b956-a3cf2f4a3e73
The wndr3700 at least has no eth0 mac address and usually leverages
the first wireless device's mac when in a bridged scenario. If,
however, you want to route, and not bridge the interfaces, you
need a unique mac address for it.
This patch sets the local bit on the mac address pulled from the
wireless chip and uses the resulting address for eth0.
Patch-by: Dave Taht <dave.taht@gmail.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29675 3c298f89-4303-0410-b956-a3cf2f4a3e73
It is based on patches from the linux-longsoon-community git tree:
http://dev.lemote.com/cgit/linux-loongson-community.git/
Now the kernel can use the command line parameter from kexec-tools.
Runtime tested on ar71xx with 2.6.39.4 (the wathdog must be stopped
before executing the new kernel). Compile tested with lantiq (3.1.4)
and brcm47xx (3.0.12).
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29674 3c298f89-4303-0410-b956-a3cf2f4a3e73
The microSD slot and the Real Time Clock is not working yet.
The miniPCIe interface is not tested due to the lack of a
suitable card.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29662 3c298f89-4303-0410-b956-a3cf2f4a3e73
These models are based on the AP99 reference board,
and uses the AR7241 SoC.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29658 3c298f89-4303-0410-b956-a3cf2f4a3e73
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>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29651 3c298f89-4303-0410-b956-a3cf2f4a3e73
om2p-watchdog package is OM2P specific. However a similar watchdog
mechanism exists on OM1P as well. This new package wants to substitute
om2p-watchdog with a new one which is suitable either for OM1P and OM2P.
Signed-off-by: Antonio Quartulli <ordex@autistici.org>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29647 3c298f89-4303-0410-b956-a3cf2f4a3e73
This patch adds the CT target for conntrack (enables manipulation of
conntrack events and supercedes NOTRACK) as well as the TTL/HL target and
match.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29645 3c298f89-4303-0410-b956-a3cf2f4a3e73
commit 8efa88540635 (sch_sfq: avoid giving spurious NET_XMIT_CN signals)
forgot to call qdisc_tree_decrease_qlen() to signal upper levels that a
packet (from another flow) was dropped, leading to various problems.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29642 3c298f89-4303-0410-b956-a3cf2f4a3e73
Works for me! ;-)
Patch-by: Russell Senior <russell@personaltelco.net>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29614 3c298f89-4303-0410-b956-a3cf2f4a3e73
