mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dominique Dumont <domi.dumont@free.fr>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-user <alsa-user@lists.sourceforge.net>,
	Francesco Peeters <Francesco@FamPeeters.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Alsa-user] PCM distorsion snapshots from SATA/ALSA conflict
Date: Sat, 14 Oct 2006 17:04:03 +0200	[thread overview]
Message-ID: <87hcy76isc.fsf@gandalf.hd.free.fr> (raw)
In-Reply-To: <1160325674.17615.107.camel@mindpipe> (Lee Revell's message of "Sun, 08 Oct 2006 12:41:13 -0400")

Lee Revell <rlrevell@joe-job.com> writes:

> (it's probably a bad idea to attach .jpgs to a LKML post - please post
> them on the web and send a URL)

(ok. But is there a site that will guarantee the availability of the
jpg attachments when people are searching the lklm or alsa archives ?
)

> You seem to be using a period size of 256 samples - any change if you
> use a larger period size?

Unless I'm wrong, you want me to test the PCM output while modifying
the --period option of speaker-test.

So I've tested this command:
  speaker-test -D iec958 -c 2 -f 1000 -p 4096 -t sine -s 2

No change: I still have a lot of spikes in the sine wave.

> Any change if you use setpci to increase LATENCY_TIMER for the SBLive!
> card?

To be sure I've done the correct tests, here are the commands are used:

$ lspci
[...]
01:07.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a)
01:07.1 Input device controller: Creative Labs SB Live! Game Port (rev 0a)
[...]
01:0b.0 RAID bus controller: Silicon Image, Inc. SiI 3112 [SATALink/SATARaid] Serial ATA Controller (rev 02)

$ sudo setpci -s 01:07.0 latency_timer=80
$ sudo setpci -s 01:07.0 latency_timer=f8
$ sudo setpci -s 01:0b.0 latency_timer=10

No change at all :-(

Cheers


  reply	other threads:[~2006-10-14 15:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-25 11:55 Pb with simultaneous SATA and ALSA I/O Dominique Dumont
2006-09-25 12:17 ` [Alsa-user] " Francesco Peeters
2006-10-05 20:42   ` Dominique Dumont
2006-10-05 20:45     ` Lee Revell
2006-10-05 21:01       ` Dominique Dumont
2006-10-05 21:12         ` Lee Revell
2006-10-05 21:50           ` Alan Cox
2006-10-08 10:38             ` PCM distorsion snapshots from SATA/ALSA conflict (was: [Alsa-user] Pb with simultaneous SATA and ALSA I/O) Dominique Dumont
2006-10-08 16:41               ` Lee Revell
2006-10-14 15:04                 ` Dominique Dumont [this message]
2006-10-05 21:18         ` [Alsa-user] Pb with simultaneous SATA and ALSA I/O Lee Revell
2006-10-07 12:03           ` Dominique Dumont
2006-10-07 17:08             ` Lee Revell
2006-10-05 21:52       ` Alan Cox
2006-10-05 21:45         ` Lee Revell
2006-09-25 14:38 ` Lennart Sorensen
2006-09-25 14:50   ` Lee Revell
2006-09-26 14:29     ` Thierry Vignaud
2006-09-26 14:37     ` Dominique Dumont
2006-09-26 14:44       ` Lee Revell
2006-10-04 10:45     ` [Alsa-user] " Dominique Dumont

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=87hcy76isc.fsf@gandalf.hd.free.fr \
    --to=domi.dumont@free.fr \
    --cc=Francesco@FamPeeters.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    /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

all inboxes | Powered by JetHome®