linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Leigh Brown <leigh@solinno.co.uk>,
	paulus@samba.org, linuxppc-dev@lists.linuxppc.org,
	barbieri@gmail.com
Subject: Re: [0/9] Support for old IBM PReP boxes
Date: Fri, 30 Jul 2004 18:08:48 +0200	[thread overview]
Message-ID: <20040730160848.GA12973@lst.de> (raw)
In-Reply-To: <20040730154611.GL16468@smtp.west.cox.net>


On Fri, Jul 30, 2004 at 08:46:11AM -0700, Tom Rini wrote:
> OK.  Thinking back to last time, I asked about being able to blacklist
> some machines Residual Data (since it's crap on some, but I don't have
> the dumps handy) and you mentioned that you'd like to do fixups on the
> data since there's a few cases where the data is mostly good, just with
> one or two incorrect things.  And it doesn't look like either are
> here... yet.
>
> Could you do a 10/9 patch that adds a bit of help to the PREP_RESIDUAL
> config option along the lines of:
> "When this information is incorrect, it could lead to the machine
> behaving incorrectly.  If this happens, please disable PREP_RESIDUAL and
> try again."
>
> And change the existing "Unless you expect to boot on a PReP system,
> there is no need to select Y." to "If you are running a PReP system, say
> Y here, otherwise say N."

As the residual support is runtime switchable can we also have a kernel
boot option?  That way we can switch it off for distro kernels.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-07-30 16:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-29 21:33 [0/9] Support for old IBM PReP boxes Leigh Brown
2004-07-30 15:30 ` Christoph Hellwig
2004-07-30 15:46 ` Tom Rini
2004-07-30 16:08   ` Christoph Hellwig [this message]
2004-07-30 16:50     ` Tom Rini
2004-07-30 16:58       ` Leigh Brown

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=20040730160848.GA12973@lst.de \
    --to=hch@lst.de \
    --cc=barbieri@gmail.com \
    --cc=leigh@solinno.co.uk \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paulus@samba.org \
    --cc=trini@kernel.crashing.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).