Message-ID: <3D5A8948.7060201@yahoo.com>
Date: Wed, 14 Aug 2002 20:46:00 +0400
From: Stas Sergeev <stssppnn@yahoo.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2.1) Gecko/20010901
MIME-Version: 1.0
To: Michael Knigge <Michael.Knigge@set-software.de>
CC: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] New PC-Speaker driver
Content-Type: text/plain; charset=KOI8-R; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1719
Lines: 44

Hello.

Michael Knigge wrote:
 > Oh, I would love to see that thing in the Standard-Kernel....
Yes, I'd also like to see it there, but
for now I don't know if/when this can be
achieved.
As pointed by David Woodhouse (from whom
I've stolen the code just because I felt
it was not updated for tooo long:) the main
problem is that this driver, dispite no longer
touching irq.c (the latest patch doesn't touch
it) still speeds up the timer (this is
unavoidable). Well, as in 2.5 HZ is configurable,
this is probably a way to go (but I haven't
yet played with 2.5).
However, since 2.5 uses ALSA rather than OSS, I
think I have to make an ALSA port before thinking
about an integration. But even if this is done,
somehow this must be dealt with:
http://www.alsa-project.org/archive/alsa-user/msg04284.html

So there are anough of long-term issues and for
2.4 solving them is not possible.
My goal for 2.4 is to get rid of the native fops
and use OSS fops instead (USE_OSS_FOPS in pcsp.h
must be set to 1) but even this doesn't work very
well: when CPU load is high, my output routines
are called with the sound buffer entirely zeroed
out! I don't know who wipes out the buffer on a
high CPU load and as the problem is deeply buried
in the OSS internals (not in my driver) I don't
know how to deal with that.

 > Thanks for your work! This is something I was missing for
 > years!
Thanks:) I'll try to make this driver acceptable
for inclusion, but this will take *a lot* of time.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/