| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Add two helpers for generating correctly tagged images for the T-Home
Speedport W 303V Typ B as well as xor'd ones as required by CFE.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26877
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rename the DSL-274xB rev C2's board ID to "AW4139" to match the one used
for the rev C3 (same hardware) and add a fixup for C2. Also generate
images for C3.
While we are at it, rename the LEDs to conform to the Linux LED naming
conventions.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26876
|
|
|
|
|
|
| |
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26875
|
|
|
|
|
|
|
|
|
| |
Make the fixup board ID independent from the image name to allow using
the same board ID for similar devices.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26874
|
|
|
|
| |
SVN-Revision: 26873
|
|
|
|
| |
SVN-Revision: 26872
|
|
|
|
|
|
|
|
| |
stuff into its own file makes sense.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 26868
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds 802.1Q VLAN support for the ADM6996M chip.
The driver is loaded for both the FC and M model. It will detect which of the
two chips is connected. The FC model is initialised, but no further
functionality is offered.
The PHY driver will always report "100 Mbit/s, link up", for both the M and FC
models. This reflects the fact that the link between switch chip and Ethernet
MAC is always on[1].
Further documentation can be found in the kernel's
Documentation/networking/adm6996.txt
Signed-of-By: Peter Lebbing <peter@digitalbrains.com>
SVN-Revision: 26865
|
|
|
|
|
|
| |
Patch-by: Cezary Jackiewicz <cezary@eko.one.pl>
SVN-Revision: 26862
|
|
|
|
|
|
| |
Based on a patch by Magyar Szabolcs <mszabi@freemail.hu>
SVN-Revision: 26861
|
|
|
|
| |
SVN-Revision: 26860
|
|
|
|
| |
SVN-Revision: 26859
|
|
|
|
| |
SVN-Revision: 26858
|
|
|
|
|
|
| |
space, so a default route of ::/0 is more correct. Thanks Dave Taht
SVN-Revision: 26857
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reading of the PHY registers occasionally returns with bogus values
under heavy load. This misleads the PHY driver and thus causes false
link/speed change notifications which leads to performance loss.
This is easily noticable during an iperf session:
...
[ 3] 52.0-53.0 sec 11.3 MBytes 94.4 Mbits/sec
[ 3] 53.0-54.0 sec 11.4 MBytes 95.4 Mbits/sec
eth1: link down
br-lan: port 2(eth1) entering forwarding state
eth1: link up (100Mbps/Full duplex)
br-lan: port 2(eth1) entering forwarding state
br-lan: port 2(eth1) entering forwarding state
[ 3] 54.0-55.0 sec 6.75 MBytes 56.6 Mbits/sec
[ 3] 55.0-56.0 sec 0.00 Bytes 0.00 bits/sec
[ 3] 56.0-57.0 sec 10.5 MBytes 88.1 Mbits/sec
...
[ 3] 169.0-170.0 sec 11.4 MBytes 95.4 Mbits/sec
[ 3] 170.0-171.0 sec 11.4 MBytes 95.4 Mbits/sec
eth1: link up (10Mbps/Half duplex)
[ 3] 171.0-172.0 sec 7.63 MBytes 64.0 Mbits/sec
[ 3] 172.0-173.0 sec 9.38 MBytes 78.6 Mbits/sec
eth1: link up (100Mbps/Full duplex)
[ 3] 173.0-174.0 sec 11.3 MBytes 94.4 Mbits/sec
[ 3] 174.0-175.0 sec 11.4 MBytes 95.4 Mbits/sec
SVN-Revision: 26856
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The function __devinit ag71xx_probe() references
a function __devexit ag71xx_phy_disconnect().
This is often seen when error handling in the init function
uses functionality in the exit path.
The fix is often to remove the __devexit annotation of
ag71xx_phy_disconnect() so it may be used outside an exit section.
The function ag71xx_phy_disconnect() references a function in an exit
section.
Often the function ag71xx_ar7240_cleanup() has valid usage outside the
exit section
and the fix is to remove the __devexit annotation of
ag71xx_ar7240_cleanup.
SVN-Revision: 26855
|
|
|
|
| |
SVN-Revision: 26854
|
|
|
|
|
|
| |
usb_modeswitch on boot and possibly others (#9352)
SVN-Revision: 26848
|
|
|
|
| |
SVN-Revision: 26846
|
|
|
|
| |
SVN-Revision: 26845
|
|
|
|
| |
SVN-Revision: 26844
|
|
|
|
| |
SVN-Revision: 26843
|
|
|
|
| |
SVN-Revision: 26842
|
|
|
|
| |
SVN-Revision: 26841
|
|
|
|
| |
SVN-Revision: 26840
|
|
|
|
| |
SVN-Revision: 26837
|
|
|
|
| |
SVN-Revision: 26836
|
|
|
|
| |
SVN-Revision: 26833
|
|
|
|
| |
SVN-Revision: 26832
|
|
|
|
|
|
| |
sprom data from the platform device to the correct pointer.
SVN-Revision: 26829
|
|
|
|
| |
SVN-Revision: 26828
|
|
|
|
| |
SVN-Revision: 26827
|
|
|
|
| |
SVN-Revision: 26822
|
|
|
|
| |
SVN-Revision: 26819
|
|
|
|
| |
SVN-Revision: 26818
|
|
|
|
| |
SVN-Revision: 26817
|
|
|
|
| |
SVN-Revision: 26816
|
|
|
|
| |
SVN-Revision: 26815
|
|
|
|
|
|
|
|
| |
unprovided kernel crypto modules that are useful for IPSEC. This is an alternative to breaking these modules out into kmod-crypto-wq (crypto_wq.ko), kmod-crypto-rng (rng.ko and krng.ko), and kmod-crypto-iv (eseqiv.ko and chainiv.ko).
Signed-off-by: Lars Hjersted <lars@hjersted.com>
SVN-Revision: 26814
|
|
|
|
|
|
|
|
| |
kmod-ipsec. Also remove the extraneous kmod-crypto-core dependency to eliminate recursion.
Signed-off-by: Lars Hjersted <lars@hjersted.com>
SVN-Revision: 26813
|
|
|
|
|
|
|
|
|
|
|
|
| |
kmod-crypto-rng, and kmod-crypto-iv packages. These packages provide some missing kernel crypto modules which are required for IPSEC. The strongswan4, ipsec-tools, and possibly other IPSEC packages do not work properly without these modules.
NOTE: The KCONFIG associated with each of these modules gets selected
whenever CRYPTO_MANAGER (kmod-crypto-manager) is selected so these
modules are already being built.
Signed-off-by: Lars Hjersted <lars@hjersted.com>
SVN-Revision: 26812
|
|
|
|
|
|
| |
unneeded on the Geos platform.
SVN-Revision: 26811
|
|
|
|
|
|
| |
deadlocks
SVN-Revision: 26810
|
|
|
|
| |
SVN-Revision: 26809
|
|
|
|
| |
SVN-Revision: 26808
|
|
|
|
| |
SVN-Revision: 26807
|
|
|
|
| |
SVN-Revision: 26806
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
passthrough Two examples of potentially useful configurations (commented out, of course):
(a) map the ssh service running on the firewall to 22001 externally, without modifying the configuration of the daemon itself. this allows port 22 on the WAN side to then be port-forwarded to a
LAN-based machine if desired, or if not, simply obscures the port from external attack.
(b) allow IPsec/ESP and ISAKMP (UDP-based key exchange) to happen by default. useful for most modern VPN clients you might have on your WAN.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 26805
|
|
|
|
|
|
| |
(standard in Debian). The modified patch reflects the current upstream: http://git.savannah.gnu.org/cgit/quilt.git/commit/?id=38df0b210c3df67f3e784af92232ae1946b98ecd
SVN-Revision: 26804
|
|
|
|
| |
SVN-Revision: 26803
|