On Fri, Nov 16, 2001 at 10:14:28AM +0100, Maarten de Boer wrote:
> > CONFIG_MK7=y
> >
> > Did I read correctly that some 3DNow instructions cause latency issues?
>
> That's what Roger Larsson suggested when I showed bad latency results.
> Compiling for 586 solved that problem for me, and I find
Hi,
This patch fixes a build problem I was having with the latest CVS
version of ALSA and gcc 3.0.2. Specifically, the "read_unlock"
function, which is really a preprocessor #define, wasn't being
expanded within the snd_runtime_check() macros in mixer_oss.c.
Chris
--- alsa-driver/include/drive
On Thu, Nov 15, 2001 at 05:12:38PM -0500, Thomas Hood wrote:
> > Am I the only one with this problem?
> You're not the only one. I have exactly the same problem.
> Are you using devfs? I am. Could it be a devfs race of
> some sort?
No, I don't use it.
Stefan
_
this patch makes ALSA treat the hammerfall the exact same way that
ASIO does, which makes sense to do given RME's claims about the card.
the hw pointer is reduced to essentially a 1 bit value - its either at
the start of the first period or at the start of the second. there are
no values between
On Fri, Nov 16, 2001 at 10:41:58AM +0100, Takashi Iwai wrote:
> At Fri, 16 Nov 2001 09:39:23 +0100,
> Maarten de Boer wrote:
> >
> > Takashi Iwai <[EMAIL PROTECTED]> wrote:
> > > I think 2.4.14 or 15pre are ok, too. The same LL patch should work.
> >
> > I applied the 2.4.15pre1AA patch on 2.4.
At Fri, 16 Nov 2001 14:21:33 -,
James Courtier-Dutton wrote:
>
> kernel 2.4.9
> I doubt it is a kernel problem, because previous CVS's had no problems.
Hmm, I guess the last change in include/driver.h wrt variable
arguments in macro is involved with this. Please try to check out the
last re
kernel 2.4.9
I doubt it is a kernel problem, because previous CVS's had no problems.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Steve Harris
> Sent: 16 November 2001 13:42
> To: ALSA dev list
> Subject: Re: [Alsa-devel] Unresolved symbols in sn
On Friday 16 November 2001 12:59, James Courtier-Dutton wrote:
> I have this exact same problem with a recent CVS.
> I never had it with previous CVS's, (about one month ago).
> I am using an emu10k1 SB Live.
> I don't understand why it has a problem with read_unlock, because other
> modules use r
Andre Pang <[EMAIL PROTECTED]> wrote:
>> I am thinking of setting up a webpage, where people can post
>> their latencytest results, so we can keep an inventory of
>> the several combinations, categorising on:
>
> This is a great idea. I actually started re-writing the latency
> testing harness s
On Fri, Nov 16, 2001 at 12:59:11PM -, James Courtier-Dutton wrote:
> I have this exact same problem with a recent CVS.
> I never had it with previous CVS's, (about one month ago).
> I am using an emu10k1 SB Live.
> I don't understand why it has a problem with read_unlock, because other
> modul
On Fri, Nov 16, 2001 at 10:26:23AM +0100, Maarten de Boer wrote:
> I am thinking of setting up a webpage, where people can post
> their latencytest results, so we can keep an inventory of
> the several combinations, categorising on:
This is a great idea. I actually started re-writing the latenc
I have this exact same problem with a recent CVS.
I never had it with previous CVS's, (about one month ago).
I am using an emu10k1 SB Live.
I don't understand why it has a problem with read_unlock, because other
modules use read_unlock without any problem.
Cheers
James
> -Original Message--
On Thu, 15 Nov 2001, Anders Torger wrote:
> On Thursday 15 November 2001 23.13, you wrote:
> > latency.c probably should handle this case more gracefully. But the core
> > issue is: why doesn't the RME96 driver adjust buffer-size and period
> > properly? Are there hardware-constraints with the RM
On Thu, 15 Nov 2001, Wolfgang Hoffmann wrote:
> Am Dienstag, 13. November 2001 23:04 schrieb Wolfgang Hoffmann:
> > Am Mittwoch, 7. November 2001 22:33 schrieb Anders Torger:
> > > Hmmm... strange... I use the driver almost every day, and I have not seen
> > > any problems. I also wrote the drive
Well of course :)
Can you also put there a comprehensive mini-howto
about how we should run which test to get these results ?
kind regards
vini
On Fri, Nov 16, 2001 at 10:26:23AM +0100, Maarten de Boer wrote:
>Hello,
>
>I am thinking of setting up a webpage, where people can post
>their latency
At Fri, 16 Nov 2001 09:39:23 +0100,
Maarten de Boer wrote:
>
> Takashi Iwai <[EMAIL PROTECTED]> wrote:
> > I think 2.4.14 or 15pre are ok, too. The same LL patch should work.
>
> I applied the 2.4.15pre1AA patch on 2.4.14 (with some very small
> modifications), and the results are horrible.
>
At Fri, 16 Nov 2001 10:26:23 +0100,
Maarten de Boer wrote:
>
> Hello,
>
> I am thinking of setting up a webpage, where people can post
> their latencytest results, so we can keep an inventory of
> the several combinations, categorising on:
>
> - processor
> - SMP
> - kernel version
> - kernel
Hello,
I am thinking of setting up a webpage, where people can post
their latencytest results, so we can keep an inventory of
the several combinations, categorising on:
- processor
- SMP
- kernel version
- kernel patch
- kernel configuration
--- processor
--- SMP
--- ??
- tuning
--- vm
--- hdp
On Thu, 15 Nov 2001 21:47:02 +0100
Andy Lo-A-Foe <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 15, 2001 at 07:54:41PM +0100, Maarten de Boer wrote:
>
> > Your results look good. For what processor did you compile your kernel?
>
> CONFIG_MK7=y
>
> Did I read correctly that some 3DNow instructions ca
Vincent Touquet <[EMAIL PROTECTED]> wrote:
> I have an Athlon too.
> Is it true that there are issues with the lowlatency patches
> (Andrew Morton's as well as the kernel pre-emption patches) and the
> optimizations used in the kernel for the Athlon processor ?
>
> If so, do I need to compile for
Takashi Iwai <[EMAIL PROTECTED]> wrote:
> I think 2.4.14 or 15pre are ok, too. The same LL patch should work.
I applied the 2.4.15pre1AA patch on 2.4.14 (with some very small
modifications), and the results are horrible.
http://www.iua.upf.es/~mdeboer/latency/2.4.14-15pre1AA/3x256.html
Maarten
21 matches
Mail list logo
