From: Marc Kleine-Budde <mkl@pengutronix.de>
To: pfifre.ext@orange.com, Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: J1939 + iMX6 + yocto
Date: Thu, 10 Sep 2015 15:30:39 +0200 [thread overview]
Message-ID: <55F185FF.3030400@pengutronix.de> (raw)
In-Reply-To: <2144_1441891087_55F1830F_2144_9033_1_72e71e6a-832b-4f03-b5a6-47ea4e7bb890@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
[-- Attachment #1: Type: text/plain, Size: 694 bytes --]
On 09/10/2015 03:18 PM, pfifre.ext@orange.com wrote:
> "Did you follow the steps that I explained on http://elinux.org#J1939?"
> Yes, I follow your explanations on http://elinux.org#J1939
> I'm on a v3.10r0, but I don't think that's the r0 change the kernel a lot.
> I will try it again.
What's a v3.10r0? There is no official "r0" Kernel release. Your kernel
vendor may probably help you with this.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2015-09-10 13:30 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
2015-09-10 13:18 ` pfifre.ext
2015-09-10 13:30 ` Marc Kleine-Budde [this message]
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=55F185FF.3030400@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=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.