On Wed, Jul 14, 2010 at 9:21 PM, Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx> wrote: > On Wed, Jul 14, 2010 at 8:24 PM, Satya <satya.rao@xxxxxxxxxxxxxxxxxx> wrote: >> >> I just wonder if the delimiter length CRC is wrong, where from we >> get the length of the data packet to get to a state where we say >> we have received the data packet with correct CRC ? >> >> I am not sure about this. I appreciate if someone could clarify this. >> Thanks. > > Great question :), Kyungwan? ---- Kyungwan wrote: Actually, the scenario we are addressing here is, delimiter "after" good crc subframe has crc error such that AR9003 keeps searching next delimiter but in a meanwhile, restart PHY error occurs and receiving stops. In this case, by design, AR9003 reports these PHY error and delimiter crc error by using Rx descriptor of good crc subframe and S/W used to discard this good crc subframe because of PHY error. But after more investigation, we found this scenario and we could save this good crc subframe with the attached patch. Please note that this happens only if AR9003 advanced feature (restart PHY error) is enabled.excemption ---- So it seems that by design the delimiter CRC error status is just borrowed for this exception by our MAC hardware folks to annotate this specific situation. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
