Hallo Tobias,
On Friday 03 August 2012 01:50:26 Tobias Diedrich wrote:
> If you want to poke at the ramips ethernet driver, I have a patch
> that I haven't submitted yet (I think it has occasional problems on
> bootup and probably unconditionally uses features that are not available on
> all chips
Tobias Diedrich wrote:
> If you want to poke at the ramips ethernet driver, I have a patch
> that I haven't submitted yet (I think it has occasional problems on
> bootup and probably unconditionally uses features that are not available on
> all chipset types):
>
> This adds support for HW checksum
If you want to poke at the ramips ethernet driver, I have a patch
that I haven't submitted yet (I think it has occasional problems on
bootup and probably unconditionally uses features that are not available on
all chipset types):
This adds support for HW checksumming, scatter/gather DMA and
generi
Hi!
On 17/07/12 11:22, Florian Fainelli wrote:
> Transmit timeouts are really a bad situation, I'd rather check where they do
> come from, maybe your transmit path is locked for too long, or you are
> loosing
> transmit completion interrupts?
Ethernet generally works stable and well on all Rt3
Hi Daniel,
On Tuesday 17 July 2012 07:00:35 Daniel Golle wrote:
> Hi!
>
> I start to observe this recently on Rt305x based boards:
>
> WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x170/0x278()
> NETDEV WATCHDOG: eth0 (): transmit queue 0 timed out
>
> Maybe TX_TIMEOUT should be a bit m
Hi!
I start to observe this recently on Rt305x based boards:
WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x170/0x278()
NETDEV WATCHDOG: eth0 (): transmit queue 0 timed out
Maybe TX_TIMEOUT should be a bit more generous?
Also this made me realize that the ramips ethernet driver uses onl
