From: "Kvaser Support" <support@kvaser.com>
To: Olivier Sobrie <olivier@sobrie.be>
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>,
"Smith, Christopher - 0999 - MITLL" <chris.smith@ll.mit.edu>
Subject: Re: (Case 14420) Kvaser socketCAN support
Date: Sun, 04 May 2014 23:23:02 +0200 [thread overview]
Message-ID: <5366afb6.077ee00a.59c9.11fa@mx.google.com> (raw)
In-Reply-To: <20140504201458.GA27956@thinkoso.home>
Correct. You will need to use a Windows machine to perform the firmware upgrade.
Best regards,
Troy
--
Kvaser Support
support@kvaser.com
---------------------------------------------------------------------------
-----Original Message-----
From: "Olivier Sobrie" <olivier@sobrie.be>
Reply-To: "Olivier Sobrie" <olivier@sobrie.be>
Date: Sun, 4 May 2014 22:14:58 +0200
To: "Kvaser Support" <support@kvaser.com>
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>, "Smith, Christopher - 0999 - MITLL" <chris.smith@ll.mit.edu>
Subject: Re: (Case 14420) Kvaser socketCAN support
>Hi Jerry,
>
>On Sun, May 04, 2014 at 08:00:57AM +0200, Kvaser Support wrote:
>> Hi guys,
>>
>> Some, but not all, versions of older firmware are available on the download page of the website, just click the Older versions link on the specific download. If you need another version than available, just let me know and I'll post it.
>
>Ok thanks.
>I assume it is still not possible to upgrade the firmware from a Linux
>machine?
>
>Kr,
>
>Olivier
next prev parent reply other threads:[~2014-05-04 21:23 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
[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 [this message]
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=5366afb6.077ee00a.59c9.11fa@mx.google.com \
--to=support@kvaser.com \
--cc=chris.smith@ll.mit.edu \
--cc=linux-can@vger.kernel.org \
--cc=olivier@sobrie.be \
--cc=shawn.adams@ll.mit.edu \
--cc=socketcan@hartkopp.net \
/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).