public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Iain Sandoe" <iain@sandoe•co.uk>
To: linuxppc-dev@lists•linuxppc.org
Cc: Benjamin Herrenschmidt <bh40@calva•net>
Subject: [PATCH] 2.4.0-test3 sys_ctrler fix.
Date: Thu, 13 Jul 2000 02:29:45 +0100	[thread overview]
Message-ID: <200007130129.CAA04704@hyperion.valhalla.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

here is a patch against 2.4.0-test3 as of yesterday (i.e. against the
version with broken timer.c & idle.c).  I was having real problems getting
the BK rsync stuff until just now...

This patch fixes the cross-referencing of sys_ctrler - a variable indicating
the ADB controller type (CUDA or PMU).

It is quite wide-ranging and affected pmac_setup, xmon, nvram, time, start,
via-cuda, via-pmu & dmasound.

It may already have been fixed in 2.4.0-test4 (I just noticed that bitkeeper
has changed).

====

I'll do a separate patch against 2.4.0-test3 for the dmasound stuff (once
I've checked it out a bit more).

If you're desperate to try the sound then add a line

extern sys_ctrler_t sys_ctrlr ;

anywhere after machdep.h  has been included - this should fix anyone else
who has a G3/desktop (with the dmasound sources from test3).

It *might* fix PB problems too (but I can't be certain).

====

It needs the scrutiny of a more experienced bunch - I may not have got the
conditionalisation right for all PPC platform variants... please be
gentle-ish...

Iain.

[-- Attachment #2: sys_ctrler.patch --]
[-- Type: application/binary, Size: 3609 bytes --]

                 reply	other threads:[~2000-07-13  1:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200007130129.CAA04704@hyperion.valhalla.net \
    --to=iain@sandoe$(echo .)co.uk \
    --cc=bh40@calva$(echo .)net \
    --cc=linuxppc-dev@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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