From: se.witt@gmx.net (Sebastian Witt)
To: lm-sensors@vger.kernel.org
Subject: ATXP1 kernel patch
Date: Thu, 19 May 2005 06:25:28 +0000 [thread overview]
Message-ID: <41D84030.2020704@hasw.net> (raw)
In-Reply-To: <41D821D9.5030003@hasw.net>
Hi,
Rudolf Marek wrote:
> +static unsigned short normal_i2c[]= { 0x37, 0x4e, I2C_CLIENT_END };
>
> I read on some forum also about 0x44. Any clue?
I've only seen the ATXP1 on 0x37 or 0x4e (it only supports two
addresses), the
0x44 is maybe for another ATXP.
> +static DEVICE_ATTR(vcore, 0644, atxp1_showvcore, atxp1_storevcore);
>
> cpu[0-1]_vid CPU core reference voltage.
> Unit: millivolt
>
> What about to use this? (This is also question for other developers :)
Yes, good idea.
> + if(i2c_smbus_read_byte_data(new_client, ATXP1_CVID) <= 0) {
> + kfree(data);
> + return 0;
>
> Hmm really not very scientific nor realible. Any other method is possible?
No, it has no register with a device id.
> Next question is about update lock.
> Why is gone? It is always good idea...
Yes, will be added again.
> Also what about ATXP3 and ATX5 my asus board (A7S333) has ATXP3.
AFAIK the ATXP3 is the same as the ATXP1 but without VID control. Not
sure about the ATXP5, I've only a board with a ATXP1. Needing someone
who wants to test this.
> Any effort about getting datasheet?
Attansic doesn't answer me. The mainboard manufacturers say they can't
give information because of nVidia.
Bye,
Sebastian
next prev parent reply other threads:[~2005-05-19 6:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:25 ATXP1 kernel patch Sebastian Witt
2005-05-19 6:25 ` Rudolf Marek
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Sebastian Witt [this message]
2005-05-19 6:25 ` Sebastian Witt
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Sebastian Witt
2005-05-19 6:25 ` Sebastian Witt
2005-05-19 6:25 ` Sebastian Witt
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Sebastian Witt
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` 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=41D84030.2020704@hasw.net \
--to=se.witt@gmx.net \
--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.