linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: "Smith, Christopher - 0999 - MITLL" <chris.smith@ll.mit.edu>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
	"Adams, Shawn - 0999 - MITLL" <shawn.adams@ll.mit.edu>
Subject: Re: Kvaser socketCAN support
Date: Thu, 01 May 2014 10:56:27 +0200	[thread overview]
Message-ID: <53620C3B.9080402@hartkopp.net> (raw)
In-Reply-To: <r049e3q3UHfiSQJ.RZmta@smtp.rzone.de>

Christopher,

On 30.04.2014 19:41, Smith, Christopher - 0999 - MITLL wrote:
> Oliver, 
> 
> After digging around a bit more it seems like I'm having the same problem
> that was mentioned here:
> 
> http://comments.gmane.org/gmane.network.socketcan.user/1445

What exactly do you refer to from this thread?

> 
> can0 never comes up

???

Does can0 apprear in dmesg or in /proc/net/dev

??

Pls post the dmesg output of the relevant lines here.
And the lsusb output.

> even though dmesg seems to indicate that other
> initialization has gone smoothly.  Is this a problem where one type of
> kvaser hardware is working but perhaps another variant does not?

I'm still not the right person to ask these kind of questions - that's why I
tried to forward your request to Olivier (not Oliver) last time (see below in
this mail).

The only I know about the Kvaser driver and it's supported hardware is what
you can determine yourself from the Kvasers Kconfig section or the driver itself:

http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/drivers/net/can/usb/Kconfig?h=linux-3.14.y#n16

http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/drivers/net/can/usb/kvaser_usb.c?h=linux-3.14.y#n33

Regards,
Oliver


  If so
