Re: contrib

[Christiaan Welvaart]

On Tue, 15 Feb 2005 danny@mailmij.org wrote:

> On Tue, Feb 15, 2005 at 12:19:03PM +0100, Christiaan Welvaart wrote:
> >
> > > > > Also, Christiaan, I think some src.rpms for stuff in main-ppc are
> > > > > missing (or does main kernel suddenly have all patches needed to do
> > > > > power4?).
> > > >
> > > > Maybe you can explain what I'm doing wrong that UP-only config options
> > > > don't appear in the ppc.config? That should be resolved before I can
> > > > submit the ppc32 changes.
> > > BROKEN_ON_SMP thing (ie, the ppc.config is probably SMP, so it disables
> > > up things)? But with the src.rpm its a bit hard to see. What specific
> > > option do you want? For multimedia, I never noticed something important
> > > missing but perhaps I didn't look hard enough.
> >
> > AFAIK all the $arch.config files are for SMP, and the x86 config has
> > UP-only options even though it's configed for SMP. Most of them are
> > unlikely to be used on ppc so you probably have them disabled, but I also
> > have
> >         $to_add{PRISM2_PCI} = "m";
> >         $to_add{PRISM2_CS} = "m";
> > (maybe it's fixed now, this is probably from ~2.6.6)
>
> strange. For multimedia, PRISM2_PCI and CS gets enabled without that
> workaround. I just add them to ppc.config. Since the kernel knows those
> are broken on SMP it disables them when you do make oldconfig on SMP. So
> just put them in the config?

So you manually add them to the ppc.config? Then the problem is updating a
config for a new kernel version. I simply run make oldconfig but I
guess one of the other scripts should be used...

> > > Also, I don't like the way the main kernel gives you 1 defconfig-maximum
> > > and does the tweaking for different processors in create_configs, so i
> > > added an option to be able to feed it a custom config directly (which I
> > > use for power4, so I don't need to borther with editing that perl script
> > > too much).
> >
> > 'power4' isn't a problem it seems, I currently have the following code for
> > it ('ppc' part probably not even needed):
> >
> >     if ($cpu eq "ppc") {
> >         $values{"6xx"}="y";
> >         $values{POWER4}="n";
> >     } elsif ($cpu eq "ppc4") {
> >         $values{"6xx"}="n";
> >         $values{POWER4}="y";
> >         $to_add{THERM_PM72}="m";
> >     }
>
> I know. Howver, I didn't saw the point in having a low of workarounds in
> the kernel that have no use on power4 since some chipsets don't exist on
> those machines. So I liked the fact I could create a power4 specific
> config.

Now you lost me. What workarounds are you talking about?

> > Hmm... being release manager does NOT necessarily mean:
> >   - maintaining the kernel
> I would be willing to do this (based on your config, so I leave the

I was trying to say that not a lot of knowledge of the platform is
needed...

> > while it does mean IMHO:
> >   - keeping track of bugs
> >   - setting target features and dates
> >   - testing installation (...)

> building cds?

Maybe: the package selection for the isos can only be tested by building
them.

> > > I tell you what I'm more or less hoping to do for 10.2:

<snip more kernel talk>

> > > - see if I can make the draktools somehow recognize mac-io devices like
> > > the soundcard and airport card. I almost finished this for 10.0, but not
> > > in time and gave it up since then. I don't know if I can do it now since
> > > I didn't expect a 10.2 and have no idea about a roadmap
> >
> > drakxtools already "recognizes" the sound card in 10.1 and cooker but with
> > a simple  arch() =~ /ppc/
>
> In draksound you mean? Yes. But i'd like to add a way of checking for
> i2c devices in harddrake as well.

That would be nice, but I don't see the audio device in
/sys/bus/i2c/devices/ (?).

> > > However, you may think some attention is needed in other areas (I've
> > > been thinking of adapting drakmouse to set up the mouse button
> > > emulation). Or perhaps the installer needs testing or whatever. Or you
> > > need help with broken rpms.
> >
> > Fixing the mouse button emulation setup would be great, it's one of the
> > few known bugs left from 10.1 (well, as listed in the release notes).
> >
> I'll try. My perl sucks but this can't be that hard :)

blame perl (: