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: Tue, 8 Sep 2015 09:58:00 +0200 [thread overview]
Message-ID: <20150908075800.GA864@airbook.eia.lan> (raw)
In-Reply-To: <12979_1441607513_55ED2F59_12979_6_1_F1366246CF364C42B98553900CE0C5CB089DBBE6@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Hi Pascal,
I got back to my PC now.
I see how the j1939-v3.10 branch dissapeared. I had pushed it
to gitorious.org, which is obsolete now, thinking that I had pushed it
to github. I set that right just now.
> Which platform do you use?
We have a custom iMX6 platform (in-house developed), with the core
similar to sabre-lite from Boundary Devices (They have renamed that
board now). Our board has 2 SJA1000 chips added.
I also updated iproute2-j1939, to a version that is equal to what yocto
is using now. This was less effort than choosing a different version
of iproute2 in yocto (to me).
Kind regards,
Kurt
--- Original message ---
> Date: Mon, 7 Sep 2015 06:31:47 +0000
> From: pfifre.ext@orange.com
> To: Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be>
> CC: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
> Subject: RE: J1939 + iMX6 + yocto
>
> Hi Kurt,
>
> Glad to know that you already work on the same feature.
>
> Which platform do you use?
> I'm working now on the Digi ConnectCore 6.
>
> I'm wating on Tuesday to get your 3.10 branch and test it on my side.
>
> Thanks a lot for your help!
>
> Pascal
>
>
> -----Message d'origine-----
> De : Kurt Van Dijck [mailto:dev.kurt@vandijck-laurijssen.be]
> Envoyé : lundi 7 septembre 2015 02:40
> À : FIFRE Pascal Ext IMT/OLPS
> Cc : linux-can@vger.kernel.org
> Objet : RE: J1939 + iMX6 + yocto
>
> Hi,
>
>
> On 4 September 2015 14:24:15 CEST, pfifre.ext@orange.com wrote:
> >Hi Kurt,
> >
> >I continue my works on J1939 on another platform (based on IMX6 and
> >Yocto).
>
> I'm currently using the same iMX6 with yocto.
>
> >
> >I try now to patch the Yocto Kernel to embed your J1939 stack.
> >But, this yocto kernel is based on 3.10-r0 and the nearest version of
> >your git is for 3.8 or for 3.12-rc1 kernels.
> >
> >I tried to patch with the git J1939-v3.8 and lot of conflicts appears
> >during merge.
> >I think I will have the same issues with 3.12-rc1.
> >
> You need first to rebase the j1939 branch onto 3.10, or else you merge everything including 3.12.
>
> >I suppose that modifications of the kernel are limited to can stack and
> >can drivers. I'm right?
>
> Can stack only, no drivers.
>
> >Can I patch my kernel manualy with the specific J1939 sources and adapt
> >their structures to my kernel version?
>
> You should merge using git and resolve merge conflicts on the way.
> I cannot tell from my current position which branch to start best with.
> Or you could wait until Tuesday, then I can push a my 3.10 branch. I've gone through the merge conflicts already...
>
> >
> >What do you think about that?
> >
> >Best regards,
> >
> >Pascal
> >
>
> Sent from a small mobile device
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
next prev parent reply other threads:[~2015-09-08 7:58 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 [this message]
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
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=20150908075800.GA864@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