[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 6 Jun 2011 15:22:01 -0500
From: Pavan Savoy <pavan_savoy@...y.com>
To: Samuel Ortiz <sameo@...ux.intel.com>
Cc: Waldemar.Rymarkiewicz@...to.com, arnd@...db.de,
linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
hthebaud@...idefr.com, matti.j.aaltonen@...ia.com,
alan@...rguk.ukuu.org.uk, Sebastian.Chlad@...to.com
Subject: Re: [PATCH] NFC: Driver for Inside Secure MicroRead NFC chip
On Thu, Mar 31, 2011 at 9:30 AM, Samuel Ortiz <sameo@...ux.intel.com> wrote:
> On Thu, Mar 31, 2011 at 06:24:50PM +0300, Waldemar.Rymarkiewicz@...to.com 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.
So, why was the network interface 'ala eth0 or the netlink interface dropped?
I saw these patches recently "NFC: add nfc subsystem core" - which
seem to add just the device /dev/nfc - am I correct ?
Or missing something ?
> 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@...r.kernel.org
> 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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists