From: Gene Heskett <gheskett@shentel.net>
To: linux-rt-users@vger.kernel.org
Subject: trying to build 4.16.18-rt9 on arm
Date: Sun, 23 Jun 2019 02:20:30 -0400 [thread overview]
Message-ID: <201906230220.30922.gheskett@shentel.net> (raw)
And I am missing mkimage to build the uImage needed for an rpi-3b on the
rpi-3b.
I have downloaded and unpacked tools-master.zip which does contain a
mkimage directory.
Looks like this:
pi@picnc:/media/pi/workpi1/linux-rt-devel-4.16.18-rt9 $
ls -l ../tools-master/mkimage
total 48
-rw-r--r-- 1 pi pi 157 Jan 12 2018 args-uncompressed.txt
-rw-r--r-- 1 pi pi 201 Jan 12 2018 boot-uncompressed.txt
-rw-r--r-- 1 pi pi 32768 Jan 12 2018 first32k.bin
-rwxr-xr-x 1 pi pi 822 Jan 12 2018 imagetool-uncompressed.py
-rw-r--r-- 1 pi pi 343 Jan 12 2018 README
Where this is sitting is a long ways away from the rpi's $PATH.
And you can paint me bright green, never haveing attempted anything like
this.
So what I am considering is composing a bash script named mkimage that is
in $PATH,
to exec
python /media/pi/workpi1/tools-master/mkimage/imagetool-uncompressed.py
with the path to the (z)image file as its argument.
What I am unsure of is how to specify the output path so as to put the
output file back into the kernel build tree so that a "make deb-pkg"
can find it.
So I could sure use some guidance.
Since this Makefile dates from 2002, is there a patch for it that will
eliminate this bit of tom-foolery with a bash script? I'm trying to do
this on raspian stretch installed on the rpi-3b.
Thank you all.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
reply other threads:[~2019-06-23 6:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201906230220.30922.gheskett@shentel.net \
--to=gheskett@shentel.net \
--cc=linux-rt-users@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;
as well as URLs for NNTP newsgroup(s).