public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Ivica Ico Bukvic <ico@fuse.net>
Cc: daniel.ritz@gmx.ch, "'Thomas Charbonnel'" <thomas@undata.org>,
	ccheney@debian.org, linux-pcmcia@lists.infradead.org,
	alsa-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	"'Tim Blechmann'" <TimBlechmann@gmx.net>
Subject: Re: [linux-audio-user] snd-hdsp+cardbus+M6807 notebook=distortion -- First good news
Date: Sun, 11 Apr 2004 14:25:27 +0100	[thread overview]
Message-ID: <20040411142527.A29837@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040410033032.XOVD8029.smtp1.fuse.net@64BitBadass>; from ico@fuse.net on Fri, Apr 09, 2004 at 11:30:31PM -0400

(Note: I've dropped one of the mailing lists from the CC line because
they appear to have zero interest in my messages.)

On Fri, Apr 09, 2004 at 11:30:31PM -0400, Ivica Ico Bukvic wrote:
> I am aware that this burst stuff should be enabled on the 2.6 kernel,
> however I am still getting bad results.

Are you saying that you have tried the 2.6.5 kernel?

> The 06 to 04 may be the critical element as even when I have everything
> properly running in Win32, when I alter this number the distortion returns

$ setpci -s a.0 0xc9.b

will display the value of this register under Linux, and:

$ setpci -s a.0 0xc9.b=value

will set it to the desired value.  However, check that a.0 is the
cardbus bridge first by using:

$ lspci

> If I do figure out the problem in Linux and find out that a particular
> register is the issue, how can I make my linux box adjust this register at
> boot-time (a simple hack-like script in a form of a service comes to mind
> but I was hoping to perhaps see a more universal solution if possible)?

The correct solution is to put a quirk into the kernels yenta driver,
but we'd need the results from your testing first.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2004-04-11 13:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-10  1:47 [linux-audio-user] snd-hdsp+cardbus+M6807 notebook=distortion -- First good news Daniel Ritz
2004-04-10  3:30 ` Ivica Ico Bukvic
2004-04-11 13:25   ` Russell King [this message]
2004-04-11 16:08     ` Tim Blechmann
2004-04-11 23:45       ` Daniel Ritz
2004-04-12  1:39         ` [linux-audio-user] snd-hdsp+cardbus+M6807 notebook=distortion -- FIXED! Ivica Ico Bukvic
2004-04-12  7:28           ` Russell King
2004-04-12  9:08             ` David Hinds
2004-04-12  9:27               ` Russell King
2004-04-12 14:40             ` Ivica Ico Bukvic
2004-04-12 14:53               ` Russell King
2004-04-12 15:31                 ` Daniel Ritz
2004-04-12 15:38                   ` Russell King
2004-04-12 18:03                     ` Daniel Ritz
2004-04-14 13:41                     ` Tim Blechmann
2004-04-12 22:06               ` Tim Blechmann
2004-04-12 11:02           ` Tim Blechmann
2004-04-12 10:39             ` Russell King
2004-04-12 12:09               ` Tim Blechmann
2004-04-12 15:19           ` Daniel Ritz

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=20040411142527.A29837@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=TimBlechmann@gmx.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=ccheney@debian.org \
    --cc=daniel.ritz@gmx.ch \
    --cc=ico@fuse.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=thomas@undata.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