From: Daniel Ritz <daniel.ritz@gmx.ch>
To: Ivica Ico Bukvic <ico@fuse.net>
Cc: 'Thomas Charbonnel' <thomas@undata.org>,
ccheney@debian.org, linux-pcmcia@lists.infradead.org,
linux-kernel@vger.kernel.org,
'Russell King' <rmk+lkml@arm.linux.org.uk>,
alsa-devel@lists.sourceforge.net,
'Tim Blechmann' <TimBlechmann@gmx.net>,
David Hinds <dhinds@sonic.net>
Subject: Re: [linux-audio-user] snd-hdsp+cardbus+M6807 notebook=distortion -- FIXED!
Date: Mon, 12 Apr 2004 17:19:52 +0200 [thread overview]
Message-ID: <200404121719.52103.daniel.ritz@gmx.ch> (raw)
In-Reply-To: <20040412013949.NJOP1634.smtp3.fuse.net@64BitBadass>
On Monday 12 April 2004 03:39, Ivica Ico Bukvic wrote:
> **I've noted that when I use:
>
> setpci -s a.0 0x81.b
>
> after changing the value to 0xd0 (with setpci -s a.0 0x81.b=d0) it would
> tell me that it was equal to f0, yet the "hexdump -v /proc/bus/pci/00/0a.0"
> would tell me it was d0 after all (see the log below).
>
it's a single bit change from 0xd0 to 0xf0. it's bit 13 of the system control
register at 0x80. it's the socket activity bit that is read-clear. this means
writing to it has no effect, reading it clears the content. so the behavior
is normal...
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Ritz <daniel.ritz@gmx.ch>
To: "Ivica Ico Bukvic" <ico@fuse.net>
Cc: "'Thomas Charbonnel'" <thomas@undata.org>, <ccheney@debian.org>,
<linux-pcmcia@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
"'Russell King'" <rmk+lkml@arm.linux.org.uk>,
<alsa-devel@lists.sourceforge.net>,
"'Tim Blechmann'" <TimBlechmann@gmx.net>,
David Hinds <dhinds@sonic.net>
Subject: Re: [linux-audio-user] snd-hdsp+cardbus+M6807 notebook=distortion -- FIXED!
Date: Mon, 12 Apr 2004 17:19:52 +0200 [thread overview]
Message-ID: <200404121719.52103.daniel.ritz@gmx.ch> (raw)
In-Reply-To: <20040412013949.NJOP1634.smtp3.fuse.net@64BitBadass>
On Monday 12 April 2004 03:39, Ivica Ico Bukvic wrote:
> **I've noted that when I use:
>
> setpci -s a.0 0x81.b
>
> after changing the value to 0xd0 (with setpci -s a.0 0x81.b=d0) it would
> tell me that it was equal to f0, yet the "hexdump -v /proc/bus/pci/00/0a.0"
> would tell me it was d0 after all (see the log below).
>
it's a single bit change from 0xd0 to 0xf0. it's bit 13 of the system control
register at 0x80. it's the socket activity bit that is read-clear. this means
writing to it has no effect, reading it clears the content. so the behavior
is normal...
next prev parent reply other threads:[~2004-04-12 15:19 UTC|newest]
Thread overview: 34+ 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-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 1:39 ` Ivica Ico Bukvic
2004-04-12 5:24 ` aplay playback-pointer Mathieu Rondonneau
2004-04-12 15:45 ` start stop Mathieu Rondonneau
2004-04-12 16:58 ` start stop resolved Mathieu Rondonneau
2004-04-12 17:59 ` start stop Jaroslav Kysela
2004-04-13 16:25 ` aplay playback-pointer Clemens Ladisch
2004-04-14 3:06 ` aplay noise Mathieu Rondonneau
2004-04-17 21:06 ` arecord wav file, buffer different Mathieu Rondonneau
2004-04-20 9:08 ` Clemens Ladisch
2004-04-12 7:28 ` [linux-audio-user] snd-hdsp+cardbus+M6807 notebook=distortion -- FIXED! 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: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 22:06 ` Tim Blechmann
2004-04-12 11:02 ` 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 [this message]
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=200404121719.52103.daniel.ritz@gmx.ch \
--to=daniel.ritz@gmx.ch \
--cc=TimBlechmann@gmx.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=ccheney@debian.org \
--cc=dhinds@sonic.net \
--cc=ico@fuse.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=rmk+lkml@arm.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.