From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Jiri Masik <masik@pc203b.fzu.cz>, linuxppc-dev@lists.linuxppc.org
Subject: Re: dmasound - kernel panic
Date: Fri, 11 Aug 2000 11:29:30 +0100 [thread overview]
Message-ID: <200008111029.LAA05480@hyperion.valhalla.net> (raw)
> I've found that I can crash the kernel by cat /dev/audio. This is the
> message I'm getting immediately
The current version(s) [dmasound monolithic, back-port & 2.4.0] do not have
a read translation for:
MU law
A law.
So I'm afraid, for the moment, this will not work.
The reason for the oops is that the code does not check (having found a
translation table) that individual routines are *all* present.
This will be fixed at the next patch release.
I may do a read translation (but... feel free ;-)
Note that these days kernel-based sample-rate & size conversion is
deprecated. It really requires FP to do the job properly.
Much better to record from /dev/dsp in some appropriate 16 bit format and
then convert off-line using sox or something like that.
Iai.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-08-11 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-11 10:29 Iain Sandoe [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-09 22:02 dmasound - kernel panic Jiri Masik
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=200008111029.LAA05480@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=masik@pc203b.fzu.cz \
/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).