All of lore.kernel.org
 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: Sat, 19 Sep 2015 08:34:35 +0200	[thread overview]
Message-ID: <5E00F3EF-2CEB-4BCE-9D73-BB4EE40ED851@vandijck-laurijssen.be> (raw)
In-Reply-To: <31941_1442579383_55FC03B7_31941_497_6_3c5ee703-7ff1-4f6c-8da3-b02d7f2c1939@OPEXCLILM7D.corporate.adroot.infra.ftgroup>



On 18 September 2015 14:29:40 CEST, pfifre.ext@orange.com wrote:
>Hi Kurt,
>
>That's the question: the patch seems to be build, but, this warning :
>"either "dev" is duplicate, or "j1939" is a garbage" seems that no
>patch has been done on the final distribution, no?
>I remember that this warning comes with the absence of iproute2-j1939
>patch. It is right?
>

Yes, you're right

>I verified the iproute2-j1939 recipe alone and it works fine.
>I think the patch won't be correctly done with the global recipe.
>

So this becomes a pure yocto issue.
Are you sure that 'ip' tool on the rootfs is from busybox or iproute2?

Kurt

>Best regards,
>
>Pascal
>
>
>-----Message d'origine-----
>De : Kurt Van Dijck [mailto:dev.kurt@vandijck-laurijssen.be] 
>Envoyé : vendredi 18 septembre 2015 14:11
>À : FIFRE Pascal Ext IMT/OLPS
>Cc : linux-can@vger.kernel.org
>Objet : RE: J1939 + iMX6 + yocto
>
>
>
>On 18 September 2015 11:04:29 CEST, pfifre.ext@orange.com wrote:
>>Hi Kurt,
>>
>>I add the Yocto patch yesterday in my distribution.
>>It's very strange, because it seems to be applied on build (it appears
>
>>on the Build without errors) but not on the distribution: I can't add 
>>any j1939 link (either "dev" is duplicate, or "j1939" is a garbage).
>
>The warning comes from iproute2. Did you patch that already?
>
>>Apparently, bitbake finds the necessary files.
>>I have just one warning at build : the file 
>>file://0001-ip-link-Remove-unnecessary-device-checking.patch doesn't
>be 
>>found by the build (not present on poky, then I removed this line in 
>>the bb).
>>
>>In fact, I notice that the git command in the bb doesn't work. I have 
>>made a voluntary error in the path and the build ran with no errors.
>>Then, your patch is no applied to the distribution.
>>
>>Do you have any idea?
>>
>>It's the last task I have to do to run all the features of my 
>>application.
>>
>>Thanks for your support.
>>
>>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.

Sent from a small mobile device

  reply	other threads:[~2015-09-19  6: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 [this message]
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=5E00F3EF-2CEB-4BCE-9D73-BB4EE40ED851@vandijck-laurijssen.be \
    --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 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.