public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Bernat <bernat@free.fr>
To: "Nix N. Nix" <nix@go-nix.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA KT266 and SBLive! (emu10k1)
Date: Sun, 27 Jan 2002 10:59:42 +0100	[thread overview]
Message-ID: <m3lmek2jxt.fsf@neo.loria> (raw)
In-Reply-To: <1012086718.11336.91.camel@tux>
In-Reply-To: <1012086718.11336.91.camel@tux> ("Nix N. Nix"'s message of "26 Jan 2002 18:11:53 -0500")

OoO En cette nuit nuageuse du dimanche 27 janvier 2002, vers 00:11,
"Nix N. Nix" <nix@go-nix.ca> disait:

> 00:0e.0 Multimedia audio controller: Creative Labs SB Live! EMU10000
> (rev 05)
> 	Subsystem: Creative Labs CT4850 SBLive! Value
> 	Flags: bus master, medium devsel, latency 32, IRQ 5
> 	I/O ports at b000 [size=32]
> 	Capabilities: <available only to root>

You may try /sbin/setpci -v -s 00:0e.0 0D.B=40

Check http://www.networking.tzo.com/net/software/readme/faqvl019.htm
and http://www.uwsg.iu.edu/hypermail/linux/kernel/0112.3/0922.html

The first one is a patch for Windows to correct the problem, it is
called "VIA latency patch" since it used to only modify latency. It is
closed source so it is difficult to see if the correction towards the
sound card is about latency (so my command line is useless).

The second one is a post from the author of the corresponding VIA
latency patch under Linux, you may want to try it (and to tweak it if
you don't have a KT266A).

However, the problem seems not IRQ related, so you may want to try
another slots for your sound card.
-- 
Say what you mean, simply and directly.
            - The Elements of Programming Style (Kernighan & Plaugher)

      parent reply	other threads:[~2002-01-27 10:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-26 23:11 VIA KT266 and SBLive! (emu10k1) Nix N. Nix
2002-01-27  0:03 ` Martin Mačok
2002-01-27 23:18   ` Nix N. Nix
2002-01-29  5:58   ` Nix N. Nix
2002-01-27  9:59 ` Vincent Bernat [this message]

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=m3lmek2jxt.fsf@neo.loria \
    --to=bernat@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nix@go-nix.ca \
    /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