Hallo, more a question to this discussion then a meaning:
> >> 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? -- Mit freundlichen Grüßen / Regards Steffen Rose -------------------------------------------------------------- emtas - your embedded solution partner Meet our specialists on the SPS IPC drives fair from 27 to 29.November in Nuremberg -------------------------------------------------------------- emtas GmbH Fischweg 17 06217 Merseburg Tel.: +49(0)3461-79416-0 Fax.: +49(0)3461-79416-10 www.emtas.de - [email protected] Geschäftsführer: Andreas Boebel, Torsten Gedenk, Steffen Rose Registergericht: Amtsgericht Stendal Registernummer: HRB 17616 UstID: DE281092198 -------------------------------------------------------------- _______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
