From: Sven Neumann <s.neumann@raumfeld.com>
To: kexec@lists.infradead.org
Subject: kexec 2.0.4-rc1 won't work on an ARM kernel without device-tree
Date: Sat, 24 Nov 2012 10:00:42 +0100 [thread overview]
Message-ID: <1353747642.6515.16.camel@bender> (raw)
Hi,
I am trying to use kexec-2.0.4-rc1 on an ARM device running Linux 3.0.4.
This old kernel does obviously not have device-tree support. Here's the
error message I get:
# uname -a
Linux speaker 3.0.4 #1 PREEMPT Fri Nov 23 09:15:39 CET 2012 armv5tel GNU/Linux
# kexec --append="console=ttyS0,115200 root=ubi0:RootFS rootfstype=ubifs rw ubi.mtd=3" /boot/uImage --force
unrecoverable error: could not scan "/proc/device-tree/": No such file or directory
Looks like the release candidate depends on the very latest kernel
features and won't work on older kernels? Is that intentional?
Regards,
Sven
--
Sven Neumann <s.neumann@raumfeld.com>
Raumfeld by Teufel
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2012-11-24 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 9:00 Sven Neumann [this message]
2012-11-28 8:42 ` kexec 2.0.4-rc1 won't work on an ARM kernel without device-tree Sven Neumann
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=1353747642.6515.16.camel@bender \
--to=s.neumann@raumfeld.com \
--cc=kexec@lists.infradead.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