Linux CAN drivers development
 help / color / mirror / Atom feed
From: Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be>
To: pfifre.ext@orange.com
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: J1939 + iMX6 + yocto
Date: Thu, 10 Sep 2015 13:34:19 +0200	[thread overview]
Message-ID: <20150910113419.GA13189@airbook.eia.lan> (raw)
In-Reply-To: <10825_1441878970_55F153BA_10825_1523_1_e2938c8e-30db-4942-96df-1d6a7628d355@OPEXCLILM7D.corporate.adroot.infra.ftgroup>


> Date: Thu, 10 Sep 2015 09:56:06 +0000
> 
> Hi Kurt,
> 
> I tried to patch my Kernel (3.10r0) with the j1939-v3.10 and lot of conflicts appears again.

Did you follow the steps that I explained on http://elinux.org#J1939?
It should work, unless you are not on a v3.10 branch of your repository.

> I noticed that I have also conflicts with the documentation repository in kernel. It seems to be strange, no?
> 
> If I just want to add j1939 stack, can I try this:
> 1) Add j1939 repository from your git sources in <linux kernel>/net/can/j1939
> 2) Mofidy Kconfig and Makefile in net/can to add j1939
> 3) Put the can.h from your from your git sources in <linux kernel>/include/linux/can.h
> 4) Modifiying af_can.c to :
> 	a) add these functions : can_rtl_doit, can_rtnl_dumpit, can_rtln_dump_addr, can_get_link_af_size, can_fill_link_af, can_validate_link_af, can_set_link_af
> 	b) add these structure : can_rtnl-af_ops
> 	c) Modify init_can to call rtl functions
> 5) Make a patch for Yocto with these

You can use git to show the diff between v3.10 and j1939-v3.10.

> 
> What do you think about this?
> 
> BTW, for another target, I try to get iproute2-j1939 from your github to compile for a 3.8 kernel, and the branches j1939-vX.X disappear. I found only the master branch. Is it normal?
No.
I see all branches, but that are not as many as branches in the kernel.
The iproute2 of a newer version is usable on older versions.

Kurt

  reply	other threads:[~2015-09-10 11:34 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 10:44 J1939 message length pascal
2014-12-12 11:07 ` Kurt Van Dijck
2014-12-15  8:58   ` pfifre.ext
2014-12-15  9:31     ` Kurt Van Dijck
2014-12-15  9:37       ` pfifre.ext
2015-01-16 13:31       ` Laurent Vaudoit
2015-01-19  9:13         ` Kurt Van Dijck
2015-04-27  9:22       ` pfifre.ext
2015-05-19  8:46         ` Kurt Van Dijck
2015-05-19 13:27           ` pfifre.ext
     [not found]             ` <CAA7hF3y7+j_TZ4nTak8t5Y4ejmE2fOFWxRBKJbrHLiFts_+8eg@mail.gmail.com>
2015-05-19 21:01               ` Kurt Van Dijck
2015-05-20  6:27                 ` pfifre.ext
2015-05-21 15:16                 ` pfifre.ext
2015-05-21 20:22                   ` Oliver Hartkopp
2015-05-22  6:08                     ` pfifre.ext
2015-05-19 13:55           ` pfifre.ext
2015-09-04 12:24           ` pfifre.ext
2015-09-07  0:40             ` J1939 + iMX6 + yocto Kurt Van Dijck
2015-09-07  6:31               ` pfifre.ext
2015-09-08  7:58                 ` Kurt Van Dijck
2015-09-08  9:33                   ` pfifre.ext
2015-09-08 12:32                     ` Kurt Van Dijck
2015-09-08 12:45                       ` pfifre.ext
2015-09-18  9:04                       ` pfifre.ext
2015-09-18 12:10                         ` Kurt Van Dijck
2015-09-18 12:29                           ` pfifre.ext
2015-09-19  6:34                             ` Kurt Van Dijck
2015-09-21  7:27                               ` pfifre.ext
2015-09-10  9:56                   ` pfifre.ext
2015-09-10 11:34                     ` Kurt Van Dijck [this message]
2015-09-10 13:18                       ` pfifre.ext
2015-09-10 13:30                         ` Marc Kleine-Budde
2015-09-10 15:32                           ` pfifre.ext
2015-09-11  3:49                             ` Kurt Van Dijck
2015-09-11  6:46                               ` pfifre.ext
2015-09-11  9:48                                 ` Kurt Van Dijck
2015-09-11  9:53                                   ` pfifre.ext
2015-09-15  6:54                                   ` pfifre.ext

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=20150910113419.GA13189@airbook.eia.lan \
    --to=dev.kurt@vandijck-laurijssen.be \
    --cc=linux-can@vger.kernel.org \
    --cc=pfifre.ext@orange.com \
    /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