linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Iain Sandoe" <iain@sandoe.co.uk>
To: linuxppc-dev@lists.linuxppc.org
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: [ANN] Dmasound backport to 2.2.17pre7/10 patch
Date: Fri, 07 Jul 2000 23:31:59 +0100	[thread overview]
Message-ID: <200007072232.XAA14475@hyperion.valhalla.net> (raw)


Hi List,

Thanks to Lars (just the first to reply - no other selection process ;-)

Here it is:

> <URL: http://quimby.gnus.org/circus/dmasound_backport.patch.bz2>

enjoy...

original post:

hello all,

This may/may not help those who are experiencing X lock-up with sound
(although I've never had the problem myself).

I have done a backport of Geert's split-up dmasound stuff to 2.2.17pre7.
Thanks to Geert for helpful suggestions in doing this.

The problem is that the patch is **too big** to put as an attachment to the
list....

Anyone able to provide a place for it? [50-ish kb as bz2]....
If anyone's desperate (i.e. those having actual real-now-problems) I can
e-mail.


It is against linuxcare linux-pmac-stable and OK against linux-pmac-benh as
well.

WHAT IT DOES:

there's a new drivers/sound/dmasound this contains a split-up version of
the multi-platform dmasound.c

It *should* add sound input to the Pmac - but that doesn't work reliably yet
(I suspect weirdness with the mixer abstraction - see below).  No crash but,
then, no recorded sound either.  I'll be on this a bit later on.

WHAT I'VE TESTED:

G3 AWACS Rev 3 with/without build as modules.
I will do G3/Lombard (IIRC has the burgundy AWACS).
I will do G4 just as soon as I get to setting it up :-)

WHAT I DIDN'T DO:

The other platforms - if it is not obvious what is needed - (add call to
dmasound_???_init() into drivers/char/mem.c and fix up the module/no module
stuff in drivers/sound/dmasound_????.c) then e-mail me off list and I'll
have a go.  BUT I've got no h'ware other than Pmac to test on.

TO DO:

Sort out mixer abstraction weirdness - there's definitely some funny
behaviour using kmixer - sometimes the stereo attribute is recognised -
sometimes not.

Sort out what is slowing things down when the buffer size is reduced:

we should be able to achieve 11ms output latency with AWACS.

Please test & comment (but send flames to /dev/null - this is my first
backport ;-)

ciao,
Iain.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-07-07 22:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-07 22:31 Iain Sandoe [this message]
     [not found] <200007080459.XAA32335@lists.linuxppc.org>
2000-07-11 15:15 ` [ANN] Dmasound backport to 2.2.17pre7/10 patch Derek Homeier
     [not found] <20000711165125.12731@mailhost.mipsys.com>
2000-07-12 10:21 ` Derek Homeier
  -- strict thread matches above, loose matches on Subject: below --
2000-07-12 11:12 Iain Sandoe
2000-07-12 11:27 ` Derek Homeier
2000-07-12 11:40   ` Benjamin Herrenschmidt
2000-07-12 15:40     ` Derek Homeier
2000-07-13 18:40     ` Derek Homeier
2000-07-12 11:37 Iain Sandoe
2000-07-12 12:36 ` Derek Homeier
2000-07-12 12:37 ` Geert Uytterhoeven

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=200007072232.XAA14475@hyperion.valhalla.net \
    --to=iain@sandoe.co.uk \
    --cc=larsi@gnus.org \
    --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).