linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: "j.p.lammertink" <j.p.lammertink@kubicas.com>
Cc: linux-can@vger.kernel.org
Subject: Re: Losing CAN messages with socket-CAN
Date: Thu, 04 Apr 2013 23:12:24 +0200	[thread overview]
Message-ID: <515DECB8.6090909@grandegger.com> (raw)
In-Reply-To: <20130404161608.8B2BF3E5B2D4A@bmail02.one.com>

On 04/04/2013 06:16 PM, j.p.lammertink wrote:
> Hi Wolfgang,
> 
> It looks like you can help us out. That would realy be great!
> I've collected answers to your questions and pasted them below.

...

> <>This CAN controller identifies itself (according to data sheet) as follows:
> <>    Vendor Identification Register    8086h
> <>    Device Identification Register    8818h
> <>    Revision Identification Register  00h
> <>    Class Code Register               0C0900h
> 
> < Ah, the "pch_can" driver does have known issues. End of last year I sent
> < some patches to improve the "pch_can" or, even better, make the "c_can"
> < driver work on the EG20T as well. See:
> 
> <   http://marc.info/?l=linux-can&m=135531975013055&w=2
> 
> < Are you able to build and use a recent mainline kernel? I need to figure
> < out how to help you best.
> 
> Currently a colleage of mine is attempting to build the kernel (to be able to
> apply patches to solve a display issue). I expect he will succeed one of these
> days.
> Wouldn't it be simplest just to use the latest sources of this driver?

These patches are not yet mainline because they do not fix all issues. I
do not have a system at hand and therefore somebody else needs to take
care. We actually want to drop the pch_can driver in favor of an updated
c_can driver. If you go over the patch series I pointed out you will get
more information. Anyway, we got positive feedback especially with the
c_can driver for the EG20T.

> Can you tell me which sources I should look for? (Probably I've downloaded them
> already, but I wish to replace only the files that make the difference)

I think that patch 1/7 of the series may already fix your TX problems:

  http://marc.info/?l=linux-can&m=135526076021515&w=2
´
If you apply the remaining patches, you can select the "c_can_pci"
driver. If you get trouble with these patches I need to adapt them to a
more recent kernel version.

Wolfgang.

  reply	other threads:[~2013-04-04 21:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 16:16 Losing CAN messages with socket-CAN j.p.lammertink
2013-04-04 21:12 ` Wolfgang Grandegger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-04-24  9:11 j.p.lammertink
2013-04-24 10:59 ` Wolfgang Grandegger
2013-04-18 10:34 j.p.lammertink
2013-04-08 14:43 j.p.lammertink
2013-04-05 13:31 j.p.lammertink
2013-04-07 13:13 ` Wolfgang Grandegger
2013-04-07 21:05   ` Kurt Van Dijck
2013-04-04 14:44 j.p.lammertink
2013-04-04 15:11 ` 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=515DECB8.6090909@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).