All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olivier Sobrie <olivier@sobrie.be>
To: "Smith, Christopher - 0999 - MITLL" <chris.smith@ll.mit.edu>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
	"Adams, Shawn - 0999 - MITLL" <shawn.adams@ll.mit.edu>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
	"Kvaser Support (support@kvaser.com)" <support@kvaser.com>
Subject: Re: Kvaser socketCAN support
Date: Thu, 1 May 2014 22:46:09 +0200	[thread overview]
Message-ID: <20140501204609.GA25569@thinkoso.home> (raw)
In-Reply-To: <53628879.751e8c0a.6be4.ffffc061SMTPIN_ADDED_MISSING@mx.google.com>

Hi Christopher,

On Thu, May 01, 2014 at 01:46:25PM -0400, Smith, Christopher - 0999 - MITLL wrote:
> Oliver, thank you for taking a look at this.  I'm guessing that other
> testing you did used that same USB command and did not have any problem?  If
> so perhaps it's an issue of firmware on our device or perhaps a slightly
> different version of hardware.  The device is the Kvaser Memorator with
> firmware 2.2.600.

I just plugged a Kvaser Memorator Professionnal and don't see any probe
error. My device is running firmware v2.0.50.

> > root@localhost:~# lsusb
> > Bus 001 Device 002: ID 0bfd:0017 Kvaser AB
> 
> Looks like a
> #define USB_LEAF_PRO_LIN_PRODUCT_ID	17
> 
> > root@localhost:~# dmesg |grep -i can
> > [    4.231784] CAN device driver interface
> > [    5.233369] kvaser_usb 1-1:1.0: Cannot get software infos, error -110

A probe problem has been fixed for this hardware. See the following commit
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a90f13b24fb40d02d11496cce6a10ae8d4b319b2
This problem is present in version 3.8.
The patch has been included in linux 3.12 and backported in stable branches
of v3.10 and v3.11. So please upgrade :-)

Let us know if it solves your problem.

Kind regards,

-- 
Olivier

  parent reply	other threads:[~2014-05-01 20:45 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     ` Kvaser socketCAN support Oliver Hartkopp
     [not found]       ` <R0595dq41EVg2BS.RZmta@smtp.rzone.de>
2014-05-01 16:24         ` 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 [this message]
     [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=20140501204609.GA25569@thinkoso.home \
    --to=olivier@sobrie.be \
    --cc=chris.smith@ll.mit.edu \
    --cc=linux-can@vger.kernel.org \
    --cc=shawn.adams@ll.mit.edu \
    --cc=socketcan@hartkopp.net \
    --cc=support@kvaser.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.