All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yang <wang701@purdue.edu>
To: Alex Layton <alex@layton.in>, linux-can <linux-can@vger.kernel.org>
Subject: Re: Re: can-j1939 API
Date: Tue, 10 Nov 2015 16:58:07 -0500	[thread overview]
Message-ID: <5642686F.5020708@purdue.edu> (raw)
In-Reply-To: <20151023111430.GB22388@airbook.eia.lan>

On 10/23/2015 07:14 AM, Kurt Van Dijck wrote:

> I'll do the necessary modifications.
> This has become a rather low-priority task nowadays, although I think
> there is a momentum to make progress now.

I am working with Alex, the author of 
https://github.com/ISOBlue/isoblue-software on a project that uses 
j1939. With Alex's module, we wrote another program to receive messages 
and get the PGN out of each message.

After looking through this thread, it seems like your module could do 
the same thing and it looks promising that your module will be added 
into the main linux kernel. You mentioned that there are things you need 
to fix and change. I'm currently looking into writing a JNI wrapper for 
the j1939 module you have. My question is: as you make modifications to 
the API, how much will change? I can't/don't want to write the JNI 
wrapper if the code will keep changing significantly.

  parent reply	other threads:[~2015-11-10 22:05 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <linux-can/can-utils/pull/7@github.com>
2015-09-28  6:53 ` [can-utils] J1939 v6 (#7) Marc Kleine-Budde
2015-09-29 12:15   ` Kurt Van Dijck
2015-09-30 15:26     ` Aaron Clarke
2015-09-30 23:38       ` Kurt Van Dijck
     [not found] ` <linux-can/can-utils/pull/7/c144149208@github.com>
2015-09-29 18:46   ` Marc Kleine-Budde
2015-09-29 19:49     ` can-j1939 API Kurt Van Dijck
2015-09-29 20:10       ` Austin Schuh
2015-10-15 22:04       ` Alex Layton
2015-10-16 19:36         ` Patrick Menschel
2015-10-18  2:42           ` Kurt Van Dijck
2015-10-19  3:41             ` Patrick Menschel
2015-10-19  6:07               ` Oliver Hartkopp
2015-10-19  9:52                 ` Kurt Van Dijck
2015-10-19 16:53                   ` Alex Layton
2015-10-19 20:57                     ` Kurt Van Dijck
2015-10-19 21:31                       ` Kurt Van Dijck
2015-10-22 16:39                       ` Alex Layton
2015-10-18  2:32         ` Kurt Van Dijck
2015-10-19 16:53           ` Alex Layton
2015-10-19 20:44             ` Kurt Van Dijck
2015-10-22 16:39               ` Alex Layton
2015-10-23 11:14                 ` Kurt Van Dijck
2015-10-29 19:33                   ` Oliver Hartkopp
2015-10-29 23:38                     ` Kurt Van Dijck
2015-11-02 12:14                       ` Oliver Hartkopp
2015-11-02 12:29                         ` Kurt Van Dijck
2015-11-02 13:18                           ` Oliver Hartkopp
2015-11-11 19:48                             ` Kurt Van Dijck
2015-11-10 21:58                   ` Yang [this message]
2015-11-11 18:49                     ` Kurt Van Dijck
2015-11-17  6:01                       ` Yang Wang
2015-11-17  8:43                         ` 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=5642686F.5020708@purdue.edu \
    --to=wang701@purdue.edu \
    --cc=alex@layton.in \
    --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 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.