From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Haren Myneni <haren@us.ibm.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: _machine removal breaks kexec?
Date: Tue, 04 Apr 2006 14:05:15 +0200 [thread overview]
Message-ID: <1144152315.4449.54.camel@localhost.localdomain> (raw)
In-Reply-To: <44316705.1040202@us.ibm.com>
> Basically, kexec-tools looks the platform property to determine whether
> to read tce-base, tce-size and htab-* properties. The attached patch
> find out the platform info based on /proc/device-tree/chosen/htab-base
> property. Not tested yet.
You should just test if the properties exist ...
> Kumar, kexec-tools completely depends on device-tree. Not sure whether
> the embedded system exports the device-tree.
With arch=powerpc, they do
next prev parent reply other threads:[~2006-04-04 12:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 1:40 _machine removal breaks kexec? Anton Blanchard
2006-04-03 16:16 ` Benjamin Herrenschmidt
2006-04-03 17:32 ` Kumar Gala
2006-04-03 18:18 ` Haren Myneni
2006-04-04 5:40 ` Michael Ellerman
2006-04-04 6:15 ` Haren Myneni
2006-04-04 12:05 ` Benjamin Herrenschmidt [this message]
2006-04-03 23:16 ` Segher Boessenkool
2006-04-04 0:43 ` Kumar Gala
2006-04-04 12:04 ` Benjamin Herrenschmidt
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=1144152315.4449.54.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=haren@us.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).