public inbox for
 help / color / mirror / Atom feed
From: John Dallaway <>
To: Gary Thomas <>
Subject: Re: CAN bus knowhow?
Date: Tue, 14 Jun 2005 14:49:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Gary and all eCos maintainers

John Dallaway wrote:

> eCosCentric already has a generic CAN I/O layer and we are keen to
> ensure that we do not end up with two incompatible CAN APIs in the eCos
> world. I will ask Nick Garnett to review Uwe Kindler's patches to assess
> the scope for merging of the two APIs. Please hold on checking anything
> in until this review is complete.

It is now clear that there is no scope for merging of the two APIs. The
eCosCentric API presents CAN peripherals as networked devices, while Uwe
Kindler's API adopts a serial I/O approach. Feel free to proceed with
the processing of Uwe Kindler's contribution.

John Dallaway
eCosCentric Limited

  reply	other threads:[~2005-06-14 14:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08 19:59 Andrew Lunn
2005-06-08 20:06 ` Gary Thomas
2005-06-09  9:55   ` John Dallaway
2005-06-14 14:49     ` John Dallaway [this message]
2005-06-14 14:58       ` Andrew Lunn

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).