From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Hollis R Blanchard <hollis+@andrew.cmu.edu>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: esound and 2.2's dmasound
Date: Wed, 03 Jan 2001 19:47:36 +0000 [thread overview]
Message-ID: <200101031947.TAA19299@hyperion.valhalla.net> (raw)
Hi Hollis et. al...
>However, with dmasound as a module (and 'alias sound dmasound_pmac' in
>/etc/modules.conf), everything (including esound) works perfectly.
;-)))
> - 2.2.18 final and esound still don't play well together
> - the 2.4 dmasound backport doesn't work compiled in (and probably could be
> updated for 2.2.18)
it's probably a silly - like forgetting to call the init from within
drivers/char/mem.c (that change has been made several times by both me &
Geert) but it seems to slip out of the diffs somehow)...
I will be back on the case as soon as poss (maybe after this month).
There's obviously lots still to do to get full duplex working properly for
2.4.0 - from other reports... and a niggle in my mind that says "maybe some
of the dbdma traffic I've seen on the list might have an effect on the
flakinesss (or otherwise) of the dmasound driver..."
(and also there's the start of an ALSA version - from a posting on the
ALSA-dev list yesterday)...
- I'm just still bogged down in "work-that-pays-the-rent" :-(
ciao,
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-01-03 19:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 19:47 Iain Sandoe [this message]
2001-01-03 20:53 ` esound and 2.2's dmasound Olaf Hering
2001-01-03 21:10 ` Hollis R Blanchard
-- strict thread matches above, loose matches on Subject: below --
2001-01-03 22:16 Iain Sandoe
2001-01-03 22:13 Iain Sandoe
2001-01-03 18:49 Hollis R Blanchard
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=200101031947.TAA19299@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=hollis+@andrew.cmu.edu \
--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).