linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: <paulus@samba.org>
Cc: <msokolov@ivan.Harhan.ORG>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: CONFIG_GENERIC_PPC32
Date: Sat, 6 Apr 2002 23:52:36 +0100	[thread overview]
Message-ID: <20020406225236.3768@smtp.wanadoo.fr> (raw)
In-Reply-To: <0204062139.AA17200@ivan.Harhan.ORG>


>> I haven't look at the patch yet, but is my understanding correct that
>> you have individual config options enabling the various board support
>> and that you allow more than one to be selected at one time ?
>
>Yes.
>
>> If that is the case, then that's great. It's also what the arm ach does
>> and I like it.

Hi Paul !

I've looked at the patch in the meantime and it makes much sense. I want
to do something around those lines:

 - Completely rip off CONFIG_ALL_PPC in favor of CONFIG_GENERIC_PPC32
 - Each board model has it's own CONFIG_xxx entry (like Michael patch),
   which means adding "back" CONFIG_PMAC, CONFIG_CHRP, CONFIG_PREP, but
   those will only control which set of .c file will get in the makefile
   and the toplevel switch/case on platform_init. That is you will be able
   to select an arbitrary set of boards.
 - bi_recs are found in r4 when r3 contains "birc" (please, Michael, adapt
   to this so we stay consistent which what BootX does). Older way of finding
   them & cmdline & initrd still used when r3 doesn't contain that magic
   value. r5 still contains the OF PROM pointer, at least until we have
   the OF interface in a wrapper.

I think this patch will not be that invasive, and it will be fully backward
compatible, so I do intend to push it to _2_4_devel though I want your
ack first. I don't plan to include Michael boards in it, I want to rework
our ground to match what Michael does and then let him drop in his new
boards.

Ben.


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

  reply	other threads:[~2002-04-06 22:52 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-06 21:39 CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-06 22:52 ` Benjamin Herrenschmidt [this message]
2002-04-07  8:34   ` CONFIG_GENERIC_PPC32 Geert Uytterhoeven
2002-04-07  9:04     ` CONFIG_GENERIC_PPC32 Benjamin Herrenschmidt
2002-04-09  8:12     ` CONFIG_GENERIC_PPC32 Michael Schmitz
  -- strict thread matches above, loose matches on Subject: below --
2002-04-11 20:51 CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-11 19:10 ` CONFIG_GENERIC_PPC32 Mark A. Greer
2002-04-11 17:15 CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-11 16:24 CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-11 16:50 ` CONFIG_GENERIC_PPC32 benh
2002-04-11 15:40 CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-11 15:49 ` CONFIG_GENERIC_PPC32 Geert Uytterhoeven
2002-04-11 16:13 ` CONFIG_GENERIC_PPC32 benh
2002-04-11  3:08 CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-10 23:42 ` CONFIG_GENERIC_PPC32 Benjamin Herrenschmidt
2002-04-11 17:51 ` CONFIG_GENERIC_PPC32 Mark A. Greer
2002-04-12 12:57 ` CONFIG_GENERIC_PPC32 Paul Mackerras
2002-04-12 11:57   ` CONFIG_GENERIC_PPC32 benh
2002-04-12 19:02   ` CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-15 15:46     ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-15 18:08       ` CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-15 19:54         ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-06 22:17 CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-06 23:29 ` CONFIG_GENERIC_PPC32 Benjamin Herrenschmidt
2002-04-06 20:23 CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-06 22:06 ` CONFIG_GENERIC_PPC32 Benjamin Herrenschmidt
2002-04-08 15:48 ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-08 16:03   ` CONFIG_GENERIC_PPC32 Gabriel Paubert
2002-04-08 16:24     ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-08 16:48       ` CONFIG_GENERIC_PPC32 Gabriel Paubert
2002-04-08 17:23         ` CONFIG_GENERIC_PPC32 Matt Porter
2002-04-08 17:37           ` CONFIG_GENERIC_PPC32 Gabriel Paubert
2002-04-08 18:07             ` CONFIG_GENERIC_PPC32 Matt Porter
2002-04-08 18:41               ` CONFIG_GENERIC_PPC32 Gabriel Paubert
2002-04-08 18:18   ` CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-08 18:53     ` CONFIG_GENERIC_PPC32 Matt Porter
2002-04-09 14:59     ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-09 19:52       ` CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-10  8:27         ` CONFIG_GENERIC_PPC32 Geert Uytterhoeven
2002-04-10 15:17           ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-11  3:50             ` CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-11 15:27               ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-10 15:16         ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-11  3:46           ` CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-11 15:24             ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-11 16:16               ` CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-11 15:51                 ` CONFIG_GENERIC_PPC32 Mark A. Greer
2002-04-11 16:59                 ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-11 17:25                   ` CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-11 17:42                     ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-10 19:08         ` CONFIG_GENERIC_PPC32 Tom Rini
2002-04-10 13:20 ` CONFIG_GENERIC_PPC32 Paul Mackerras
2002-04-10 15:23   ` CONFIG_GENERIC_PPC32 benh

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=20020406225236.3768@smtp.wanadoo.fr \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=msokolov@ivan.Harhan.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).