From: Robert Love <rml@tech9.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4.7-ac11: Updated emu10k1 driver
Date: 10 Aug 2001 19:26:15 -0400 [thread overview]
Message-ID: <997485978.898.33.camel@phantasy> (raw)
In-Reply-To: <E15VLWl-0001qB-00@the-village.bc.nu>
In-Reply-To: <E15VLWl-0001qB-00@the-village.bc.nu>
On 11 Aug 2001 00:17:15 +0100, Alan Cox wrote:
> > Alan, please consider merging this. I know it is big but how else will
> > we ever get it back in sync? I will work to keep it up to date if it
> > falls behind again.
>
> Is there ar reason the maintainer hasnt submitted it yet ?
The "maintainer" is listed as Creative. They have not updated anything
in a year (in the kernel tree; their CVS tree gets frequent updates).
There was a thread a month or so ago where the emu10k1 was mentioned and
the reply was "get the updated driver" -- I asked why the kernel driver
was so old and I was told a patch was floating around but it had not
been merged. I have never seen this patch, so I replied I would do it
myself.
It took awhile but here it is.
I don't think there is a reason as in "its beta code" or "it needs to
remain a module for licensing reasons" -- its solid (admittedly better
than what is in there now, has more features, and is GLPed).
With the exception of the two modifications listed, its right from the
Creative CVS tree. It compiles. It works for me.
--
Robert M. Love
rml at ufl.edu
rml at tech9.net
next prev parent reply other threads:[~2001-08-10 23:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-10 23:10 [PATCH] 2.4.7-ac11: Updated emu10k1 driver Robert Love
2001-08-10 23:17 ` Alan Cox
2001-08-10 23:26 ` Robert Love [this message]
2001-08-10 23:31 ` Alan Cox
2001-08-10 23:38 ` Robert Love
2001-08-11 2:18 ` Robert Love
2001-08-11 3:29 ` John Cavan
2001-08-11 3:42 ` Robert Love
2001-08-11 4:30 ` Robert Love
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=997485978.898.33.camel@phantasy \
--to=rml@tech9.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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