linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Simon Richter <Simon.Richter@hogyros.de>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, linuxppc64-dev@ozlabs.org
Subject: Re: merge progress
Date: Tue, 18 Oct 2005 00:19:07 +0200	[thread overview]
Message-ID: <4354235B.8090608@hogyros.de> (raw)
In-Reply-To: <17235.33942.754076.419504@cargo.ozlabs.ibm.com>

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

Hi,

Paul Mackerras schrieb:

> Hmmm, probably should work off the merge tree.

Good, then I'll fast-forward them there.

> However, we decided at
> OLS that platforms would require a device tree before being merged.
> Have you looked at creating a suitable flattened device tree blob with
> dtc?  (If not, you can continue to compile with ARCH=ppc for now.)

In fact my current plan is to move away from m68k bootinfo (which APUS
borrows so you can use the same bootloader) towards a flattened dev tree
passed in from the bootloader. For that, however, we need a new
bootloader first, which is dependant on AmigaOS binutils/gcc.

So I guess it will be ARCH=ppc until the new bootloader is ready.

Should APUS still get a special treatment then, or should I try to
emulate enough of OF in the bootloader so it is possible to build CHRP
images that work on APUS?

   Simon

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 374 bytes --]

  reply	other threads:[~2005-10-17 22:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-11 12:26 merge progress Paul Mackerras
2005-10-11 12:31 ` Simon Richter
2005-10-17 11:01   ` Paul Mackerras
2005-10-17 22:19     ` Simon Richter [this message]
2005-10-18  7:50       ` Geert Uytterhoeven
2005-10-17 22:39     ` Kumar Gala
2005-10-11 18:54 ` Arnd Bergmann

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=4354235B.8090608@hogyros.de \
    --to=simon.richter@hogyros.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc64-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).