| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
SVN-Revision: 26922
|
|
|
|
|
|
| |
Signed-off-by: Jan Willies <jan@willies.info>
SVN-Revision: 26920
|
|
|
|
|
|
| |
Signed-of-By: Lauri Võsandi <lauri.vosandi@gmail.com>
SVN-Revision: 26919
|
|
|
|
| |
SVN-Revision: 26918
|
|
|
|
|
|
| |
some instances
SVN-Revision: 26915
|
|
|
|
| |
SVN-Revision: 26913
|
|
|
|
| |
SVN-Revision: 26912
|
|
|
|
| |
SVN-Revision: 26911
|
|
|
|
| |
SVN-Revision: 26908
|
|
|
|
| |
SVN-Revision: 26906
|
|
|
|
|
|
| |
Thank you Peter Wagner for the patch. I refreshed the kernel patches and added the md5sum of the kernel.
SVN-Revision: 26905
|
|
|
|
|
|
|
|
|
| |
Since the oldest kernel in trunk is 2.6.30 the modules always use the
newer names, so we can just use the _generic prefix directly.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26903
|
|
|
|
|
|
|
|
|
| |
There's only 2.6, so it doesn't make sense to mention modules that are
2.4 only or for modules that they are available only for 2.6.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26902
|
|
|
|
|
|
|
|
|
| |
With no 2.4 support in trunk, we can safely remove any 2.4 definitions for
kmods and merge the 2.6 definitions into the generic ones.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26901
|
|
|
|
|
|
|
|
|
| |
Since there's only 2.6 in trunk $(KMOD_SUFFIX) can be safely replaced with
ko for all mainline kernel modules.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26900
|
|
|
|
| |
SVN-Revision: 26891
|
|
|
|
| |
SVN-Revision: 26890
|
|
|
|
| |
SVN-Revision: 26889
|
|
|
|
| |
SVN-Revision: 26885
|
|
|
|
| |
SVN-Revision: 26884
|
|
|
|
| |
SVN-Revision: 26883
|
|
|
|
|
|
| |
the patch during r26879 and r26880.
SVN-Revision: 26882
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for the alix2*, alix3, and alix6 headless (non-VGA equipped) SBC's.
Note that the Alix6 uses GPIO 27 to disable wireless transmit (W_DIS#), whereas on all other versions this is used to actuate the speaker.
GPIO 1 : SIM select (Alix6)
GPIO 6 : LED1
GPIO 25 : LED2
GPIO 27 : LED3 or RFKILL (Alix6)
GPIO 24 : Soft switch 1
No kernel version bump. Added i2c-scx200-acb for lm-sensors support.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 26880
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
headless (non-VGA equipped) SBC's.
Note that the Alix6 uses GPIO 27 to disable wireless transmit (W_DIS#), whereas on all other versions this is used to actuate the speaker.
GPIO 1 : SIM select (Alix6)
GPIO 6 : LED1
GPIO 25 : LED2
GPIO 27 : LED3 or RFKILL (Alix6)
GPIO 24 : Soft switch 1
No kernel version bump. Added i2c-scx200-acb for lm-sensors support.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 26879
|
|
|
|
|
|
|
|
|
| |
Add the required board definition, default config and image generation for
the T-Home Speedport W 303V Typ B.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26878
|
|
|
|
|
|
|
|
|
| |
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
|