linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Andrey Volkov <avolkov@varma-el.com>
Cc: David Jander <david.jander@protonic.nl>,
	urs.thuermann@volkswagen.de, socket-can@pengutronix.de,
	oliver.hartkopp@volkswagen.de, linuxppc-embedded@ozlabs.org
Subject: Re: Which CAN driver to port to for PPC
Date: Thu, 29 Dec 2005 14:43:55 +0100	[thread overview]
Message-ID: <20051229134355.GH19375@pengutronix.de> (raw)
In-Reply-To: <43B2A902.3090008@varma-el.com>

Hi, 

On Wed, Dec 28, 2005 at 06:02:26PM +0300, Andrey Volkov wrote:
> Robert Schwebel et al have worked socket based CAN (i.e. implement CAN
> as _net_ dev, not as char), as consequence you will not have problem
> with major/minor numbers, duplicated code in drivers for different
> chips, could share CAN dev between diff processes _without_ misc.
> third party shared libraies, stacked CAN protocols (CANopen/NMEA2000
> could be abstract kernel module)... But currently it is not open for
> everyone (due to beta status, AFAIK)
> 
> Alessandro, please check Pengutronix work first, may be it will be
> helpfull to you to
>
> [...]
>
> P.S. Robert, when I check last time, it was mature enogh, so may be time
> to open mail-list and svn?

The socket-can stuff is mature enouth to have been used in some projects
at Pengutronix.

In december, we have made a synchronisation meeting with the VW people
who made the initial port for 2.4; they are more focussed on having
higher level transport protocols ontop of the "raw" socket interface we
currently use. During that process we have reviewed the user interface
with regard to their use cases, so it will have to be changed a little
bit before we have something which is in a state to be posted on lkml.

Unfortunately we have no commercial project behind the infrastructure
work, so it's priority is lower than it should be to really drive things
forward (paying customers have a higher priority than community work). 

Robert
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hannoversche Str. 2, 31134 Hildesheim, Germany
   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9

  reply	other threads:[~2005-12-29 14:07 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 15:02     ` Andrey Volkov
2005-12-29 13:43       ` Robert Schwebel [this message]
2005-12-29 15:12         ` [Socket-can] " Jan Kiszka
2005-12-28 15:07     ` Alessandro Rubini
2005-12-29 12:17       ` Wolfgang Grandegger
2005-12-29 16:28         ` David Jander
2005-12-28 13:19   ` Alessandro Rubini
2005-12-28 15:05     ` David Jander
2005-12-28 10:44 ` Wolfgang Grandegger
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=20051229134355.GH19375@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=avolkov@varma-el.com \
    --cc=david.jander@protonic.nl \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=oliver.hartkopp@volkswagen.de \
    --cc=socket-can@pengutronix.de \
    --cc=urs.thuermann@volkswagen.de \
    /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).