linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Martin Costabel <costabel@wanadoo.fr>
To: andreas tobler <toa@pop.agri.ch>
Cc: Linuxppc-Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: defconfig for pmac in 2.3.51 and up
Date: Sun, 12 Mar 2000 13:37:20 +0100	[thread overview]
Message-ID: <38CB8F80.8A64B8CC@wanadoo.fr> (raw)
In-Reply-To: 38CB649E.7B7F426@pop.agri.ch


andreas tobler wrote:
>
> Hi all,
>
> maybe a dump Q, but I don't find it. In the kernels before 2.3.51 (stable &
> devel) I could type 'make pmac_config' to get the most things set to my needs.
> Now in 2.3.51 this defconfig is away.
> Any idea? Neither on bitkeeper nor on linuxcare. Or are there new methods to
> make defconfigs for certain machines?
> I don't like to set every item by hand. (too much)

Strange... When I say 'make pmac_config' in the 2.3.51 tree from
bitkeeper, it does
rm -f .config arch/ppc/defconfig
cp -f arch/ppc/configs/pmac_defconfig arch/ppc/defconfig

The only thing that changed from older kernels is that the config files
now have their own subdirectory arch/ppc/configs/. But this should work
precisely as before.

(digging a little further...) Oh I see, bitkeeper doesn't have the
complete collection of arch/ppc/configs/*_defconfig files any more; no
more chrp, pmac, or prep. I still have them from a previous version.
Weird...



--
Martin

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

  reply	other threads:[~2000-03-12 12:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-12  9:34 defconfig for pmac in 2.3.51 and up andreas tobler
2000-03-12 12:37 ` Martin Costabel [this message]
2000-03-12 13:00   ` Andreas Tobler
2000-03-12 15:51     ` Michel Lanners
2000-03-12 18:46       ` Martin Costabel

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=38CB8F80.8A64B8CC@wanadoo.fr \
    --to=costabel@wanadoo.fr \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=toa@pop.agri.ch \
    /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).