From: Michel Lanners <mlan@cpu.lu>
To: toa@pop.agri.ch
Cc: costabel@wanadoo.fr, linuxppc-dev@lists.linuxppc.org
Subject: Re: defconfig for pmac in 2.3.51 and up
Date: Sun, 12 Mar 2000 16:51:35 +0100 (CET) [thread overview]
Message-ID: <200003121551.QAA00488@piglet.grunz.lu> (raw)
In-Reply-To: <38CB94D1.C443C343@pop.agri.ch>
On 12 Mar, this message from Andreas Tobler echoed through cyberspace:
>> > 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...
Wouldn't this be a side-effect of trying to 'unify' all the PPC
configs? There's only a generic PPC config option as well, an no more
CONFIG_PMAC, CONFIG_PREP, CONFIG_CHRP etc.., thy are all replaced by
the single CONFIG_ALL_PPC.
I think it still makes sense, though, to keep the default configs for
each hardware type. Makes kernel config a lot easier...
Michel
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art.
23, Rue Paul Henkes | Ask Questions. Make Mistakes.
L-1710 Luxembourg |
email mlan@cpu.lu |
http://www.cpu.lu/~mlan | Learn Always. "
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-12 15:51 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
2000-03-12 13:00 ` Andreas Tobler
2000-03-12 15:51 ` Michel Lanners [this message]
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=200003121551.QAA00488@piglet.grunz.lu \
--to=mlan@cpu.lu \
--cc=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).