All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeramy B Smith <jsmith@penguinppc.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: SndConfig for Linux/PPC
Date: Fri, 24 Sep 1999 10:46:06 -0500	[thread overview]
Message-ID: <99092411060800.00471@lintop> (raw)


I've been thinking about making sndconfig run on linuxppc. 
A. rip out the sun/sbus code
B. remove defs for isa cards
C. remove the defs for pci cards that don't work on linuxppc
D. add dma sound def
E. debug, debug, debug

D is giving me the most problems, i guess i shouldnt have to probe but one of
the variabes in the defs is a bustype (isa, pci, sbus). Any ideas what I should
do and what header I would need?

I think a utility like this would help people test their sound system and be
able to diagnose if their sound problems are caused by kernel driver issues or
software (esd, etc) problems.

A utility like this might even be able to incorporate Ben's work at mapping
inputs/outputs by having a machine select screen if dmasound is present. The
user would choose his machine and the correct input/output settings would be
used.


Please feel free to tell me if I'm going about this bass-ackwards ;).



Jeramy B Smith
PenguinPPC.org
jsmith@penguinppc.org

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

             reply	other threads:[~1999-09-24 15:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-24 15:46 Jeramy B Smith [this message]
1999-09-24 17:57 ` SndConfig for Linux/PPC Anirudh Joshi
1999-09-26 15:26   ` Dan Malek
1999-09-27  8:57     ` Benjamin Herrenschmidt
1999-09-26 20:10   ` Geert Uytterhoeven
1999-09-26 21:35     ` Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
1999-09-27 17:19 jeramy b smith
1999-09-27 17:24 ` Geert Uytterhoeven
     [not found] <37F32EBC.FAFD82E2@zib.de>
1999-09-30  9:41 ` 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=99092411060800.00471@lintop \
    --to=jsmith@penguinppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.