From: "Iain Sandoe" <iain@sandoe.co.uk>
To: linuxppc-dev@lists.linuxppc.org
Subject: 2.4.0-t1 & t3: dmasound
Date: Wed, 12 Jul 2000 12:06:48 +0100 [thread overview]
Message-ID: <200007121106.MAA13142@hyperion.valhalla.net> (raw)
has anyone got dmasound_awacs to produce output under test1-ac21 or test3?
The same code base is the one I pack-ported to 2.2.17pre7/10 & works OK
(with reservations) there.
not a peep from 2.4.0-tx. Modules load OK, nothing seems overtly broken (no
crash, sndstat looks sensible, setting parameters works OK)... just no
output.
Happy to try & fix - but it would be useful to know whether there are *any*
conditions under which it has worked.
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-12 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-12 11:06 Iain Sandoe [this message]
2000-07-12 13:10 ` 2.4.0-t1 & t3: dmasound schinder
2000-07-12 14:52 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2000-07-12 13:16 Iain Sandoe
2000-07-12 15:55 Iain Sandoe
2000-07-12 16:35 ` Dan Malek
2000-07-12 18:07 Iain Sandoe
2000-07-12 18:19 ` Dan Malek
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=200007121106.MAA13142@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--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).