linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kvaser Support" <support@kvaser.com>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
	Olivier Sobrie <olivier@sobrie.be>
Subject: Re: (Case 14359) Kvaser socketCAN support
Date: Wed, 23 Apr 2014 18:19:01 +0200	[thread overview]
Message-ID: <5357e7f5.c72de00a.4ba2.40ff@mx.google.com> (raw)
In-Reply-To: <CAGm1_ks40c8SGE+BuokShMmOXkGk0PO4MF67N+jhYh+DBWnp6w@mail.gmail.com>

The provided link covers chips and mentions ESD CAN Cards.  But I do not see any mention of Kvaser in the list.  So, on quick glance I thought it was a list of supported chips.

Most people who purchase will be looking for product level names.  They rarely look in depth at the chip or clock used in the product.  They just want the card to work and are trying to confirm that a particular product works with socketcan.

Best regards,

Troy
-- 
Kvaser Support
support@kvaser.com
---------------------------------------------------------------------------



-----Original Message-----
From: "Yegor Yefremov" <yegorslists@googlemail.com>
Reply-To: "Yegor Yefremov" <yegorslists@googlemail.com>
Date: Wed, 23 Apr 2014 09:48:45 +0200
To: "Kvaser Support" <support@kvaser.com>
Cc: "Oliver Hartkopp" <socketcan@hartkopp.net>, "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>, "Olivier Sobrie" <olivier@sobrie.be>
Subject: Re: (Case 14359) Kvaser socketCAN support

>Hi Troy,
>
>What about this link
>(http://elinux.org/CAN_Bus#SocketCAN_Supported_Controllers)?
>
>Linux distribution table i.e. Linux kernel version where not bad. I've
>also thought about a list of Linux distors, that maintain can-utils,
>libsocketcan etc.
>
>Yegor
>
>On Wed, Apr 23, 2014 at 9:38 AM, Kvaser Support <support@kvaser.com> wrote:
>> Looking at the provided web page and associated links, I do not see:
>> - a list of vendor supported/tested CAN hardware
>> - the Linux distribution where this support was included.
>>
>> These are two basic questions that we get concerning socketcan.
>>
>> Best regards,
>>
>> Troy
>> --
>> Kvaser Support
>> support@kvaser.com
>> ---------------------------------------------------------------------------
>>
>>
>>
>>

  reply	other threads:[~2014-04-23 16:19 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 [this message]
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
     [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=5357e7f5.c72de00a.4ba2.40ff@mx.google.com \
    --to=support@kvaser.com \
    --cc=linux-can@vger.kernel.org \
    --cc=olivier@sobrie.be \
    --cc=socketcan@hartkopp.net \
    --cc=yegorslists@googlemail.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 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).