All of lore.kernel.org
 help / color / mirror / Atom feed
From: mds@mds.gotdns.com (Mark Studebaker)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] PC87591x
Date: Thu, 22 Dec 2005 21:25:24 +0000	[thread overview]
Message-ID: <43AB19C4.8050608@mds.gotdns.com> (raw)
In-Reply-To: <42418B75.3080707@web.de>

unless the FW is implementing a standard IPMI-BMC or there is a 
published interface for the firmware, it sounds like
going through ACPI is the only solution.

Enrico Bartky wrote:
> Hi,
> 
> I have (new?) information about the PC87591x Super-I/O Chip. I have 
> talked to Winbond and they said, the only way to access this chip is 
> through the PowerManagement channels. The problem is, there exists 
> verious firmware implementations, so (I think) there exists different 
> commands through these channels.
> 
> To support this chip, there are 2 possibilities. The first is we need to 
> develope a firmware. The second is to analyze the firmware. On the 
> Uniwill website, there is a reader/writer for this chip 
> (http://www.uniwill.com/UserDownload/N243S/N243S2.htm), included in the 
> BIOS Update archive and is called ecf11t.exe. And on National's page 
> there is a programming reference for the core of the chip (CR16B). The 
> datasheet is available at 
> http://www.national.com/appinfo/compactrisc/pdf/cr16b-prog-ref.pdf.
> 
> Have anyone an idea, how to proceed the support? I know, none of these 
> possibilities are easy to manage.
> 
> EnricoB
> 
> 
> _______________________________________________
> lm-sensors mailing list
> lm-sensors at lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors


      parent reply	other threads:[~2005-12-22 21:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:25 PC87591x Enrico Bartky
2005-05-19  6:25 ` PC87591x Rudolf Marek
2005-12-22 17:38 ` [lm-sensors] PC87591x Enrico Bartky
2005-12-22 21:25 ` Mark Studebaker [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=43AB19C4.8050608@mds.gotdns.com \
    --to=mds@mds.gotdns.com \
    --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.