From: "Iain Sandoe" <iain@sandoe.co.uk>
To: linuxppc-dev@lists.linuxppc.org
Cc: Benjamin Herrenschmidt <bh40@calva.net>
Subject: 2.4.0-test3 dmasound - prob. found - solution ?
Date: Wed, 12 Jul 2000 22:15:24 +0100 [thread overview]
Message-ID: <200007122119.WAA26666@hyperion.valhalla.net> (raw)
Hi Ben,
I've been through the (non-PB) init code very carefully and am convinced
that what was in dmasound.c in pre10-ben1 is also in the split code from
2.4.0-test3.
TODO - go through the PB stuff equally carefully (later).
I have found the problem with G3/desktop/AWACS rev.3.
2.4.0-test3 has conditionals before cuda interaction like:
if( sysctrlr != sysctril_cuda) ... don't do it...
2.2.17pre10 has:
if( adb_hardware != adb_viacuda) ... don't do it...
commenting out the conditional before the bit where output is switched on
brings the G3 to life...
The questions are:
what does this change reflect in the transition to 2.4.0?
which is correct (noting also that there are *three* possible ADB sources in
the configs)?
looking much better...
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2000-07-12 21:15 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=200007122119.WAA26666@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).