Linux CAN drivers development
 help / color / mirror / Atom feed
From: Patrick Menschel <menschel.p@posteo.de>
To: Paul Bongaerts <pauluzs@gmail.com>, linux-can@vger.kernel.org
Subject: Re: J1939 kernel for Raspberry Pi
Date: Mon, 15 May 2017 18:52:14 +0200	[thread overview]
Message-ID: <8cadf968-35f7-d490-9f00-3be5b52ea34d@posteo.de> (raw)
In-Reply-To: <CAGJdXcFPye1VUwaSkDLKNf_apXud3Qnj_wYXv1PzsypbmvCdXQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 676 bytes --]

Hello Paul,

just to be sure, you're not doing both configurations, are you?

>>>> Set kernel type
>>>>
>>>> For Rapberry Pi 1/compute/zero (w)
>>>> KERNEL=kernel
>>>> For Raspberry Pi 2/3
>>>> KERNEL=kernel7
>>>>
>>>> Use default config
>>>>
>>>> For Rapberry Pi 1/compute/zero(w)
>>>> make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- bcmrpi_defconfig
>>>> For Raspberry Pi 2/3
>>>> make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- bcm2709_defconfig
>>>>
Imho building this top down would result in armv7 code for rpi2/3
(kernel7.img), not armv6 as needed for rpi1/ zero (kernel.img).

That would explain your crosscompile issue.

Regards,
Patrick


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3709 bytes --]

      parent reply	other threads:[~2017-05-15 16:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 11:50 J1939 kernel for Raspberry Pi Paul Bongaerts
2017-05-10 15:03 ` Patrick Menschel
2017-05-11 19:29 ` Kurt Van Dijck
2017-05-14 17:57   ` Paul Bongaerts
2017-05-14 22:30     ` Paul Bongaerts
2017-05-15  7:14       ` Kurt Van Dijck
2017-05-15 10:50         ` Paul Bongaerts
2017-05-15 10:53           ` Paul Bongaerts
2017-05-15 12:43             ` Kurt Van Dijck
2017-05-16 13:02               ` Kurt Van Dijck
2017-05-16 13:13                 ` Kurt Van Dijck
2017-05-16 17:22                   ` Paul Bongaerts
2017-05-16 20:40                     ` Paul Bongaerts
2017-05-15 16:52             ` Patrick Menschel [this message]

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=8cadf968-35f7-d490-9f00-3be5b52ea34d@posteo.de \
    --to=menschel.p@posteo.de \
    --cc=linux-can@vger.kernel.org \
    --cc=pauluzs@gmail.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