linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <kiszka@rts.uni-hannover.de>
To: The Linux Socket CAN Framework <socket-can@pengutronix.de>
Cc: David Jander <david.jander@protonic.nl>,
	urs.thuermann@volkswagen.de, oliver.hartkopp@volkswagen.de,
	linuxppc-embedded@ozlabs.org
Subject: Re: [Socket-can] Re: Which CAN driver to port to for PPC
Date: Thu, 29 Dec 2005 16:12:20 +0100	[thread overview]
Message-ID: <43B3FCD4.2020409@rts.uni-hannover.de> (raw)
In-Reply-To: <20051229134355.GH19375@pengutronix.de>

[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]

Robert Schwebel wrote:
> ...
> 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.
> 

Beyond the outstanding comparably minor API adjustments, we furthermore
discussed first ideas how to define the lowest interface, i.e. the CAN
network device layer. That should be done in a way which makes porting
CAN low-level drivers between the standard kernel and a real-time Linux
CAN stack trivial. That's a unique chance (compared to the situation of
RTnet e.g.), so we should take it.

This real-time stack is to be derived from the RT-SJA1000 driver
Wolfgang pointed at. It is already based on an abstraction layer (RTDM)
that makes it portable across many of the various RT-Linux variant. So
far this includes support for Xenomai and RTAI, RTLinux/GPL is planning
to adopt RTDM as well. This means we could end up with portable CAN
applications and drivers, RT and non-RT!

As Robert said, it "just" requires some resources for implementing
this... ;)

Jan

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2005-12-29 15:28 UTC|newest]

Thread overview: 15+ 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
2005-12-29 15:12         ` Jan Kiszka [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2005-12-30 18:00 AW: [Socket-can] " Hartkopp, Oliver (K-GEFE/E)
2005-12-30 21:10 ` Robert Schwebel

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=43B3FCD4.2020409@rts.uni-hannover.de \
    --to=kiszka@rts.uni-hannover.de \
    --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).