Hi all, On Thu, Mar 31, 2011 at 12:30 PM, Samuel Ortiz <sameo@xxxxxxxxxxxxxxx> wrote: > On Thu, Mar 31, 2011 at 06:24:50PM +0300, Waldemar.Rymarkiewicz@xxxxxxxxx wrote: >> Hi Samuel, >> >> >That's the Bluetooth approach, and it works just fine as well. >> >However, the netlink option for sending commands and receiving >> >answers to/from a subsystem sounds more appropriate, at least to me. >> >> I haven't used netlink in practice, so just wondering why netlink. I assume, then, it's more suitable :) >> > Have a look at the wireless nl80211.c implementation. It's a good example for > that sort of usage. We are finalizing a NFC stack prototype and we decided to use generic netlink. But during the implementation we found a disadvantage of this approach. While implementing data_exchange through netlink, it was not possible to avoid memcpy as the skbuff coming from netlink can contain more than one message. We didn't find any implementation that uses netlink to exchage data. As in the nl80211, the netlink is used only for control commands. We plan to publish for comments this prototype early next week. Then we plan to implement a version using AF_NFC. Regards, Aloisio Almeida Jr INdT - Instituto Nokia de Tecnologia > Cheers, > Samuel. > > -- > Intel Open Source Technology Centre > http://oss.intel.com/ > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
