On Fri, 2011-06-03 at 17:18 -0300, Lauro Ramos Venancio wrote: > Actually, we don't expect more than a couple of targets because of NFC > short range. I know. > I agree that this can be a problem if we start supporting vicinity cards. I have no idea what that is, but I think that you'll start adding attributes at some point, and somebody will also build "scanners" with better RX sensitivity ... I'd rather not design something that _right now_ limits you to around 100 targets. > I agree that this is a better solution. But I think we don't need a > generation counter because only a new polling operation (start_poll > call) can change the targets list (i.e. there is no passive polling). > We don't need a generation counter here because we have the events > NFC_EVENT_DEVICE_ADDED and NFC_EVENT_DEVICE_REMOVED. So, it is > possible to keep the device list consistency listening for these > events. That may be true, but it complicates coding in userspace. Much easier to check a generation counter (in both cases) to see if data is consistent than to listen to multiple events concurrently with receiving a dump. johannes -- 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
