All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kurt Van Dijck <kurt.van.dijck@eia.be>
To: Wolfgang Wagner <wutz@unterderbruecke.de>
Cc: linux-can@vger.kernel.org
Subject: Re: using can-j1939
Date: Thu, 1 Dec 2011 14:36:52 +0100	[thread overview]
Message-ID: <20111201133652.GC321@e-circ.dyndns.org> (raw)
In-Reply-To: <20111201115256.GB321@e-circ.dyndns.org>

Wolfgang,

> Did you read Documentation/networking/can/j1939.txt from the can-j1939-modules?
In order to not overload you too much, can you (high-level) describe what
you're about to do?
* using dynamic address claiming vs. static addresses
* writing own programs vs. using some predefined cansend/candump.
* sending & receiving vs. receive only.
....

Kind regards,
Kurt Van Dijck

  reply	other threads:[~2011-12-01 13:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20111201105434.214940@gmx.net>
2011-12-01 11:52 ` using can-j1939 Kurt Van Dijck
2011-12-01 13:36   ` Kurt Van Dijck [this message]
2011-12-02  9:05   ` Oliver Hartkopp
2011-12-13 15:51 backporting can & can-j1939 Kurt Van Dijck
2011-12-14 13:29 ` Wolfgang
2011-12-14 15:43   ` Kurt Van Dijck
2011-12-14 18:19     ` Wolfgang
2011-12-14 20:42       ` Using " Kurt Van Dijck
2011-12-15  8:35         ` Wolfgang
2011-12-15  9:20           ` Cross-compiling iproute2-j1939 Kurt Van Dijck
2011-12-15 11:24             ` Wolfgang
2011-12-15 12:04               ` replacing iproute2 & can-utils with j1939 variants Kurt Van Dijck
2011-12-15 13:43                 ` Wolfgang
2011-12-15 14:00                   ` using can-j1939 Kurt Van Dijck
2011-12-15 14:49                     ` Wolfgang
2011-12-15 15:06                       ` Kurt Van Dijck
2011-12-15 15:16                         ` Wolfgang
2011-12-15 15:50                           ` Kurt Van Dijck
2011-12-15 16:17                             ` Wolfgang
2011-12-16  8:37                       ` Kurt Van Dijck
2011-12-16  9:00                         ` Wolfgang
2011-12-16  9:33                           ` Kurt Van Dijck
2011-12-16 14:29                             ` Wolfgang
2011-12-17 19:20                               ` Kurt Van Dijck
2011-12-20 10:35                                 ` API calls Wolfgang
2011-12-20 11:00                                   ` Kurt Van Dijck
2011-12-20 14:49                                     ` Wolfgang
2011-12-20 15:05                                       ` Kurt Van Dijck
2011-12-20 15:43                                         ` Wolfgang
2011-12-20 16:32                                           ` Kurt Van Dijck
2011-12-21 10:46                                             ` Wolfgang
2011-12-21 13:43                                               ` using can-j1939 Kurt Van Dijck
2011-12-21 15:11                                                 ` Wolfgang
2011-12-21 15:53                                                   ` Kurt Van Dijck
2011-12-22 13:06                                                     ` Wolfgang
2011-12-23 11:04                                                       ` Kurt Van Dijck
2011-12-28 10:49                                                         ` Wolfgang
2012-01-04  9:47                                                           ` Kurt Van Dijck

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=20111201133652.GC321@e-circ.dyndns.org \
    --to=kurt.van.dijck@eia.be \
    --cc=linux-can@vger.kernel.org \
    --cc=wutz@unterderbruecke.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 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.