linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: esound and 2.2's dmasound
Date: Wed, 3 Jan 2001 21:53:20 +0100	[thread overview]
Message-ID: <20010103215320.A4451@suse.de> (raw)
In-Reply-To: <200101031947.TAA19299@hyperion.valhalla.net>; from iain@sandoe.co.uk on Wed, Jan 03, 2001 at 07:47:36PM +0000


On Wed, Jan 03, Iain Sandoe wrote:

> (and also there's the start of an ALSA version - from a posting on the
> ALSA-dev list yesterday)...

There are results.
ftp://ftp.suse.com/pub/suse/ppc/kernel/2.2.18/k_pmac-2.2.18-0.ppc.rpm
http://penguinppc.org/~olaf/alsa/alsa-0.5.9-38.ppc.rpm
http://penguinppc.org/~olaf/alsa/alsamixergui-0.5.7-0.ppc.rpm
ftp://ftp.suse.com/pub/suse/ppc/7.0/suse/xdev2/fltk.rpm
http://penguinppc.org/~olaf/alsa/modules-alsa.conf

echo "include /etc/modules-alsa.conf" >> /etc/modules.conf
(disable dmasound.o, just unload it)


everything that works with dmasound.o should still work.
iMac sound works (internal speaker), B&W internal speaker. iBook doesnt
work yet, but this guy had the iBook only for a few minutes ;)

There are no alsa modules in
ftp.suse.com/pub/suse/ppc/kernel/2.4.0-test13/k_ppc23-2.4.0_test13pre3-0.ppc.rpm
because the Makefile was buggy, I will update it these days.


Please test it, I'm not a multimedia guy ;)


Gruss Olaf

--
 $ man clone

BUGS
       Main feature not yet implemented...

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

  reply	other threads:[~2001-01-03 20:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-03 19:47 esound and 2.2's dmasound Iain Sandoe
2001-01-03 20:53 ` Olaf Hering [this message]
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=20010103215320.A4451@suse.de \
    --to=olh@suse.de \
    --cc=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).