linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: [ANNOUNCEMENT] CAN (FD) and ISO 16765-2:2015 at Embedded World 2015
Date: Mon, 23 Feb 2015 12:44:19 +0100	[thread overview]
Message-ID: <54EB1293.6080408@hartkopp.net> (raw)

Hi all,

just in the case you are able to visit the Embedded World the next three days:

The CAN in Automation Newsletter http://www.can-newsletter.org/ has an
overview of exhibitors with CAN(FD) context and booth numbers at the fair.

See PDF at:

http://v2.can-newsletter.org/uploads/media/raw/63b57b25e4653f63eda89eb935be4a15.pdf

At the PEAK System booth SocketCAN with CAN FD will be shown (can-utils) and
a live performance demonstration for ISO-TP over CAN FD (ISO 16765-2:2015).

I'll be at Nuremberg tomorrow. Hope to get to see some of you there.

Regards,
Oliver

                 reply	other threads:[~2015-02-23 11:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=54EB1293.6080408@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --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).