From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: francesco.chiechi@colibre.it, Simon Horman <horms@verge.net.au>,
Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: [PATCH] kexec tools mipsel port
Date: Sun, 17 Feb 2008 02:41:49 +0100 [thread overview]
Message-ID: <47B790DD.7090100@wpkg.org> (raw)
In-Reply-To: <47B74826.8090707@wpkg.org>
Tomasz Chmielewski schrieb:
(...)
>>> There was a thread about kexec-tools mipsel port on Kexec Mailing
>>> List in June 2007.
>>>
>>> What's the current state of this patch?
>>>
>>> Is it working, will be merged, will not be merged?
>>
>> Its still very much in the state of needing someone to
>> nurse it into a merge.
>
> Funny thing is, kernel supports kexec, but there is no userland support
> for it (well, unless you patch kexec-tools with the patches you found
> somewhere on the internet).
>
> I'll try to see if the old patches posted to this list work for me.
Well, it's not very encouraging:
# kexec -l vmlinux-2.6.23.1
# kexec -e
Starting new kernel
Will call new kernel at 002ca000
Bye ...
And that's about it.
Do I need to specify mem-min and/or mem-max on mipsel?
--
Tomasz Chmielewski
http://wpkg.org
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-02-17 1:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 11:50 [PATCH] kexec tools mipsel port Tomasz Chmielewski
2008-02-16 16:33 ` Simon Horman
2008-02-16 20:31 ` Tomasz Chmielewski
2008-02-17 1:41 ` Tomasz Chmielewski [this message]
2008-02-17 4:56 ` Simon Horman
2008-02-17 22:05 ` Francesco Chiechi
-- strict thread matches above, loose matches on Subject: below --
2007-06-01 22:21 francesco chiechi
2007-06-04 5:40 ` Horms
2007-06-21 7:52 ` francesco chiechi
2007-06-26 5:31 ` Milton Miller
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=47B790DD.7090100@wpkg.org \
--to=mangoo@wpkg.org \
--cc=francesco.chiechi@colibre.it \
--cc=horms@verge.net.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.