Use a patch from gentoo which allows building libmount even
if the C library does not supports %ms/%as.
See: https://bugs.gentoo.org/406303
SVN-Revision: 33270
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.
SVN-Revision: 33265
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
SVN-Revision: 33216
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.
SVN-Revision: 33212
This takes the device_id and subsystem_id from the EEPROM, I'll add
the info for other Rt3xxx chips in the next days.
[jow: minor whitespace changes]
Signed-off-by: Daniel Golle <dgolle@allnet.de>
SVN-Revision: 33199
These are two Atheros modules we are using, just for the cosmetics to make them
show up with the proper names in LuCI.
Signed-off-by: Daniel Golle <dgolle@allnet.de>
SVN-Revision: 33186
rssileds is a small user-space process to control LEDs by polling the
signal quality reported by a WiFi interface. By using the iwinfo library,
rssileds is independent of the WiFi driver used.
It supports pwm controlled LEDs and may by used to nicely fade through
all colors in real-time of the rainbow while only wasting very little CPU
time and a small constant amount of system memory.
An example configuration for the ALL0258N will follow in the next patch.
This is a slightly improved version of rssileds, now quality values are
in percent and stuff is written to syslog.
Signed-off-by: Daniel Golle <dgolle@allnet.de>
SVN-Revision: 33163
When the underlying /etc/config/wireless got changed since the last "wifi up"
has been performed, the uci vap ifname state vars become inconsistent on a
subsequent "wifi up" and multiple vaps get mapped to the same ifnames which
confuses the gui and other processes relying on them.
For now call an explicit "wifi down" prior to each "wifi up" which will clear
up the state accordingly.
SVN-Revision: 33076
Give nas interface time to setup them selves before configuring them.
Should fix#11826.
Contributed by T-Labs, Deutsche Telekom Innovation Laboratories
Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
SVN-Revision: 33074
The structs defined in these header files should be the same as the
structes used by the platform code otherwise it will cause strange
runtime errors. By removing them from compat-wireless we will get a
compile error instead of a runtime error if they are out of sync.
SVN-Revision: 33006
* remove use_et, all supported drivers are using mii ioctls
* remove robo.phy_addr, phy_addr was always set to ROBO_PHY_ADDR.
* remove support for old kernel versions
* do_ioctl is allways called with buff == NULL
* use if_mii
SVN-Revision: 33002
When standalone ldd is selected in config the binary is installed in /usr/bin/ldd.
Signed-off-by: Michael Heimpold <mhei@heimpold.de>
SVN-Revision: 32891
I did not add the last patch, because it add some stubs for the flash drivers and our patches have to be changed for that, if the flash support in bcma is able to do something I will integrate it.
This also contains 3 additional patches fixing some bugs in bcma.
SVN-Revision: 32880
With the BRCM47xx image I have built (Linksys E3000), there are additional
writes following the completion of "mtd_replace_jffs2" which invalidate the
'trx_fixup' performed by 'mtd_replace_jffs2'. Moving the 'trx_fixup' to somewhere
after all writes have completed fixes the problem. I also noticed that 'erasesize'
used to compute 'block_offset' in 'mtd_fixtrx' is used before it is computed by
'mtd_check_open'; moving the call to 'mtd_check_open' up a few lines fixes this.
Unlike 'mtd_fixtrx', 'trx_fixup' appears to assume that the TRX header is always at
offset 0; which may be the cause of the problem described in Ticket #8960.
Signed-off-by: Nathan Hintz <nlhintz@hotmail.com>
SVN-Revision: 32866
