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>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33266 3c298f89-4303-0410-b956-a3cf2f4a3e73
It is required by sysupgrade on some boards, and it is only
working if a suitable /etc/fw_env.config is present on the
target board. If an user creates such configuration he/she
should know that it is a dangerous tool. The devices can
be bricked in several other ways anyway.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33265 3c298f89-4303-0410-b956-a3cf2f4a3e73
The 'mtdparts=' prefix and the name of the flash device is missing.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33226 3c298f89-4303-0410-b956-a3cf2f4a3e73
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>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33224 3c298f89-4303-0410-b956-a3cf2f4a3e73
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>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33219 3c298f89-4303-0410-b956-a3cf2f4a3e73
doesn't need to do it 20 times all the time, missing loop condition check
Signed-off-by: Conor O'Gorman <i@conorogorman.net>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33217 3c298f89-4303-0410-b956-a3cf2f4a3e73
This is fix an issue with dnsmasq's RA that does not set the "on-link" bit, making all local IPv6 traffic go to the router then to the destination host, not directly to each other.
patch is from dnsmasq git
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33216 3c298f89-4303-0410-b956-a3cf2f4a3e73
It seems that the comgt package does not handle the Huawei 3G USB dongle E176 correctly (and probably other Huawei dongles too). My dongle appears as ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem and 3G/UMTS
connections work well. However, no connection is established if only 2G/GPRS is available: the pppd chat script fails with NO CARRIER although the dongle is registered to the network (via 2G). As outlined in this wiki or this
blog, Huawei chips use the AT^SYSCFG command to set 2G or 3G mode, which is not implemented in comgt at the moment. Thus I wrote a patch for /lib/network/3g.sh which adds support for the "service" option in the network
configuration with Huawei dongles. By default (if no "service" option is specified) also 2G is used when 3G is unavailable. The Huawei dongle is detected analogously to other chips (the output of gcom -d /dev/ttyUSB0 -s
/etc/gcom/getcardinfo.gcom is scanned for huawei).
Some further information: The AT^SYSCFG command seems to be respected only once after the dongle is attached (or after the host is powered up). Resetting the dongle seems to render the serial port unusable in some cases.
However, the patch sets a useful mode by default which should cover most use cases (3G preferred, but 2G allowed) and if 3G-only or 2G-only mode is required the device can be power cycled.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33212 3c298f89-4303-0410-b956-a3cf2f4a3e73
