From: Stephane Grosjean <s.grosjean@peak-system.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: linux-can Mailing List <linux-can@vger.kernel.org>
Subject: Re: [PATCH] can/peak_pci: fix FPGA potential frame loss issue
Date: Fri, 22 Jan 2016 10:10:20 +0100 [thread overview]
Message-ID: <56A1F1FC.5070402@peak-system.com> (raw)
In-Reply-To: <56A11AB2.5060200@hartkopp.net>
Hello Oliver,
At the moment, we think about how best to proceed.
We've got one tool that is able to do the update, but we want to reduce
risks at their minimum.
Keep intouch!
Regards,
Stéphane
Le 21/01/2016 18:51, Oliver Hartkopp a écrit :
> Hi Stephane,
>
> On 01/20/2016 03:33 PM, Marc Kleine-Budde wrote:
>> On 01/20/2016 03:29 PM, Stephane Grosjean wrote:
>>> [ 2200.129168] peak_pci 0000:05:01.0: Warning: FW v1.2.0 needs a
>>> workaround; update is available
>> One per hardware device is enough.
>> "Warning: FW v1.2.0 workaround active; Please update device Firmeware."
>>
>> ...and a webpage displaying this message, so that you will find it.
>> Maybe even add a link to the website in the commit message.
>>
> searching for a potential firmware update on the PEAK Website
>
> http://www.peak-system.com/Firmware.180.0.html?&L=1
>
> I did not find anything about the PCIe Hardware.
>
> Will there be a Linux tool to apply the firmware update too?
> I don't have any PCIe slots on Windows machines anymore 8-)
>
> Best regards,
> Oliver
>
--
PEAK-System Technik GmbH
Sitz der Gesellschaft Darmstadt - HRB 9183
Geschaeftsfuehrung: A.Gach, U.Wilhelm
--
next prev parent reply other threads:[~2016-01-22 9:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 11:15 [PATCH] can/peak_pci: fix FPGA potential frame loss issue Stephane Grosjean
2016-01-20 14:11 ` Marc Kleine-Budde
2016-01-20 14:29 ` Stephane Grosjean
2016-01-20 14:33 ` Marc Kleine-Budde
2016-01-21 17:51 ` Oliver Hartkopp
2016-01-22 9:10 ` Stephane Grosjean [this message]
2016-04-08 5:36 ` Oliver Hartkopp
2016-01-20 14:51 ` Andri Yngvason
2016-02-23 16:53 ` Andri Yngvason
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=56A1F1FC.5070402@peak-system.com \
--to=s.grosjean@peak-system.com \
--cc=linux-can@vger.kernel.org \
--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).