On Thu, Jul 8, 2010 at 10:56 AM, Drasko DRASKOVIC <[email protected]> wrote: > On Thu, Jul 8, 2010 at 10:24 AM, Wayne Wang <[email protected]> wrote: >> hi Sebastein, >> >> here is code section for towitoko >> http://towitoko.sourcearchive.com/documentation/2.0.7-8/protocol__t0_8c-source.html >> >> It handles the APDU directly in the driver. >> Any comment :) > > No, it does not. What you show is not a driver code, but a transport > layer, which confirms Sebastien's statements, and my initial idea of > layer decoupling.
Well that's even simpler then. I didn't notice that (excuse: working on something else right now :) ). > > Driver does not get APDU at all, but TPDU formed by this transport > layer. Driver code (here not shown) implements functions like: > ICC_Async_Transmit() and ICC_Async_Receive() and does not have much > idea of protocol itself (I guess, though I did not look at fnc > implementation). > > Also, I am still wondering on the driver implementing functions like this : > ICC_Async_Receive (t0->icc, 1, buffer + recv) <-- receiving byte by byte ??? the towitoko code is ten years old :) > > That means that you will have yourself interrupt after each byte that > comes... Unsupportable from the performance point of view in a larger > RT system (like mobile phone). Yes, I saw you on the osmocombb mailing list ;) Sebastien > > BR, > Drasko > _______________________________________________ > Muscle mailing list > [email protected] > http://lists.drizzle.com/mailman/listinfo/muscle > _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
