linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dylan Griffiths <Dylan_G@bigfoot.com>
To: Robert Love <rml@ufl.edu>
Cc: Daniel Bertrand <d.bertrand@ieee.ca>,
	emu10k1-devel <emu10k1-devel@opensource.creative.com>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Emu10k1-devel] Re: Buggy emu10k1 drivers.
Date: Tue, 19 Jun 2001 16:57:26 -0600	[thread overview]
Message-ID: <3B2FD8D6.ED04B275@bigfoot.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0106171449470.2175-100000@kilrogg> <992822448.3798.6.camel@phantasy>

Robert Love wrote:
> > 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.
> 
> if the driver in the kernel is that old, could we try merging a newer
> release?  is there any reason why it has not been done yet?


Tried 2.4.5 and 2.2.19 with the same snapshot code (emu10k1-20010617.tar.gz)

2.4.5 works, 2.2.19 doesn't.

Maybe 2.2.19 has deeper problems with my hardware which aren't in the
driver, then, as identical code works on one and not the other.

--
    www.kuro5hin.org -- technology and culture, from the trenches.

  parent reply	other threads:[~2001-06-19 22:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-17 10:52 Dylan Griffiths
2001-06-17 22:17 ` [Emu10k1-devel] " Daniel Bertrand
2001-06-18  0:00   ` 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 [this message]
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=3B2FD8D6.ED04B275@bigfoot.com \
    --to=dylan_g@bigfoot.com \
    --cc=d.bertrand@ieee.ca \
    --cc=emu10k1-devel@opensource.creative.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@ufl.edu \
    --subject='Re: [Emu10k1-devel] Re: Buggy emu10k1 drivers.' \
    /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

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).