All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Intel DP35DP - P35 Sensor Support?
Date: Fri, 02 Nov 2007 10:32:52 +0000	[thread overview]
Message-ID: <20071102113252.2cbece00@hyperion.delvare> (raw)
In-Reply-To: <loom.20071015T022008-788@post.gmane.org>

On Wed, 31 Oct 2007 20:50:13 -0700, d. d. gmane wrote:
> Jean,  Hmm.. Strange results indeed.  It's odd that via BIOS HW 
> monitoring, that the values are available.  Has intel (un)intentionally 
> used a chip that's hard to access? 
> 
> When looking for open ioports, 0x0a00 was open, so I used it for all of 
> the rest of the testing.  Sadly, I think it's going to be difficult just 
> as you predicted.  Thank you for your time in looking at the prior 
> messages.  You're doing great work with lm sensors!
> 
> 
> 
> [root@skippy ]# isaset 0x2e 0x2f 0x07 0x08
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will write value 0x08 to address 0x07 of chip with address register 0x2e
> and data register 0x2f.
> Continue? [Y/n] Y
> 
> [root@skippy ]# isaset 0x2e 0x2f 0x60 0x0a
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will write value 0x0a to address 0x60 of chip with address register 0x2e
> and data register 0x2f.
> Continue? [Y/n] y
> 
> [root@skippy ]# isaset 0x2e 0x2f 0x61 0x00
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will write value 0x00 to address 0x61 of chip with address register 0x2e
> and data register 0x2f.
> Continue? [Y/n] Y
> 
> [root@skippy ]# isaset 0x2e 0x2f 0x30 0x01
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will write value 0x01 to address 0x30 of chip with address register 0x2e
> and data register 0x2f.
> Continue? [Y/n] Y
> 
> [root@skippy ]# isadump 0x2e 0x2f 0x08
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will probe address register 0x2e and data register 0x2f.
> Probing bank 8 using bank register 0x07.
> Continue? [Y/n] Y    
>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00: 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 41
> 20: f1 91 00 00 c1 01 00 91 00 91 00 00 00 00 00 00
> 30: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 70: 00 03 00 00 04 04 00 00 00 00 00 00 00 00 00 00
> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> f0: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 
> [root@skippy ]# isadump -f 0x0a00
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will probe address range 0xa00 to 0xaff.
> Continue? [Y/n] Y
>        0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 0a00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0a10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0a20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0a30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0a40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0a50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0a60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0a70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0a80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0a90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0aa0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ab0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ac0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ad0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ae0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0af0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [root@skippy ]#

I expected to see something here, but it's desperately empty. I have no
idea why enabling the I/O area didn't work as expected. And I don't
have the time to investigate further, sorry.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

      parent reply	other threads:[~2007-11-02 10:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-15  2:23 [lm-sensors] Intel DP35DP - P35 Sensor Support? d.d.
2007-10-28 14:26 ` Jean Delvare
2007-10-28 15:43 ` d. d. gmane
2007-10-28 15:58 ` d. d. gmane
2007-10-30 14:22 ` Jean Delvare
2007-10-30 22:26 ` d. d. gmane
2007-10-31 19:40 ` Jean Delvare
2007-11-01  3:50 ` d. d. gmane
2007-11-02 10:32 ` Jean Delvare [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=20071102113252.2cbece00@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=lm-sensors@vger.kernel.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.