From: Andy Green <andy@warmcat.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux list <linux-kernel@vger.kernel.org>
Subject: Re: Black box flight recorder for Linux
Date: Mon, 10 Apr 2006 13:01:43 +0100 [thread overview]
Message-ID: <443A4927.5040801@warmcat.com> (raw)
In-Reply-To: <m3psjqeeor.fsf@defiant.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]
Krzysztof Halasa wrote:
> I think the most trivial and reliable way would be to solder some
> I^2 or similar EEPROM chip to, for example, parallel port connector.
>
> Most motherboards have an internal I^2C bus / SMBus (for reading RAM
> types and for other things) and I think it could be used to connect
> the EEPROM instead of external port.
>
> There are 512 Kbit (64 KB) and 1 Mbit (128 KB) EEPROMs available -
> there is plenty of space not only for crash dump but for whole dmesg.
Just an additional thought on this idea... both VGA and DVI connectors
on modern video cards appear to have DDC-2 connections, which is in fact
I2C. This would provide an (inherently bidirectional :-) ) 3-pin
digital interface out of a mostly dead box even on laptops and so on
with no serial, parallel or legacy keyboard/mouse, so long as they had
reasonably modern VGA or DVI out. You would need to get access to the
two I2C pins and Gnd somehow in that scenario. Since I2C has a concept
of addressing it should be possible to choose I2C addresses for this
communication that doesn't address whatever may be listening on the same
bus in the monitor.
I don't know if you bitbang these or there is some kind of
shifter/management logic in the video chip, in which case some minimal
case by case support is needed, but since simple IO is otherwise all but
gone on modern laptops so I thought it worth mentioning.
-Andy
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 4492 bytes --]
next prev parent reply other threads:[~2006-04-10 12:01 UTC|newest]
Thread overview: 29+ 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 [this message]
2006-04-10 19:24 ` Krzysztof Halasa
2006-04-19 10:47 ` Krzysztof Halasa
2006-04-19 20:20 ` [lm-sensors] " Rudolf Marek
2006-04-19 23:02 ` Krzysztof Halasa
2006-06-06 17:42 ` Krzysztof Halasa
2006-06-07 8:03 ` Jean Delvare
2006-06-07 10:18 ` Andy Green
2006-06-07 23:52 ` Krzysztof Halasa
2006-04-11 11:21 ` Jan Engelhardt
2006-04-10 3:06 ` Russell Senior
[not found] <5ZjEd-4ym-37@gated-at.bofh.it>
[not found] ` <5ZlZk-7VF-13@gated-at.bofh.it>
2006-04-08 14:05 ` Robert Hancock
2006-04-08 7:17 ` Andi Kleen
2006-04-08 16:28 ` James Courtier-Dutton
2006-04-08 22:28 ` JustFillBug
2006-04-09 17:09 ` James Courtier-Dutton
2006-04-10 18:53 ` Ville Herva
2006-04-09 15:04 ` Andi Kleen
2006-04-09 19:25 ` Eric W. Biederman
2006-04-10 12:18 ` linux-os (Dick Johnson)
2006-04-10 19:44 ` Krzysztof Halasa
2006-04-10 20:07 ` linux-os (Dick Johnson)
-- strict thread matches above, loose matches on Subject: below --
2006-04-08 22:45 linux
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=443A4927.5040801@warmcat.com \
--to=andy@warmcat.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox