From: Paul Davis <paul@linuxaudiosystems.com>
To: "Ivica Ico Bukvic" <ico@fuse.net>
Cc: "'A list for linux audio users'"
<linux-audio-user@music.columbia.edu>,
"'Russell King'" <rmk+lkml@arm.linux.org.uk>,
alsa-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
linux-pcmcia@lists.infradead.org,
"'Thomas Charbonnel'" <thomas@undata.org>,
ccheney@debian.org, "'Tim Blechmann'" <TimBlechmann@gmx.net>
Subject: Re: [Alsa-devel] RE: [linux-audio-user] snd-hdsp+cardbus+M6807 notebook=distortion -- First good news!
Date: Fri, 09 Apr 2004 18:49:23 -0400 [thread overview]
Message-ID: <200404092249.i39MnNwx025652@dhin.linuxaudiosystems.com> (raw)
In-Reply-To: Your message of "Fri, 09 Apr 2004 18:25:47 EDT." <20040409222552.MLZG22605.smtp2.fuse.net@64BitBadass>
>Well, if there is a way of monitoring these hex registers for various
>hardware in Linux I could try to compare their state upon initialization in
>Linux to that one in Windows (since in both situations they share the same
>IRQ, at least on my notebook) and forward this info to you guys.
>
>So my question at this point is, is there such hex-editor in Linux that
>allows this kind of monitoring and if so where can I obtain it?
i would imagine that you have it already, though its cmdline: setpci
(and lspci -vv for the display side, so to speak).
not sure if this is really the equivalent, but i suspect that it is.
--p
next prev parent reply other threads:[~2004-04-09 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-03 4:17 [linux-audio-user] snd-hdsp+cardbus=distortion -- the sagacontinues (cardbus driver=culprit?) MORE UPDATE Ivica Ico Bukvic
2004-04-09 22:25 ` [linux-audio-user] snd-hdsp+cardbus+M6807 notebook=distortion -- First good news! Ivica Ico Bukvic
2004-04-09 22:49 ` Paul Davis [this message]
2004-04-10 3:28 ` [Alsa-devel] " Ivica Ico Bukvic
2004-04-10 23:53 ` Tim Blechmann
2004-04-11 14:07 ` Tim Blechmann
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=200404092249.i39MnNwx025652@dhin.linuxaudiosystems.com \
--to=paul@linuxaudiosystems.com \
--cc=TimBlechmann@gmx.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=ccheney@debian.org \
--cc=ico@fuse.net \
--cc=linux-audio-user@music.columbia.edu \
--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 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®