Its question for me: I scanned network A with wireshark and found that at network have more broadcast and multicast messages. Other people have been mentioning the problem occasionally in this group. The reason I ask is that we think that mac. Atmel MACB at 0xfffc irq 21 3a:
|Date Added:||18 April 2018|
|File Size:||29.68 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Is there anything I can check by myself without an ICE to see what’s wrong? Atmel MACB at 0xfffc irq 21 3a: Of course, if it’s a cache flushing issue, we might not see anything wrong in the descriptors.
TX underrun, resetting buffers”?
Linux Kernel Driver DataBase: CONFIG_MACB: Cadence MACB/GEM support
Software needs ahmel re-initialize the transmit queue after a transmit error. I also did a test to see if Auto probing works and changed the EK’s phy address to 1 and macb did pick it up and Ethernet works fine. At my workplace working OK.
I wish all vendors were as effective and efficient. But from a quick look, it seems like this is an issue with the board code — you probably need to set the PHY address mask because the PHY autoprobing attmel work.
Our symptoms were that the ethernet appeared to start but then would just sit there incrementing rx errors but not actually do anything. Why in networks A, B hung at Mbit Full duplex? Currently I make in code Reset Tx descriptors, and testing.
I scanned network A with wireshark and found that at network have more broadcast and multicast messages. I’ve added some printk s in underrun handler.
If it’s a problem with the descriptor, it would probably help to dump out some information about the ring state, i.
Other people have been mentioning the problem occasionally in this group. But currently, my devices working nice some months.
macb: Kill PHY reset code [Linux 4.16]
On Fri, 17 NovHaavard Skinnemoen wrote: Currently, with this changed macb. Thanks for submitting a nice, clean driver that was so painless to apply to the latest kernel. No registered users and 0 guests. So, at work place I test my device with simple test sofware, amel send arp request to device and sent more broadcast messages. Jeff – To unsubscribe from this list: On Thu, 16 Nov Free forum by Nabble.
AVR32 uc3a macb driver serious problem. Yes, that’s the message. It was discussed on the avrfreaks forum. Maybe some mechanism is already provided. The list of descriptors: Thanks in advance, Lucas. Tx Ring full when queue awake! These changes are mostly about making the driver more compatible with the at91 infrastructure.
The reason I ask is that we think that mac. Atmel MACB at 0xfffc irq 21 It have 2 modes.