You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I am using the jetson nano and for the kernel we refer to the linux tegra kernel branch oe4t-patches-l4t-r32.7.3 and for the wifi we use the cypress 43455 wifi driver and it works great. But we did the update to oe4t-patches-l4t-r32.7.4 and then we get hiccups in the wifi connection. It works, but there are some short hangs now and then, it's not fluent anymore. It really is a huge difference. Is there any commit that could be the culprit for this? Also the latest kernel branch oe4t-patches-l4t-r32.7.5 has the issue. I also tried the latest cypress driver and it does not make a difference, so the kernel branch makes the difference.
Thanks for any pointers,
Best regards
To Reproduce
Steps to reproduce the behavior:
Use tegra-kernel branch oe4t-patches-l4t-r32.7.4 on kirkstone with jetson nano
Check wifi is having hiccups.
The text was updated successfully, but these errors were encountered:
@metalMajor have you attempted to reproduce with the L4T release as delivered by NVIDIA an a Nano devboard to see if it's related to OE4T patches or some differences in the kernel as delivered by NIVIDA between these releases?
Describe the bug
I am using the jetson nano and for the kernel we refer to the linux tegra kernel branch oe4t-patches-l4t-r32.7.3 and for the wifi we use the cypress 43455 wifi driver and it works great. But we did the update to oe4t-patches-l4t-r32.7.4 and then we get hiccups in the wifi connection. It works, but there are some short hangs now and then, it's not fluent anymore. It really is a huge difference. Is there any commit that could be the culprit for this? Also the latest kernel branch oe4t-patches-l4t-r32.7.5 has the issue. I also tried the latest cypress driver and it does not make a difference, so the kernel branch makes the difference.
Thanks for any pointers,
Best regards
To Reproduce
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: