linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: <msokolov@ivan.Harhan.ORG>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: CONFIG_GENERIC_PPC32
Date: Sun, 7 Apr 2002 00:29:40 +0100	[thread overview]
Message-ID: <20020406232941.774@smtp.wanadoo.fr> (raw)
In-Reply-To: <0204062217.AA17328@ivan.Harhan.ORG>


>(This doesn't mean that having such wrapper is the RTTD or that the vmlinux
>boot ABI inherently has to change all the time. It is perfectly possible
>technically to fix the vmlinux boot ABI, keep it stable, and eliminate all
>those wrappers. But that would require a revolution to oust the current
>tyrants
>with a strangehold on write access to the mainline tree and let people with
>more progressive minds in.)

heh, well, I for one thinks the PPC tree hasn't a strong enough tyrant ;)

>> 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.
>
>I don't have my own boards yet. In my tree I used the Adirondack, EV-64260A,
>and K2 ports to prove the CONFIG_GENERIC_PPC32 implementation. EV-64260A is
>Galileo's reference board for the GT-64260A system controller, and Adirondack
>and K2 are SBS boards already supported in 2_4_devel. I'm not at SBS any more
>and don't have their hardware, but those boards are still fresh in my
head and
>I needed a few ports to prove my generic PPC32 implementation.

Ok.


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

  reply	other threads:[~2002-04-06 23:29 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-06 22:17 CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-06 23:29 ` Benjamin Herrenschmidt [this message]
  -- 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 21:39 CONFIG_GENERIC_PPC32 Michael Sokolov
2002-04-06 22:52 ` CONFIG_GENERIC_PPC32 Benjamin Herrenschmidt
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
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=20020406232941.774@smtp.wanadoo.fr \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=msokolov@ivan.Harhan.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).