linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: relocatable kernel vs. yaboot
Date: Thu, 30 Oct 2008 22:37:14 +0100	[thread overview]
Message-ID: <1225402634.16440.2.camel@johannes.berg> (raw)
In-Reply-To: <18698.10295.463071.212141@cargo.ozlabs.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]

On Fri, 2008-10-31 at 08:33 +1100, Paul Mackerras wrote:

> Yes, yaboot needs to be fixed.

Yeah, my bad, I was offline when writing this and only checked later to
find you'd already discussed that. Sorry.

> > Modifying the vmlinux in the same way as above makes yaboot take it, and
> > I can easily make this part of my installation procedure, but I wonder
> > if it should be done automatically? Or maybe only documented in the
> > Kconfig help text? I probably wouldn't have enabled it and then wondered
> > why it doesn't work if it had warned me about breaking yaboot ;)
> 
> Yes, we could add something to the help text.  Until yaboot gets
> fixed, you could either boot the zImage with yaboot or use that
> iseries hack.

I can send a patch if you want?

> Why did you enable it?  Just to try it out?  The main reason for
> having it turned on is if you want to have a single kernel image that
> can be used both as a normal kernel and a kdump kernel.

Yeah, no particular reason, just enabled it on a whim when oldconfig
asked.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2008-10-30 21:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29 23:26 relocatable kernel vs. yaboot Johannes Berg
2008-10-30 21:33 ` Paul Mackerras
2008-10-30 21:37   ` Johannes Berg [this message]

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=1225402634.16440.2.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --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).