linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Bertrand <d.bertrand@ieee.ca>
To: Dylan Griffiths <Dylan_G@bigfoot.com>
Cc: emu10k1-devel <emu10k1-devel@opensource.creative.com>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Emu10k1-devel] Re: Buggy emu10k1 drivers.
Date: Sun, 17 Jun 2001 15:17:41 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.33.0106171449470.2175-100000@kilrogg> (raw)
In-Reply-To: <3B2C8BFE.299BD47@bigfoot.com>

On Sun, 17 Jun 2001, Dylan Griffiths wrote:

> 	Kernel 2.4.5 has a working emu10k1 driver (all apps which hung with
> 2.2.19's driver worked fine, none of the working ones stopped working).
> Could we perhaps see this backported to the 2.2.20 prepatches so that us 2.2
> lovers can enjoy working sound?

Can you give the CVS driver a try? Snapshots are available here:
http://opensource.creative.com/snapshot.html

The driver in the kernel is based on a CVS snapshot from last summer, the
problem may be fixed in CVS. Also, the CVS driver is a common driver for
2.2 and 2.4 (with some #ifdef), so it may be useful to see if it works for
you on 2.4.5 but not on 2.2.19.


-- 
Daniel Bertrand


  reply	other threads:[~2001-06-17 22:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-17 10:52 Buggy emu10k1 drivers Dylan Griffiths
2001-06-17 22:17 ` Daniel Bertrand [this message]
2001-06-18  0:00   ` [Emu10k1-devel] " Robert Love
2001-06-18  0:25     ` Daniel Bertrand
2001-06-18  0:33       ` Robert Love
2001-06-18  2:22       ` Joseph Carter
2001-06-19 22:57     ` Dylan Griffiths
2001-06-18  0:01   ` Nerijus Baliunas

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=Pine.LNX.4.33.0106171449470.2175-100000@kilrogg \
    --to=d.bertrand@ieee.ca \
    --cc=Dylan_G@bigfoot.com \
    --cc=emu10k1-devel@opensource.creative.com \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).