Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Dave Mielke <dave@mielke.cc>
To: linux-sound@vger.kernel.org
Subject: Re: OSS/Free /dev/audio full duplex sound format.
Date: Tue, 23 May 2000 12:03:25 +0000	[thread overview]
Message-ID: <marc-linux-sound-95908356417170@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-95903210912907@msgid-missing>

[quoted lines by paco@hydrofunk.org on May 22, 2000, at 15:29]

>As for why it switched on you in the first place... I have no idea.

I'm using the 2.2.12-20 kernel, as suplied by RedHat6.1, and the OSS/Free
drivers which it contains. If I open /dev/audio just for input (O_RDONLY), then
it delivers sound in mu_law format. If I open it just for output (O_WRONLY),
then it interprets sound in mu_law format. If I open it for both input and
output (O_RDWR), then it delivers sound in mu_law format, but, and this is my
problem, it interprets sound in unsigned 8-bit format (as though it were
/dev/dsp). My /etc/conf.modules contains the following:

   alias sound sb
   alias midi awe_wave
   options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330
   pre-install sound insmod sound dmabuf=1
   pre-install awe_wave modprobe opl3
   options opl3 io=0x388
   post-install awe_wave /bin/sfxload /etc/midi/GU11-ROM.SF2


Have I done anything wrong? Is it probably a bug in the sound driver, or might
the dmabuf=1 option to the sound module have something to do with it?

-- 
Dave Mielke           | 856 Grenon Avenue | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario   | Word of God. Please contact me
EMail: dave@mielke.cc | Canada  K2B 6G3   | if you're concerned about Hell.

  parent reply	other threads:[~2000-05-23 12:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-22 21:39 OSS/Free /dev/audio full duplex sound format Dave Mielke
2000-05-22 22:29 ` paco
2000-05-23 12:03 ` Dave Mielke [this message]
2000-05-23 12:37 ` Gianmaria Collazuol
2000-05-23 18:09 ` Jeff Garzik
2000-05-24 12:33 ` Dave Mielke

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=marc-linux-sound-95908356417170@msgid-missing \
    --to=dave@mielke.cc \
    --cc=linux-sound@vger.kernel.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