From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Hartkopp Subject: Re: vcan name Date: Wed, 16 May 2012 14:38:39 +0200 Message-ID: <4FB39FCF.4070108@hartkopp.net> References: <4FB25A39.7090608@hartkopp.net> <20120515135429.GB1414@vandijck-laurijssen.be> <4FB27B78.4070002@hartkopp.net> <20120515184832.GA414@vandijck-laurijssen.be> <4FB2BD82.2060105@hartkopp.net> <20120515211613.GB482@vandijck-laurijssen.be> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: Received: from mo-p00-ob.rzone.de ([81.169.146.161]:50384 "EHLO mo-p00-ob.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754835Ab2EPMih (ORCPT ); Wed, 16 May 2012 08:38:37 -0400 In-Reply-To: <20120515211613.GB482@vandijck-laurijssen.be> Sender: linux-can-owner@vger.kernel.org List-ID: To: Kurt Van Dijck Cc: "linux-can@vger.kernel.org" On 15.05.2012 23:16, Kurt Van Dijck wrote: >> 4: vcan0: mtu 72 qdisc noqueue state UNKNOWN mode DEFAULT >> link/can >> RX: bytes packets errors dropped overrun mcast >> 46 8 0 0 0 0 >> TX: bytes packets errors dropped carrier collsns >> 46 8 0 0 0 0 > > wasn't your vcan interface named 'helga' :-) ? > > Kurt Well yes. On my box @work i usually have vcan0 .. vcan3 and helga - but i did not want to confuse the other readers in the first CAN FD test setups ;-) Regards, Oliver