From: Wolfgang Grandegger <wg@grandegger.com>
To: "j.p.lammertink" <j.p.lammertink@kubicas.com>
Cc: linux-can@vger.kernel.org
Subject: Re: Evaluating the c_can driver for EG20T
Date: Thu, 25 Apr 2013 09:52:29 +0200 [thread overview]
Message-ID: <5178E0BD.30501@grandegger.com> (raw)
In-Reply-To: <20130425074353.D0711D8071390@bmail03.one.com>
On 04/25/2013 09:43 AM, j.p.lammertink wrote:
>
> Hi Wolfgang,
>
> < Hi Jeroen,
> <> On 04/24/2013 11:11 AM, j.p.lammertink wrote:
> <> Hi Wolfgang,
>
> <> I think I have a patch for the "Loosing CAN messages problem"
> <> See at the bottom Appendix 7 Sugested patch.
> <> I realize that this patch has a performance penalty, but I didn't dare
> <> to make more rigorous changes.
> <> I've put the patch on top of Patch 1, of the patches that you sugested (see
> <> text below)
>
> <> I'm interested in all feedback.
> < Well, we want to get rid of the pch_can driver sooner than later.
> < Therefore I would appreciate if you could test and improve the c_can
> < driver instead.
> < Wolfgang.
>
> I tried once before but I did not succeed. I probably did something
> wrong. Can you tell me how I can replace the pch_can driver by the
> c_can driver?
> We have reduced confidence in the pch_can driver and therefor we
> are also intrested in evaluating the c_can driver.
Good, anyway, could you sent me your patches pch_can.c to understand
better your lates problems.
> Note, after applying patch 1/7 to the pch_can driver, I also attemped to
> apply the patches 2/7-7/7 which mainly/only(?) effect the c_can driver.
> 1/7 went succesfull, 2/7-7/7 not. Do I still need to apply those patches?
What exact kernel disto and kernel version are you using. With that
knowledge I could provid new patches.
Wolfgang.
next prev parent reply other threads:[~2013-04-25 7:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 7:43 Evaluating the c_can driver for EG20T j.p.lammertink
2013-04-25 7:52 ` Wolfgang Grandegger [this message]
2013-04-25 8:55 ` j.p.lammertink
2013-04-25 9:23 ` Wolfgang Grandegger
2013-04-25 10:11 ` j.p.lammertink
2013-04-26 11:42 ` Wolfgang Grandegger
2013-04-25 13:25 ` Wolfgang Grandegger
-- strict thread matches above, loose matches on Subject: below --
2013-04-26 7:23 j.p.lammertink
2013-04-26 11:45 ` Wolfgang Grandegger
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=5178E0BD.30501@grandegger.com \
--to=wg@grandegger.com \
--cc=j.p.lammertink@kubicas.com \
--cc=linux-can@vger.kernel.org \
/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).