All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Chmouel Boudjnah <chmouel@mandrakesoft.com>
Cc: pawel.worach@mysun.com, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: i810_audio broken?
Date: Mon, 23 Apr 2001 22:44:15 -0400	[thread overview]
Message-ID: <3AE4E87F.FDE83136@redhat.com> (raw)
In-Reply-To: <3804336226.3622638043@mysun.com> <m3n197ur5i.fsf@giants.mandrakesoft.com>

Chmouel Boudjnah wrote:
> 
> "Pawel Worach" <pworach@mysun.com> writes:
> 
> > I was using mpg123 (xmms and c/o does exactly the same)
> > if I run it like this Moby sounds very stupid... :)
> 
> i got the same problem when using mpg123 compiled with esd on my dell
> workstation (which has a need to have set explictely to a clocking of
> 41194 via ftsodell option), compiling without esd seems fix the prob
> for me.

The latest i810 driver does away with the ftsodell option entirely and should
work on your laptop without having to do anything special.

-- 

 Doug Ledford <dledford@redhat.com>  http://people.redhat.com/dledford
      Please check my web site for aic7xxx updates/answers before
                      e-mailing me about problems

  reply	other threads:[~2001-04-24  2:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-23 21:48 i810_audio broken? 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 [this message]
  -- 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:39 Pawel Worach
2001-04-23 22:59 ` Jeff Garzik
2001-04-23 23:08 ` David Woodhouse
2001-04-23 23:17 ` Alan Cox
2001-04-23 22:30 Pawel Worach
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=3AE4E87F.FDE83136@redhat.com \
    --to=dledford@redhat.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.