From: khc@pm.waw.pl (Krzysztof Halasa)
To: lkml <linux-kernel@vger.kernel.org>, Andy Green <andy@warmcat.com>
Cc: lm-sensors@lm-sensors.org
Subject: [lm-sensors] Black box flight recorder for Linux
Date: Wed, 19 Apr 2006 10:47:46 +0000 [thread overview]
Message-ID: <m364l5dep9.fsf@defiant.localdomain> (raw)
In-Reply-To: <m3odz9kze6.fsf@defiant.localdomain> (Krzysztof Halasa's message of "Mon, 10 Apr 2006 21:24:01 +0200")
Hi,
(Cc to lm-sensors list).
> Yes, that could be used, too. It would be a bit more complicated as
> different VGA cards use different access methods (i.e., different
> I/O port and bit numbers). X11 drivers probably know how to drive it.
BTW: I just soldered a 24C64 I^2C EEPROM (the largest I could find
at home but 24C512 (64 KB) and even 24C1024 (128 KB) are available
on the market) to a connector and connected it to SMBus on my Asus
A7V333 mobo. I don't have code to write "printk" messages to it yet
but will look at it sometime.
Interesting: i2cdetect and friends can only find a custom Asus sensors
chip on this bus (ASB100 chip at addresses 0x2D, 0x48 and 0x49) - and
now my 24C64 at 0x57 (config address 7 = all ones). But the BIOS POST
searches and finds more devices: there is something at 0x2F, 0x69, and
there are (I think) DDR SDRAM EEPROMs and 0x51 and 0x52 (0x50 is an
empty DIMM slot). Got this info with my "DIY" logic analyzer. I think
the BIOS POST disconnects somehow the devices before loading the OS
(in order to prevent data damage?).
No wonder my first attempt with 24C16 which occupies all 0x50 - 0x57
addresses had to fail.
I think VGA monitors respond (at least?) at 0x50 address so
a 16-bit-addressable EEPROM (at least not larger than 24C2048 which
IMHO aren't yet available) with all-ones I^2C address selected
should do as well if connected to VGA/DVI I^2C/ACCESS.bus.
--
Krzysztof Halasa
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Halasa <khc@pm.waw.pl>
To: lkml <linux-kernel@vger.kernel.org>, Andy Green <andy@warmcat.com>
Cc: lm-sensors@lm-sensors.org
Subject: Re: Black box flight recorder for Linux
Date: Wed, 19 Apr 2006 12:47:46 +0200 [thread overview]
Message-ID: <m364l5dep9.fsf@defiant.localdomain> (raw)
In-Reply-To: <m3odz9kze6.fsf@defiant.localdomain> (Krzysztof Halasa's message of "Mon, 10 Apr 2006 21:24:01 +0200")
Hi,
(Cc to lm-sensors list).
> Yes, that could be used, too. It would be a bit more complicated as
> different VGA cards use different access methods (i.e., different
> I/O port and bit numbers). X11 drivers probably know how to drive it.
BTW: I just soldered a 24C64 I^2C EEPROM (the largest I could find
at home but 24C512 (64 KB) and even 24C1024 (128 KB) are available
on the market) to a connector and connected it to SMBus on my Asus
A7V333 mobo. I don't have code to write "printk" messages to it yet
but will look at it sometime.
Interesting: i2cdetect and friends can only find a custom Asus sensors
chip on this bus (ASB100 chip at addresses 0x2D, 0x48 and 0x49) - and
now my 24C64 at 0x57 (config address 7 = all ones). But the BIOS POST
searches and finds more devices: there is something at 0x2F, 0x69, and
there are (I think) DDR SDRAM EEPROMs and 0x51 and 0x52 (0x50 is an
empty DIMM slot). Got this info with my "DIY" logic analyzer. I think
the BIOS POST disconnects somehow the devices before loading the OS
(in order to prevent data damage?).
No wonder my first attempt with 24C16 which occupies all 0x50 - 0x57
addresses had to fail.
I think VGA monitors respond (at least?) at 0x50 address so
a 16-bit-addressable EEPROM (at least not larger than 24C2048 which
IMHO aren't yet available) with all-ones I^2C address selected
should do as well if connected to VGA/DVI I^2C/ACCESS.bus.
--
Krzysztof Halasa
next prev parent reply other threads:[~2006-04-19 10:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-08 11:12 Black box flight recorder for Linux James Courtier-Dutton
2006-04-08 13:41 ` Andi Kleen
2006-04-08 19:42 ` Guennadi Liakhovetski
2006-04-08 16:40 ` Lee Revell
2006-04-08 17:30 ` Matti Aarnio
2006-04-09 19:23 ` Krzysztof Halasa
2006-04-10 12:01 ` Andy Green
2006-04-10 19:24 ` Krzysztof Halasa
2006-04-19 10:47 ` Krzysztof Halasa [this message]
2006-04-19 10:47 ` Krzysztof Halasa
2006-04-19 20:20 ` [lm-sensors] " Rudolf Marek
2006-04-19 20:20 ` Rudolf Marek
2006-04-19 23:02 ` Krzysztof Halasa
2006-04-19 23:02 ` Krzysztof Halasa
2006-06-06 17:42 ` Krzysztof Halasa
2006-06-06 17:42 ` Krzysztof Halasa
2006-06-07 8:03 ` [lm-sensors] " Jean Delvare
2006-06-07 8:03 ` Jean Delvare
2006-06-07 10:18 ` [lm-sensors] " Andy Green
2006-06-07 10:18 ` Andy Green
2006-06-07 23:52 ` [lm-sensors] " Krzysztof Halasa
2006-06-07 23:52 ` Krzysztof Halasa
2006-04-11 11:21 ` Jan Engelhardt
2006-04-10 3:06 ` Russell Senior
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=m364l5dep9.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=andy@warmcat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.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.