From: Takashi Iwai <tiwai@suse.de>
To: J Sloan <jjs@pobox.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jamie Lokier <lk@tantalophile.demon.co.uk>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
Zwane Mwaikambo <zwane@linux.realnet.co.sz>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: OSS driver cleanups.
Date: Wed, 05 Dec 2001 12:05:50 +0100 [thread overview]
Message-ID: <s5hwv02lyep.wl@alsa1.suse.de> (raw)
In-Reply-To: <3C0DBD4F.E7AC50A3@pobox.com>
In-Reply-To: <E16BJ58-0002hg-00@the-village.bc.nu> <3C0DBD4F.E7AC50A3@pobox.com>
At Tue, 04 Dec 2001 22:23:11 -0800,
J Sloan wrote:
>
> Alan Cox wrote:
>
> > > Not least because I have reports from my housemate that ALSA drivers are
> > > a b*tch to set up. To be done only if there isn't an OSS driver for
> > > your card. Whereis with OSS you just load a module and its done.
> >
> > Thats already a "must fix"
>
> Is the really bad latency reported on this list
> as coming from the alsa drivers also "must fix"?
At the last time I've tried, the bad latency happened only on OSS
emulation. There must be some small difference of behavior between
OSS and emulation. Yes, this is "must fix", too.
On ALSA native mode you get even lower latency than OSS.
IIRC the chip reported on lkml is ymfpci - it cannot achieve latency
lower than 256/48000 = 5.33 msec, anyway, due to h/w limit..
Takashi
next prev parent reply other threads:[~2001-12-05 11:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 9:11 OSS driver cleanups Zwane Mwaikambo
2001-12-03 9:30 ` Alan Cox
2001-12-04 0:13 ` Jeff Garzik
2001-12-04 16:49 ` Jamie Lokier
2001-12-04 16:55 ` Jeff Garzik
2001-12-04 17:29 ` [s-h] " Takashi Iwai
2001-12-04 16:34 ` gmack
2001-12-04 17:42 ` Alan Cox
2001-12-04 17:10 ` Alan Cox
2001-12-04 17:15 ` Jordan Breeding
2001-12-04 17:42 ` Jeff Garzik
2001-12-04 20:24 ` Dan Hollis
2001-12-05 6:23 ` J Sloan
2001-12-05 11:05 ` Takashi Iwai [this message]
2001-12-04 1:18 ` John Gluck
2001-12-04 9:50 ` Zwane Mwaikambo
2001-12-04 14:35 ` Jeff Garzik
2001-12-04 18:42 ` Piter Punk
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=s5hwv02lyep.wl@alsa1.suse.de \
--to=tiwai@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=jjs@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@tantalophile.demon.co.uk \
--cc=zwane@linux.realnet.co.sz \
/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