> maybe more information about what was working well would allow me to use
> similar hardware.
> 
> Thanks,
> 
> Chris
> 
> -----Original Message-----
> From: Oliver Hartkopp [mailto:socketcan@hartkopp.net] 
> Sent: Monday, April 21, 2014 1:49 PM
> To: Smith, Christopher - 0999 - MITLL
> Cc: Kvaser Support (support@kvaser.com); linux-can@vger.kernel.org; Olivier
> Sobrie
> Subject: Re: Kvaser socketCAN support
> 
> Hello Christopher,
> 
> the Kvaser Leaf USB driver has been contributed by Olivier Sobrie (see CC).
> 
> See log messages of the driver in the Linux Mainline repository:
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/n
> et/can/usb/kvaser_usb.c
> 
> The initial support was added at 2012-11-27 and emerged in Linux 3.8.
> 
> Regards,
> Oliver
> 
> ps. feel free to ask this kind of questions on the linux-can mailing list
> which I added in CC. Tnx
> 
> 
> On 17.04.2014 03:31, Smith, Christopher - 0999 - MITLL wrote:
>> Hi, I was just looking to get confirmation and a few points for 
>> getting the initial install figured out.
>>
>>  
>>
>> I have a kvaser leaf device that I'd like to use with socketCAN.  Is 
>> this in fact supported?
>>
>>  
>>
>> I noticed the general process for setting up socketCAN documented on 
>> wikipedia <http://en.wikipedia.org/wiki/SocketCAN>.  When I issue the
> following command:
>>
>>  
>>
>> ip link add dev vcan0 type vcan
>>
>>  
>>
>> What do I replace vcan0 with?  I've tried can0 with no luck.  Is there 
>> a way to check which devices are registered?  I'm not entirely sure 
>> that when I plugged in the USB device the proper drivers were 
>> recognized.  I may need some of the lower level drivers distributed by
> Kvaser.
>>
>>  
>>
>> Thank you,
>>
>>  
>>
>> Chris
>>
>>  
>>
>> -----Original Message-----
>> From: Kvaser Support [mailto:support@kvaser.com]
>> Sent: Monday, April 14, 2014 3:24 PM
>> To: Smith, Christopher - 0999 - MITLL
>> Subject: Re: (Case 14217) Linux driver support
>>
>>  
>>
>> Did the response below answer your questions?
>>
>>  
>>
>> Or do you need more information?
>>
>>  
>>
>> Best regards,
>>
>>  
>>
>> Troy
>>
>> --
>>
>> Kvaser Support
>>
>> support@kvaser.com <mailto:support@kvaser.com>
>>
>> ----------------------------------------------------------------------
>> -----
>>
>>  
>>
>>  
>>
>>  
>>
>> -----Original Message-----
>>
>> From: "Kvaser Support" <support@kvaser.com 
>> <mailto:support@kvaser.com>>
>>
>> Reply-To: "Kvaser Support" <support@kvaser.com 
>> <mailto:support@kvaser.com>>
>>
>> Date: Mon, 31 Mar 2014 22:29:00 +02:00
>>
>> To: "Smith, Christopher - 0999 - MITLL" <chris.smith@ll.mit.edu 
>> <mailto:chris.smith@ll.mit.edu>>
>>
>> Subject: Re: (Case 14217) Linux driver support
>>
>>  
>>
>>> To our knowledge, support for the Leaf family was added to socketcan 
>>> by
>> Oliver Harkopp in 2012.
>>
>>>
>>
>>> I tried to perform a google search to determine which version of Linux 
>>> this
>> has been included in without good results.
>>
>>>
>>
>>> I hope the socketcan community can point you to the version that 
>>> includes
>> this patch.
>>
>>>
>>
>>> Best regards,
>>
>>>
>>
>>> Troy
>>
>>> --
>>
>>> Kvaser Support
>>
>>> support@kvaser.com <mailto:support@kvaser.com>
>>
>>> ----------------------------------------------------------------------
>>> -----
>>

  parent reply	other threads:[~2014-05-01  8:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f0331cq3H1VPknv.RZmta@smtp.rzone.de>
2014-04-21 17:48 ` Kvaser socketCAN support Oliver Hartkopp
2014-04-22  0:40   ` (Case 14359) " Kvaser Support
2014-04-22  5:54     ` Yegor Yefremov
2014-04-23  7:38       ` Kvaser Support
2014-04-23  7:48         ` Yegor Yefremov
2014-04-23 16:19           ` Kvaser Support
2014-04-24  7:46             ` Yegor Yefremov
2014-04-24  9:19               ` Marc Kleine-Budde
2014-04-24 12:01                 ` Oliver Hartkopp
2014-04-24 12:06                   ` Marc Kleine-Budde
2014-04-24 12:34                     ` Yegor Yefremov
2014-04-24 18:56                       ` Oliver Hartkopp
2014-04-24 19:29                         ` Yegor Yefremov
2014-04-24 22:12                           ` Kvaser Support
2014-04-25 20:38                             ` SocketCAN Supported Controllers information updates Oliver Hartkopp
2014-04-28  0:25                               ` (Case 14383) " Kvaser Support
2014-04-27 17:41                         ` elinux wiki Kurt Van Dijck
     [not found]   ` <r049e3q3UHfiSQJ.RZmta@smtp.rzone.de>
2014-05-01  8:56     ` Oliver Hartkopp [this message]
     [not found]       ` <R0595dq41EVg2BS.RZmta@smtp.rzone.de>
2014-05-01 16:24         ` Kvaser socketCAN support Oliver Hartkopp
     [not found]           ` <6073ccq41HkW3ar.RZmta@smtp.rzone.de>
2014-05-01 18:46             ` Oliver Hartkopp
     [not found]           ` <53628879.751e8c0a.6be4.ffffc061SMTPIN_ADDED_MISSING@mx.google.com>
2014-05-01 20:46             ` Olivier Sobrie
     [not found]               ` <5363a95a.e3208c0a.bc54.574dSMTPIN_ADDED_MISSING@mx.google.com>
2014-05-03 13:18                 ` Olivier Sobrie
2014-05-04  6:00                   ` (Case 14420) " Kvaser Support
2014-05-04 20:14                     ` Olivier Sobrie
2014-05-04 21:23                       ` Kvaser Support
2014-05-11 20:34                 ` Olivier Sobrie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53620C3B.9080402@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=chris.smith@ll.mit.edu \
    --cc=linux-can@vger.kernel.org \
    --cc=shawn.adams@ll.mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).