public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Whitmore <arigead@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: RaspberryPi "is this a real kernel?"
Date: Sun, 24 May 2015 11:32:36 +0100	[thread overview]
Message-ID: <20150524103235.GA7663@bamboo.electronicsoup> (raw)

I tried to subscribe to the RaspberryPi Kernel mailing list a few days ago but
I guess that my request has not been accepted as yet. Maybe it was missed so I
re-tried a moment ago. Since I can't get in there I thought I'd try
here. Apologies, bit of a panic.

So I'm trying to make a few changes to the Ubuntu Mate kernel for the
RaspberryPi V2. The Ubuntu kernel is 3.18.0-22 so I checked out, what I
thought was the last version of 3.18.0 from the RaspberryPi Kernel git repo,
did a make oldconfig, make menuconfig, to include CAN and stuff and then built
the kernel without any issues.

Now I'm not fully understanding the rest of the process but there's a utility
in the RaspberryPi tools to actually take the output from the build and
produce the image file for your SD card. It's questioning the integrity of my
built kernel and I've no idea why. (I think it's lovely and can't see why
anybody could question it!)

$ ./mkknlimg ../../linux/arch/arm/boot/zImage 3.18.0-can+.img
tail: +: invalid number of bytes
* Is this a valid kernel? In pass-through mode.


I'm using "mkknlimg" as the other utility "imagetool-uncompressed.py" is just
giving me a data file. 

So can anybody help me to understand what it is that's going wrong with this
process. 

John

             reply	other threads:[~2015-05-24 10:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-24 10:32 John Whitmore [this message]
2015-05-25  1:11 ` RaspberryPi "is this a real kernel?" Valdis.Kletnieks
2015-05-25  9:24   ` John Whitmore
2015-05-26 13:53     ` Austin S Hemmelgarn
2015-05-29 14:02       ` John Whitmore

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=20150524103235.GA7663@bamboo.electronicsoup \
    --to=arigead@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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