All of lore.kernel.org
 help / color / mirror / Atom feed
From: r.marek@sh.cvut.cz (Rudolf Marek)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Winbond W83627HF - deactivated
Date: Thu, 06 Jul 2006 18:04:45 +0000	[thread overview]
Message-ID: <44AD50BD.5080803@sh.cvut.cz> (raw)
In-Reply-To: <44AD4B8C.1010002@sh.cvut.cz>

Albert wrote:
> Hi Rudolf
> On 06/07/06, Rudolf Marek <r.marek at sh.cvut.cz> wrote:
>> Maybe they just forgotten it to activate ....
>>
>> Enter configuration mode
>>
>> isaset -y -f 0x2e 0x87
> Data mismatch, wrote 0x87, read 0xff back.
> 
>> isaset -y -f 0x2e 0x87
> Data mismatch, wrote 0x87, read 0xff back.
> 
>> select logical device 0xb - hw monitor
>> isaset -y 0x2e 0x2f 0x07 0xb
> No issue here
> 
>> select base addr: (assuming 0x290 is safe, check /proc/ioports and see if the
>> 0x290 - 0x29F is empty)
> The address ranges are open
> 
>> isaset -y 0x2e 0x2f 0x61 0x90
>> isaset -y 0x2e 0x2f 0x60 0x2
> no issue here
> 
>> activate it:
>> isaset -y 0x2e 0x2f 0x30 0x1
> no issue here
> 
>> Leave configuration mode
>> isaset -y -f 0x2e 0xaa
> Data mismatch, wrote 0xaa, read 0xff back.
> 
> Seems to me that it is not there at all.

This errors are normal. Ignore them.

> I'm sending an email to Ampro to find out what is going on here. I'll
> let you know as soon as I have more info from them.

Well this sequence just reprograms the chip. After that you should be able to
modprobe the module, and sensors-detect should find it active.

(unless I made some mistake)

Can you re-run the sequence, and run this:
isaset -y -f 0x2e 0x87
isaset -y -f 0x2e 0x87
isaset -y 0x2e 0x2f 0x07 0xb
isadump -y 0x2e 0x2f
isaset -y -f 0x2e 0xaa

Thanks,
Regards
Rudolf


  parent reply	other threads:[~2006-07-06 18:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06 17:42 [lm-sensors] Winbond W83627HF - deactivated Rudolf Marek
2006-07-06 17:58 ` Albert
2006-07-06 18:04 ` Rudolf Marek [this message]
2006-07-06 18:10 ` Albert
2006-07-06 18:33 ` Rudolf Marek

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=44AD50BD.5080803@sh.cvut.cz \
    --to=r.marek@sh.cvut.cz \
    --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.