On Wed, Sep 19, 2012 at 12:02:37PM +0200, Steffen Rose wrote: > Hallo, Please use [email protected] mailing list :-)
> > more a question to this discussion then a meaning: (small english vocabulary fix: s/meaning/opinion/) > > > >> a) clear the TX-queue in Linux > [...] > > Yes, if it's a hardware limitation so be it. But if we design an > > interface it should support "clear everything" (a+b+c), but also just > > only c. > > > > Example: > I use more than one program, e.g.3 to communicate over one interface, > e.g.can0. > > Question: > The TX Queue is interface related, not program related, right? > > This would mean, if my program (one of the 3) clear the TX queue as part of > an > internal communication reset it would also destroy the messages of the other > programs. > > Is this idea right? Yes, you're right. That's an aspect of 'multi-user' environment, with a flexible 'user' interpretation. Kind regards, Kurt _______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
