defconfig for pmac in 2.3.51 and up

defconfig for pmac in 2.3.51 and up

[andreas tobler]

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)

Thx,
Andreas

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

Re: defconfig for pmac in 2.3.51 and up

[Martin Costabel]

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/

Re: defconfig for pmac in 2.3.51 and up

[Andreas Tobler]

Martin Costabel wrote:
>
> 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...

On bitkeeper they're lost a longer time, but on linuxcare only since the
latest update from 48 to 51. Normally I wouldn't recognize such things,
but since I enabled the --delete option in rsync, such files, which are
no longer present, are deleted. Maybe the same happened to
linuxcare-pmac-devel when syncing with bitkeeper??
I have the files around on an other machine, but I agree; weird

Andreas

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

Re: defconfig for pmac in 2.3.51 and up

[Michel Lanners]

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/

Re: defconfig for pmac in 2.3.51 and up

[Martin Costabel]

Michel Lanners wrote:

> >> (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.

If this disappearance of the 3 defconfig files is by purpose, then the
arch/ppc/Makefile should be told about it, too. There you still find 9
different *_config targets, but 3 of them won't work because the
respective *_defconfig files have disappeared. The 6 other oddball
*_defconfig files are still there.

> I think it still makes sense, though, to keep the default configs for
> each hardware type. Makes kernel config a lot easier...

Developers only ever use make oldconfig, so the other make *config
options are notoriously untested.

--
Martin

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