Quoth Dave Page: > A small change was required to make the BUSY OpCode transition to > the correct state in fsm_foe.c, and have the subsequent FoE Ack.req show > the correct PacketNo IAW > ETG.1020 Section 15 > "FoE Extension." > > The attached patch includes the FoE PacketNo length fix from Gavin > Lambert
Did you see my other patch specifically for FoE busy? My slave is working fine for busy reads with both of my patches applied. (There was a third patch included in the same email as the busy patch, but that's optional and just increases debug logging.) My patch also fixes handling of error packets. As for incrementing the packet number or not, it's been a while since I looked at that so I don't remember whether it increments or not with my patches applied, but I think I remember making it do whatever the SSC was expecting. _______________________________________________ etherlab-dev mailing list etherlab-dev@etherlab.org http://lists.etherlab.org/mailman/listinfo/etherlab-dev
