On Mon, Feb 1, 2010 at 2:05 PM, Wolfgang Grandegger <[email protected]> wrote:
> > In real-time, transfer errors are not allowed to happen, otherwise > deterministic behavior can not be guaranteed. I actually hesitate to add > too much extra code for this feature. Note also, that the network stack > is not hard real-time anyway and the "-rt" patch does only help partially. > I fully agree. The problem is that without some care one shot mode now is broken (I mean it can just halt the driver forever). So we can disable it otherwise something is needed. I feel like the approach from my last patch above has a "flavor" more like the idea behind the OSM (but I agree with you that it's nothing like real RT) than having a timeout (that can be implemented using the standard netdev mechanism or with a timer) which introduces a considerable delay. To say the truth, it looks like to me that OSM was added to the mcp2515 just to say it is supported without much thought by microchip. Anyway let me know what do you think is better: I could prepare a patch based on one of the methods listed above or it would be wise to just remove OSM; otherwise I guess we will have more bug reports when people enable it. -- Christian Pellegrin, see http://www.evolware.org/chri/ "Real Programmers don't play tennis, or any other sport which requires you to change clothes. Mountain climbing is OK, and Real Programmers wear their climbing boots to work in case a mountain should suddenly spring up in the middle of the computer room." _______________________________________________ Socketcan-core mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-core
