linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joseph Carter <knghtbrd@d2dc.net>
To: Daniel Bertrand <d.bertrand@ieee.ca>
Cc: Robert Love <rml@ufl.edu>, Dylan Griffiths <Dylan_G@bigfoot.com>,
	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 19:22:11 -0700	[thread overview]
Message-ID: <20010617192211.A15116@debian.org> (raw)
In-Reply-To: <992822448.3798.6.camel@phantasy> <Pine.LNX.4.33.0106171707150.2262-100000@kilrogg>
In-Reply-To: <Pine.LNX.4.33.0106171707150.2262-100000@kilrogg>; from d.bertrand@ieee.ca on Sun, Jun 17, 2001 at 05:25:11PM -0700

[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]

On Sun, Jun 17, 2001 at 05:25:11PM -0700, Daniel Bertrand wrote:
> > 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?
> 
> A patch was submitted to Alan in April but appears to have never made it
> in, I'm not sure what his reason was.

Right after it was made I found out that it had broken mmap.  Rui sent me
a patch, then another.  Seems he has committed most of that patch to CVS
now but there are differences still.  I'm not sure if the differences are
actually still important, I may have to try building fresh CVS to be sure.

I don't know for sure if that's why Alan hasn't applied the new driver,
but it was an issue that would have broken the patch he was given which is
supposed to be fixed now.  I'm thinking Rui has gotten busy in the
meantime since he's been rather quiet lately.

-- 
Joseph Carter <knghtbrd@d2dc.net>                   Free software developer

<jt> should a bug be marked critical if it only affects one arch?
<james-workaway> jt: rc for that arch maybe, but those kind of arch
                 specific bugs are rare...
<jt> not when it's caused by a bug in gcc
<doogie> jt: get gcc removed from that arch. :)


[-- Attachment #2: Type: application/pgp-signature, Size: 273 bytes --]

  parent reply	other threads:[~2001-06-18  2: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 ` [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 [this message]
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=20010617192211.A15116@debian.org \
    --to=knghtbrd@d2dc.net \
    --cc=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 \
    /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).