From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: pawel.worach@mysun.com
Cc: Chmouel Boudjnah <chmouel@mandrakesoft.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: i810_audio broken?
Date: Mon, 23 Apr 2001 18:59:33 -0400 [thread overview]
Message-ID: <3AE4B3D5.E026E291@mandrakesoft.com> (raw)
In-Reply-To: <3829d3430e.3430e3829d@mysun.com>
Pawel Worach wrote:
>
> Ok building mpg123 without eSound worked for me too,
> so guess this is not a Linux kernel issue, sorry for this.
>
> I tried the fstodell hack but it seems to be obsoluted.
> Now it works without any tweaks.
>
> eSound sux?
Are you guys running esd with any special arguments?
esd needs a special argument, -r RATE [iirc], in order to tell esd that
it is dealing with a locked rate codec.
--
Jeff Garzik | The difference between America and England is that
Building 1024 | the English think 100 miles is a long distance and
MandrakeSoft | the Americans think 100 years is a long time.
| (random fortune)
next prev parent reply other threads:[~2001-04-23 23:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 22:39 i810_audio broken? Pawel Worach
2001-04-23 22:59 ` Jeff Garzik [this message]
2001-04-23 23:20 ` i810_audio broken?t Alan Cox
2001-04-23 23:08 ` i810_audio broken? David Woodhouse
2001-04-23 23:17 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-04-23 23:04 Pawel Worach
2001-04-23 22:56 Pawel Worach
2001-04-23 22:30 Pawel Worach
2001-04-23 21:48 Pawel Worach
2001-04-23 22:07 ` Jeff Garzik
2001-04-23 23:02 ` Alan Cox
2001-04-23 23:34 ` Chmouel Boudjnah
2001-04-24 2:44 ` Doug Ledford
2001-04-23 18:15 Pawel Worach
2001-04-23 19:53 ` Alan Cox
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=3AE4B3D5.E026E291@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chmouel@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pawel.worach@mysun.com \
/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.