linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Meissner <meissner@cygnus.com>
To: Cort Dougan <cort@persephone.cs.nmt.edu>
Cc: Matt Porter <mmporter@home.com>,
	Paul.Mackerras@cs.anu.edu.au,
	Hartmut Koptein <koptein@et-inf.fho-emden.de>,
	zankel@tarantel.rz.fh-muenchen.de, bh40@calva.net,
	davidsen@prodigy.com, marsmail@globegate.utm.edu,
	dvdoug@tiac.net, paubert@iram.es, jskov@cygnus.co.uk,
	hozer@drgw.net, linuxppc-dev@lists.linuxppc.org
Subject: Re: [ppc-dev] Summary: Restructuring Efforts
Date: Fri, 19 Feb 1999 20:18:12 -0500	[thread overview]
Message-ID: <19990219201812.A2814@wogglebug.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.3.96.990219132018.12450A-100000@persephone.cs.nmt.edu>; from Cort Dougan on Fri, Feb 19, 1999 at 01:21:35PM -0700


On Fri, Feb 19, 1999 at 01:21:35PM -0700, Cort Dougan wrote:
> 
> The concern in this discussion (If I'm following along correctly) is RAM
> size, that's all.  The PReP bootloader works on MTX even though it's not
> in the embedded dir.  Since RAM is the issue how much RAM does a typical
> MTX installed system have?  Do they boot from flash or from a hd once
> deployed?

Note, on my little PowerStack with 48 meg of memory, the new bootloader does
not work (as I reported previously -- there are no messages after the prompt).
The old bootloader works on the machine, but not on my big Utah PowerStack with
128 meg of memory.

> }PReP and CHRP machines are not necessarily desktops/servers.

-- 
Michael Meissner, Cygnus Solutions (Massachusetts office)
4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA
meissner@cygnus.com,	617-354-5416 (office),	617-354-7161 (fax)

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

  reply	other threads:[~1999-02-20  1:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-19  0:55 [ppc-dev] Summary: Restructuring Efforts Christian Zankel
1999-02-19  6:12 ` Paul Mackerras
1999-02-19  7:31   ` Cort Dougan
1999-02-19 13:20   ` Hartmut Koptein
1999-02-19 17:41     ` Matt Porter
1999-02-19 20:21       ` Cort Dougan
1999-02-20  1:18         ` Michael Meissner [this message]
1999-02-22 16:38         ` Matt Porter
1999-02-22 18:26           ` Cort Dougan
1999-02-22 23:42             ` Matt Porter
1999-02-26  6:53               ` Cort Dougan
1999-02-19 21:16       ` Hartmut Koptein
1999-02-19 13:54   ` Michael Meissner
1999-02-21 11:20     ` Paul Mackerras
1999-02-19  7:25 ` Cort Dougan

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=19990219201812.A2814@wogglebug.cygnus.com \
    --to=meissner@cygnus.com \
    --cc=Paul.Mackerras@cs.anu.edu.au \
    --cc=bh40@calva.net \
    --cc=cort@persephone.cs.nmt.edu \
    --cc=davidsen@prodigy.com \
    --cc=dvdoug@tiac.net \
    --cc=hozer@drgw.net \
    --cc=jskov@cygnus.co.uk \
    --cc=koptein@et-inf.fho-emden.de \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=marsmail@globegate.utm.edu \
    --cc=mmporter@home.com \
    --cc=paubert@iram.es \
    --cc=zankel@tarantel.rz.fh-muenchen.de \
    /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).