All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: David Jander <david.jander@protonic.nl>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Which CAN driver to port to for PPC
Date: Wed, 28 Dec 2005 11:44:49 +0100	[thread overview]
Message-ID: <43B26CA1.4040700@grandegger.com> (raw)
In-Reply-To: <200512271730.28563.david.jander@protonic.nl>

David Jander wrote:
> Hi,
> 
> We have developed CAN hardware based on the Philips SJA1000 controller hooked 
> to a MPC8xx based processor board. Now we want to write driver support for 
> it. My first try was lincan-0.3.1, which seemed quite well written at first 
> glance. Porting was easy too, and the driver works fine on our board with the 
> latest kernel (2.6.14).
> But.... this driver lacks a proper way of checking the status of the CAN 
> controller from userspace :-( Not that nice after all!
> 
> Then I see on the DENX website, mention of Rubini's OCAN (mostly useless to 
> us), and Peak's PCAN drivers (there is a port for MPC5200 on DENX's site). No 
> word about lincan, though.

We have looked for "free" CAN software/drivers for Linux already some 
time ago, especially for embedded PowerPC processors. There are various 
implementations out there, but only a few of them are "alive". A natural 
choice for the SJA1000 seems to be the CAN driver from Peak Systems (see
http://www.peak-system.com/linux/index.htm). It already supports 2.6 and 
seems to be well maintained. Porting it to your MPC 8xx bases hardware 
should not be to much effort. The OCAN driver is for the i82527. It's a 
good choice if you use that CAN controller but porting to the SJA1000 
might not be straight-forward as the API uses details of the chips hardware.

> 
> The reason I suppose is, someone already figured out that lincan is not a good 
> choice for whatever reason (status reportability ??), right?

I never tried lincan.

> Before beginning to re-invent wheels and re-discover known problems in certain 
> CAN driver architectures, could someone please point me to the right place to 
> start looking for answers (if that place exists) or just give the answer, 
> opinion or experience with one of PeakCAN, lincan, can4linux, etc...?
> 
> I am again puzzeled about which way to go.

AFAIK, there is no _generic_ embedded CAN driver available which even 
supports real-time extensions.

Wolfgang.

> Thanks for any advice,
> 

  parent reply	other threads:[~2005-12-28 10:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-27 16:30 Which CAN driver to port to for PPC David Jander
2005-12-27 21:49 ` Alessandro Rubini
2005-12-28  9:00   ` David Jander
2005-12-28 13:19     ` Alessandro Rubini
2005-12-28 15:05       ` David Jander
2005-12-28 15:02     ` Andrey Volkov
2005-12-28 15:07       ` Alessandro Rubini
2005-12-29 12:17         ` Wolfgang Grandegger
2005-12-29 16:28           ` David Jander
2005-12-29 13:43       ` Robert Schwebel
2005-12-29 15:12         ` [Socket-can] " Jan Kiszka
2005-12-28 10:44 ` Wolfgang Grandegger [this message]
2005-12-28 12:02   ` David Jander
2005-12-29 11:53     ` 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=43B26CA1.4040700@grandegger.com \
    --to=wg@grandegger.com \
    --cc=david.jander@protonic.nl \
    --cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.