From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Kvaser Support <support@kvaser.com>,
Yegor Yefremov <yegorslists@googlemail.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Olivier Sobrie <olivier@sobrie.be>
Subject: SocketCAN Supported Controllers information updates
Date: Fri, 25 Apr 2014 22:38:08 +0200 [thread overview]
Message-ID: <535AC7B0.3020101@hartkopp.net> (raw)
In-Reply-To: <53598c53.02608c0a.aea0.4bbe@mx.google.com>
Hello Troy,
I just added the USB based drivers for Kvaser and PEAK.
This is a pretty boring and laborious work ... e.g. to retrieve the
information from product websites (URLs) or the Linux version.
Please check if
http://elinux.org/CAN_Bus#SocketCAN_Supported_Controllers
looks ok from the Kvaser side.
When not all of you want to have a wiki account, you may send the wiki code
lines for integration into the wiki on this list, so that Yegor or me can
just copy/paste the line into the wiki.
E.g. for the Kvaser USB this was:
|[http://www.kvaser.com/ Kvaser] || [http://www.kvaser.com/products-services/our-products/ Leaf] || kvaser_usb || (unknown) || CONFIG_CAN_KVASER_USB || 3.8 || supports USB Leaf / Memorator / Blackbird / R (see detailed USB device IDs in kvaser_usb.c)
Best regards,
Oliver
On 25.04.2014 00:12, Kvaser Support wrote:
> Looks great!
>
> Just missing Kvaser from the list. Do you need anything from me to add Kvaser to the table? Web page links?
>
> Best regards,
>
> Troy
>
next prev parent reply other threads:[~2014-04-25 20: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
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 ` Oliver Hartkopp [this message]
2014-04-28 0:25 ` (Case 14383) SocketCAN Supported Controllers information updates 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=535AC7B0.3020101@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=olivier@sobrie.be \
--cc=support@kvaser.com \
--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).