Hi Ilan, On Sun, 2011-07-10 at 16:16 +0200, Elias, Ilan wrote: > Hi Aloisio, > > I went over the userspace interface and it seems to me > that it's very much following the PN533 chip interface. > > As you probably know, the NFC forum is in the process of defining > a new industry standard for the NFC Controller Interface (NCI). > All NFC chips in the near future will probably support the NCI, I suppose that's arguable, especialy the "All" and "near future" terms of your statement :) Moreover, as far as I know, most NFC chips are currently HCI based and I expect the transition from HCI to NCI to not be that fast. > > which will provide a generic and standard interface for NFC functionality. > > I think that your current userspace interface might be too specific > for PN533 chip, and might not expose all the required NFC functionality. The idea for the current netlink userspace API is to be a generic and high level one. It should allow for userspace components to build their target management code and NDEF parsing code on top of it, without having to know if the below HW is HCI, NCI or anything else based. Also, please note that the current API is going to be soon extended to support target mode. > A similar case with Bluetooth, where HCI is the industry standard which > is supported by most Bluetooth chips, thus BlueZ support it of course. We plan to implement the NFC HCI (as in ETSI 102 622) code as a kernel component, and we're currently working on that. HCI NFC based chipsets will register against this layer which will then talk to the NFC core layer. The same architecture would hopefully work with NCI, although due to the lack of currently available public NCI specs, I can't guarantee that it won't require some small adjustments. > Doesn't it make more sense to make the userspace interface more similar to the NCI? Could you please point us at a publically available description of that interface ? Cheers, Samuel. -- 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
