public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dmj+@andrew•cmu.edu>
To: linuxppc-dev@lists•linuxppc.org
Subject: Re: Incoming to helium.harhan.org:/home/linuxppc/linuxppc_2_4_alt
Date: Tue, 9 Apr 2002 16:15:37 -0400	[thread overview]
Message-ID: <20020409161537.A11697@nevyn.them.org> (raw)
In-Reply-To: <0204092005.AA24074@ivan.Harhan.ORG>


On Tue, Apr 09, 2002 at 01:05:42PM -0700, Michael Sokolov wrote:
>
> Tom Rini <trini@kernel•crashing.org> wrote:
>
> > Taking debian as an example here.  You certainly wouldn't stick a zImage
> > for every board into 1 package.
>
> Exactly, which is why I never liked that idea.
>
> > So you only 'win' if you have a common, _bootable_ image on all of these
> > boards.
>
> Yes.
>
> > And while it is possible that there could be a common
> > firmware, I'm not holding my breath. :)
>
> When I go to Debian with this, I'll be asking for a ppcstar subarch to join to
> the ranks of apus, chrp, powermac, and prep. All HEC PPC boards will be
> PPCStar-compliant. If another manufacturer wants Debian support, they'll have
> to address Debian themselves and decide for themselves if they want to
> standardize their boot mechanism to make their request more acceptable.

Debian only supplies CONFIG_ALL_PPC images right now.  The
CHRP/pmac/PREP breakdown was only for 2.2.

If GENERIC_PPC32 is adequate, I'll do that instead - when it's ready.

--
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

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

  reply	other threads:[~2002-04-09 20:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200204060739.g367duV18841@helium.Harhan.ORG>
2002-04-08 15:20 ` Incoming to helium.harhan.org:/home/linuxppc/linuxppc_2_4_alt Tom Rini
2002-04-08 17:58   ` benh
2002-04-08 18:57     ` Tom Rini
2002-04-08 18:40       ` Benjamin Herrenschmidt
2002-04-09  8:14         ` Geert Uytterhoeven
2002-04-09 10:08           ` benh
     [not found]   ` <0204081705.AA21087@ivan.Harhan.ORG>
2002-04-08 18:02     ` benh
2002-04-09 14:52     ` Tom Rini
2002-04-09 19:23       ` Michael Sokolov
2002-04-09 19:47         ` Tom Rini
2002-04-09 20:05           ` Michael Sokolov
2002-04-09 20:15             ` Daniel Jacobowitz [this message]
2002-04-10 15:09             ` Tom Rini
2002-04-11  3:11               ` Michael Sokolov
2002-04-11 15:29                 ` Tom Rini
2002-04-15 16:54         ` Troy Benjegerdes
2002-04-15 18:11 Michael Sokolov

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=20020409161537.A11697@nevyn.them.org \
    --to=dmj+@andrew$(echo .)cmu.edu \
    --cc=linuxppc-dev@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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