From: "Iain Sandoe" <iain@sandoe.co.uk>
To: linuxppc-dev@lists.linuxppc.org
Subject: [PATCH] 2.4.1p4 : dmasound ed21 - houston, we have record ;-)
Date: Thu, 18 Jan 2001 07:57:37 +0000 [thread overview]
Message-ID: <20010118075610.52EC8DB9E1@atlas.valhalla.net> (raw)
Hi,
This is only posted here - for now...
I would dearly like to post to Linux-Audio-Dev & Music-DSP to tell them that
PPC has hit the 21st century for audio... well, OK, that we can get sound in
as well as out... but - I could do with some testing for machines I don't
have.
====
This is a quickie nasty set of patches to mop up the major hassles that have
been most frequently reported in the six months I have been inactive...
1. I think I've finally squashed the dbdma fragility bug and _hammered_ the
driver (using all the stresses from the latency test set simultaneously)
without it stopping... but I shall wait to see what you all think.
2. In the process, I believe that record is now working reliably.
It does for me using "rec" (front end to SoX).
I can do an e-to-e (using a loopthrough program) and thrash the machine
without it killing the driver. (sound drops out, of course, see below).
3. I've fixed up the _AWACS_ mixer abstraction to make the sliders work as
expected for RecLevel
4. the AWACS mixer abstraction now keeps values so that mixer apps that
don't obey OSS rules (most of them) still work.
5. I've separated the Mic Gain control from the mic/cd/line selection
process - so that you can do it independently - it makes more sense to me in
mixer apps that don't understand PMac h/ware (description on the linked
page).
6. there's source for a loopthrough program to help test it - on the stest
page.
====
2.4.x & stest pages linked from:
http://www.drfruitcake.com/linux/linuxppc.html
there is a pre-built 2.4.1pre4 kernel and module set - with Andrew Morton's
Low-Latency patch applied (unfortunately doesn't have quite such spectacular
improvements on PPC as on x86 - but that's another story).
I would like:
(A) Pismo owners to see if it solves the LE file problems.
(B) People to tell me what the audio connectivity of different Pmac models
is.
(C) BURGUNDY:
This is a smart chip and it's hard to work on it without any test hardware
so Owners/DISTROS? if you have a spare machine with Burgundy - or (even
better) an Apple DVD/Video card for the perch slot in a G3/beige - and you
can spare it for a few months... let me know.
Alternatively - someone can volunteer to implement/test... ;-)
AUDIO LATENCY:
We have big hassles.
As it stands, Linuxppc is not usable for serious audio - even with low
latency patches applied.
Trying to get some stuff together to find out where the killers are.
GOTCHAS:
It is possible that applications which set number of frags & frag sizes
could put stuff in that would break the driver (this has always been true
AFAICT). Don't try less than three frags or more than 4 ;-))))
this is not meant to be nice code - just band-aid - there's a proper
re-write under way but that will take some time.
ciao,
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2001-01-18 7:57 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=20010118075610.52EC8DB9E1@atlas.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).