From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <45E838E3.80506@domain.hid> Date: Fri, 02 Mar 2007 15:46:59 +0100 From: Wolfgang Grandegger MIME-Version: 1.0 Subject: Re: [Xenomai-help] problems installing peak CAN dongle References: <45E7E49C.2000005@domain.hid> <45E7F453.9090803@domain.hid> <45E7FFA6.3060405@domain.hid> <45E808C7.4010101@domain.hid> <45E80CDB.1040504@domain.hid> <45E82460.1030809@domain.hid> <45E82887.8090809@domain.hid> <45E837AC.1060609@domain.hid> In-Reply-To: <45E837AC.1060609@domain.hid> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Xenomai-help@domain.hid Wolfgang Grandegger wrote: > Roland Tollenaar wrote: >>> >>> Inspect /proc/rtcan or watch the log messages. >>> >>>> Then I presume I will send a message on 1 and then see it appear on >>>> the rtcanrecv rtcan1 ? >>> >>> Yes, but with rtcan2. >> Does this not depend on the outcome of the earlier inspection of >> /proc/rtcan or is rtcan2 an educated guess? To clarify: I will be >> sending and recieving on rtcan2 in loopback mode in order to test? > > The virtual can driver will install two devices. Have you seen something > different? If you then load xeno_can_peak_dng... The devices will be > named according to order they are installation, of course. FYI, I just committed the following changes to the trunk: 2007-03-02 Wolfgang Grandegger * include/rtdm/rtcan.h: Document CAN controller modes and remove definition of SIOCGIFINDEX to avoid potential conflicts with the corresponding definition in kernel header files. * ksrc/drivers/can/sja1000/rtcan_peak_dng.c: add plug-n-play support to ensure that the parallel port device is powered on and do proper cleanup. Wolfgang.