Recent searches
Search options
@sycophantic @whitequark Interesting all of my MACs to date has just treated the 802.1q tag the same as an ethertype for the most part (only caring about the tag once i start making forwarding decisions) and my padding insertion logic pads the entire frame to 64.
I haven't got to the point of adding outbound 802.1q tags on trunk ports yet but when I do, I'll probably need to patch my MAC code that does padding insertion to change the target frame length based on whether a tag is present
@azonenberg @sycophantic so while I have your attention: in my Ethernet deframer (connected to output of PHY), how should I treat the preamble? do I just sync on the SFD and ignore all 55's before it? do I count the 55's?
@whitequark @sycophantic My own implementation looks for I think at least one 55 as a state machine trigger followed by a D5 and then goes to frame content. Do not count the 55s, some PHYs/protocols can remove some of them (e.g. 10baseT before bit sync is achieved)
@azonenberg @sycophantic right, that's exactly how I implemented it already