From: "Rost, Martin" <Martin.Rost@tonfunk.de>
To: Francesco Rocca <roccafrancesco@gmail.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: RE: mcp251x issue
Date: Mon, 19 May 2014 05:06:58 +0000 [thread overview]
Message-ID: <2E9F00CBB66AB544A1ACDC59627518BA0DC9502D@mailserver> (raw)
In-Reply-To: <CADZ8cjmOw+Ns7Zf7PDqpFwRRRAQn19Go8G2iPAJuQYnE9oSGAw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1577 bytes --]
Hello Francesco.
The patch went to the official mailing list; you should have seen it.
There was also some discussion about it, in the current state it probably won't make it into an official code repository.
http://thread.gmane.org/gmane.linux.can/5796
Please note that I am only one single user of the mcp2515 and can only comment on the problem I have been seeing.
There are, however, numerous other people using the mcp2515 on the official linux-can list, your chance of getting a helpful response is much higher there.
http://vger.kernel.org/vger-lists.html#linux-can
Mit freundlichen Gruessen
Best regards
Martin Rost
> -----Original Message-----
> From: Francesco Rocca [mailto:roccafrancesco@gmail.com]
> Sent: Friday, May 16, 2014 3:35 PM
> To: Rost, Martin
> Subject: Re: mcp251x issue
>
> Hello Martin
>
> we continue to have problem in our side with can communication;
> the problem seem occurs eralier when also trasmit socket on same can port
> is activated; the bus once off doesn't recovery as expected.
>
> How do you suggest? i wrote that you are preparing a patch! can we have
> notice about it?
>
> your help wiil be very appreciate!
> Thanks in advance!
>
> Francesco
>
>
>
> 2014-05-08 8:17 GMT+02:00 Rost, Martin <Martin.Rost@tonfunk.de>:
>
>
> Hi,
>
> this is exactly the problem I've been seeing.
> For reference: see http://article.gmane.org/gmane.linux.can/5319
>
> I'll prepare a patch from my code.
>
> Mit freundlichen Gruessen
> Best regards
>
> Martin Rost
>
>
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2015 bytes --]
prev parent reply other threads:[~2014-05-19 5:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADZ8cjkTH5=iYz1fD2Pua2nMZns1xinA+gEWaDLHqMM=WxR62g@mail.gmail.com>
[not found] ` <5367BDDC.70709@hartkopp.net>
[not found] ` <CADZ8cjnEUT6r8EUxZdKbnuVADQ3bCbYJ1cU5evXxJrorJmNK3g@mail.gmail.com>
2014-05-07 15:52 ` mcp251x issue Oliver Hartkopp
2014-05-08 6:17 ` Rost, Martin
[not found] ` <CADZ8cjmOw+Ns7Zf7PDqpFwRRRAQn19Go8G2iPAJuQYnE9oSGAw@mail.gmail.com>
2014-05-19 5:06 ` Rost, Martin [this message]
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=2E9F00CBB66AB544A1ACDC59627518BA0DC9502D@mailserver \
--to=martin.rost@tonfunk.de \
--cc=linux-can@vger.kernel.org \
--cc=roccafrancesco@gmail.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