All of lore.kernel.org
 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 09:38:22 +0200	[thread overview]
Message-ID: <53576dee.0770e00a.185d.04ca@mx.google.com> (raw)
In-Reply-To: <CAGm1_kuvZx7uoGTYbwDkWh1NAHNxUeDpn=2nnojvaOH17eh7pA@mail.gmail.com>

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
---------------------------------------------------------------------------



-----Original Message-----
From: "Yegor Yefremov" <yegorslists@googlemail.com>
Reply-To: "Yegor Yefremov" <yegorslists@googlemail.com>
Date: Tue, 22 Apr 2014 07:54:31 +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

>On Tue, Apr 22, 2014 at 2:40 AM, Kvaser Support <support@kvaser.com> wrote:
>> Thanks for the information Oliver.
>>
>> Is there a good location for us to point to that would list the current hardware supported by Socketcan and the version of Linux needed for that support?  A site that is kept up to date?
>>
>> I am looking for something that we could put in a FAQ on our website that point people using socketcan in the correct direction.
>
>Try http://elinux.org/CAN_Bus
>
>The wiki could definitely get more care, but from time to time we update it.
>
>Regards,
>Yegor
>
>> ---------------------------------------------------------------------------
>>
>>
>>
>>

  reply	other threads:[~2014-04-23  7:38 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 [this message]
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
     [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=53576dee.0770e00a.185d.04ca@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 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.