From: David Hinds <dhinds@sonic.net>
To: Ivica Ico Bukvic <ico@fuse.net>,
daniel.ritz@gmx.ch, "'Tim Blechmann'" <TimBlechmann@gmx.net>,
"'Thomas Charbonnel'" <thomas@undata.org>,
ccheney@debian.org, linux-pcmcia@lists.infradead.org,
alsa-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [linux-audio-user] snd-hdsp+cardbus+M6807 notebook=distortion -- FIXED!
Date: Mon, 12 Apr 2004 02:08:17 -0700 [thread overview]
Message-ID: <20040412090817.GA3158@sonic.net> (raw)
In-Reply-To: <20040412082801.A3972@flint.arm.linux.org.uk>
On Mon, Apr 12, 2004 at 08:28:01AM +0100, Russell King wrote:
>
> > 3) FOR FURTHER INVESTIGATION: Does linux hdsp driver force the f0
> > value upon the 0x81 register or is it that in Linux one simply
> > cannot select d0 value for whatever reason
>
> I suspect it may be caused by using a byte access to a longword-sized
> register. 0x81 is supposed to be accessed via:
>
> setpci -s a.0 0x80.l
>
> which of course means its bits 8 to 15.
I don't think so; I'm not sure what the PCI spec has to say about it,
but I have not had problems doing byte reads/writes for longer PCI
configuration registers. Bit 9 of the sysctl register for the TI 1410
is "socket activity"; it is read only and is cleared after each read.
The key change is setting bit 14 (enable upstream burst reads).
Regarding the register at 0xc9, I don't think that is defined in any
TI bridge data sheet; it is in a "reserved" range.
-- Dave
next prev parent reply other threads:[~2004-04-12 9:08 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
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 [this message]
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=20040412090817.GA3158@sonic.net \
--to=dhinds@sonic.net \
--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