On 28/12/13 05:36, jonsm...@gmail.com wrote:
On Fri, Dec 27, 2013 at 4:16 PM, John Crispin wrote:
Hi
i just pushed a patch that i think will fix the issue. can you please test
it as i don't have access to a rt5350 board right now
Didn't fix it. Still same failure.
ok, i'll have access to a
On Fri, Dec 27, 2013 at 4:16 PM, John Crispin wrote:
> Hi
>
> i just pushed a patch that i think will fix the issue. can you please test
> it as i don't have access to a rt5350 board right now
Didn't fix it. Still same failure.
>
> John
--
Jon Smirl
jonsm...@gmail.com
__
Hi,
Le 27/12/2013 22:27, Darija Tadin-Đurović a écrit :
PS Thanks for the tip on AsiaRF. However, HLK's operating temperature range
is from -20°C to +70°C, which is really important right now
>>>
>>> That is impossible. RT5350 is only rated -10C to 55C.
>
> It's possible: the actual var
Hi John,
I checked out r39171, it's compiling presently. I'll let you know.
Darki
* John Crispin [2013-12-27 22:16:47 +0100]:
Hi
i just pushed a patch that i think will fix the issue. can you please
test it as i don't have access to a rt5350 board right now
John
--
Time is the quality
Hello,
* jonsm...@gmail.com [2013-12-27 15:34:44 -0500]:
On Fri, Dec 27, 2013 at 3:33 PM, jonsm...@gmail.com wrote:
On Fri, Dec 27, 2013 at 3:27 PM, Darija Tadin-Đurović <68da...@gmail.com> wrote:
Hi Jon,
what do you mean by "TCP checksum hardware"?
I had the same HW board working on (and b
Hi
i just pushed a patch that i think will fix the issue. can you please
test it as i don't have access to a rt5350 board right now
John
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/list
On Fri, Dec 27, 2013 at 3:33 PM, jonsm...@gmail.com wrote:
> On Fri, Dec 27, 2013 at 3:27 PM, Darija Tadin-Đurović <68da...@gmail.com>
> wrote:
>> Hi Jon,
>> what do you mean by "TCP checksum hardware"?
>> I had the same HW board working on (and before) r39018, but never after
>> (well, "never" b
On Fri, Dec 27, 2013 at 3:27 PM, Darija Tadin-Đurović <68da...@gmail.com> wrote:
> Hi Jon,
> what do you mean by "TCP checksum hardware"?
> I had the same HW board working on (and before) r39018, but never after
> (well, "never" being too strong a term, actually it does not work - with the
> same T
Hi Jon,
what do you mean by "TCP checksum hardware"?
I had the same HW board working on (and before) r39018, but never after
(well, "never" being too strong a term, actually it does not work
- with the same TCP checksum error - on r39019, r39020, r39024, r39033,
r39101).
Regards
Darki
PS Tha
So it is something to do with the TCP checksum hardware not the
switch. I have been blaming my failures on the switch code. I had
noticed before that UDP worked and TCP failed.
I'm using the AsiaRF module which is very similar to the Hi-Link one
but it is 25% smaller. It also brings out more pins.
Hello,
same problem here, with RT5350 / HLK-RM04.
Got it working up to and including r39018 (with Jiapeng Li's patches
from https://github.com/JiapengLi/OpenWrt-HiLink-HLK-RM04 ).
On r39019 it breaks because of incorrect TCP checksum in packets
outgoing from HLK-RM04 (and the destination correct
I had to revert this commit in order to get RT5350 working again. Any
ideas why this change impacts Ethernet on the RT5350?
commit b4fc4053d63294afbf77d1985b44a778d03af6c4
Author: blogic
Date: Mon Dec 9 17:29:29 2013 +
ralink: add TSO
Signed-off-by: John Crispin
git-svn-id:
12 matches
Mail list logo
