mtk-20170518/target/linux/ramips/files, branch master

ralink: drop old ethernet driver

2015-12-17T09:25:30+00:00

Signed-off-by: John Crispin 

SVN-Revision: 47899

ralink: remove stray "+" from ethernet driver

2015-12-12T06:42:17+00:00

this is what you get if you manually apply patches with c&p

Signed-off-by: John Crispin 

SVN-Revision: 47877

ralink: bump to the target to v4.3

2015-12-10T19:06:32+00:00

Signed-off-by: John Crispin 

SVN-Revision: 47831

ramips: fix for kernel 4.0 napi repoll need return budgets number

2015-10-30T22:32:49+00:00

Signed-off-by: Michael Lee 

SVN-Revision: 47306

ramips: Enable rx of 1536 bytes ethernet frames on MT7621

2015-10-05T10:26:34+00:00

The default switch frame size (with FCS + header) is 1536 bytes. But the
GMAC only accepted frames up to 1522 bytes. Setting it to 1536 allows to
receive ethernet frames using the full of MTU 1500 + an extra VLAN header +
VLAN header added by the switch.

Signed-off-by: Sven Eckelmann 

SVN-Revision: 47117

ramips: Fix too small rx buffer

2015-10-05T10:26:28+00:00

The driver assumes that the maximum received buffer for non-jumbo frames is
1536 bytes. But the allocation of the rx fragment doesn't reflect that. It
currently allocates fragments which will only be large enough to be used as
rx buffer with the size of 1534 bytes. This is problematic because the GMAC
will now try to write to 2 bytes which don't belong to its receive buffer
when a large enough ethernet frame is received.

This may already be a problem on existing chips but will at least become a
problem when the 1536 byte rx modus is enabled on MT7621a. It is required
on this SoC to receive ethernet frames which use their full 1500 bytes MTU
and a VLAN header next to the switch VLAN tag.

Signed-off-by: Sven Eckelmann 

SVN-Revision: 47116

ramips: Fix setting of rx buffer length

2015-10-05T10:26:21+00:00

The length of the DMA rx buffer was always set to 0 because the function
for extracting the length was used to calculate the value for setting it.
Instead the macro has to be split in a get and set function similar to the
TX_DMA_(GET_|)PLEN(0|1) macro.

No problem was noticed on MT7621a before this was changed and thus maybe it
was hidden by different problem which is not yet fixed.

Signed-off-by: Sven Eckelmann 

SVN-Revision: 47115

ramips: Allow to receive vlan over untag ports on MT7530

2015-10-05T10:26:09+00:00

The MT7530 switch driver with enable_vlan set will automatically set all
ports to the user port mode. The hardware will remove the incoming vlan tag
on these ports and use it for its internal vlan. This is usually not wanted
and makes it impossible to communicate via vlan over the switch in both
directions.

It is possible to configure a switch port to "transparent mode" when this
port is only used as untag in the switch VLANs. This will disable the VLAN
untagging of packets when they were received on this port. The tagging on
"tag" ports based on the vlan id is still working.

The transparent port mode cannot be used when a port is both used in a VLAN
as "tag" and in another one as "untag" port.

Signed-off-by: Sven Eckelmann 

SVN-Revision: 47114

ramips: collect rx related members to fe_rx_ring struct

2015-07-10T19:41:48+00:00

Signed-off-by: michael lee 

SVN-Revision: 46295

ramips: add xmit_more support

2015-07-10T19:41:42+00:00

use pktgen to verify on rt3662. can improve transmit rate.
pkt_size 1500
burst 1 : 807Mb/sec
burst 8 : 984Mb/sec

pkt_size 60
burst 1 : 57Mb/sec
burst 8 : 236Mb/sec

Signed-off-by: michael lee 

SVN-Revision: 46294