Messages in this thread | | | Date | Tue, 29 Mar 2011 12:59:31 +0100 | From | Alan Cox <> | Subject | Re: [PATCH] NFC: Driver for Inside Secure MicroRead NFC chip |
| |
> The difference between the two is where you keep the common > NFC logic:
I think I'd disagree on that > > If you have a character device, it will be like a serial port > connecting to a modem. Any higher-level protocols live in the > user space and are limited to a single application then, which > is required to have appropriate priviledges to open the device.
A socket is just an API just as a file, you can put the stack in either place in either case.
> character device is its simplicity, so that would be preferred > if you only expect a very small set of possible applications > for this.
NFC is not particularly performance dependant so having a lot of the stack in a daemon isn't really going to hurt anything too much on a client embedded device/phone.
The bigger question is probably what it needs to look like the other end - ie the server side embedded devices doing transactions.
| |