| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
SVN-Revision: 26846
|
|
|
|
| |
SVN-Revision: 26845
|
|
|
|
| |
SVN-Revision: 26844
|
|
|
|
| |
SVN-Revision: 26843
|
|
|
|
| |
SVN-Revision: 26842
|
|
|
|
| |
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: 26818
|
|
|
|
| |
SVN-Revision: 26817
|
|
|
|
|
|
| |
unneeded on the Geos platform.
SVN-Revision: 26811
|
|
|
|
| |
SVN-Revision: 26803
|
|
|
|
|
|
| |
ethernet driver
SVN-Revision: 26802
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If there is no sprom on an ssb based pci device on the brcm47xx
architecture ssb now asks the architecture code to look into the nvram
to get some sprom data for this device. Now we are able to read out
pci/1/1/ foo or pci/1/3/ foo config options.
This will fix some problems where the wireless devices does not got an
mac address and the following message was show:
ssb: WARNING: Invalid SPROM CRC (corrupt SPROM)
SVN-Revision: 26801
|
|
|
|
|
|
| |
- fixes some issues with ath9k
SVN-Revision: 26797
|
|
|
|
|
|
| |
default network config
SVN-Revision: 26779
|
|
|
|
| |
SVN-Revision: 26778
|
|
|
|
| |
SVN-Revision: 26777
|
|
|
|
| |
SVN-Revision: 26776
|
|
|
|
| |
SVN-Revision: 26772
|
|
|
|
|
|
|
|
|
| |
SPIN_LOCK_UNLOCKED has been deprecated since 2.6.19 and will get removed
in 2.6.39, so replace it with DEFINE_SPINLOCK().
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26770
|
|
|
|
| |
SVN-Revision: 26748
|
|
|
|
| |
SVN-Revision: 26747
|
|
|
|
| |
SVN-Revision: 26746
|
|
|
|
| |
SVN-Revision: 26715
|
|
|
|
| |
SVN-Revision: 26710
|
|
|
|
| |
SVN-Revision: 26709
|
|
|
|
| |
SVN-Revision: 26708
|
|
|
|
| |
SVN-Revision: 26707
|
|
|
|
| |
SVN-Revision: 26706
|
|
|
|
|
|
|
|
|
|
| |
Use offset from struct mtd_part instead of struct mtd_partition for defining
the new partitions. This enables the usage of MTDPART_OFS_APPEND macro in
struct mtd_partition.
Signed-off-by: Jochen Friedrich <jochen@scram.de>
SVN-Revision: 26705
|
|
|
|
|
|
| |
Signed-off-by: Jochen Friedrich <jochen@scram.de>
SVN-Revision: 26704
|