Sascha Herrmann wrote: > I think you are right here, I had the setting of RX_SAFE_MODE removed in > an earlier version, too. If I understand this right, we only need to set > RX_SAFE_MODE after reading the frame buffer.
I think we just need to set it once and then never touch it again. At least that's what seems to work quite well in atusb. Here, I empty the buffer in a single read and thus don't need to invoke static buffer protection, but I think this shouldn't make a difference. > I fear your thoughts about > the race condition with the double reading of the frame buffer are true > too. I will try to get some time to work on this. Back then, Dmitry explained [1] that the driver used static buffer protection to keep the buffer across the two (not just one) accesses. I think this should work as intended. But if you come across a problem, that would of course be interesting, too :-) [1] http://www.mail-archive.com/linux-zigbee-devel@lists.sourceforge.net/msg00589.html - Werner ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ Linux-zigbee-devel mailing list Linux-zigbee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
