From: jbradford@dial.pipex.com
To: landley@trommello.org (Rob Landley)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Experimental IDE oops dumper v0.1
Date: Mon, 16 Sep 2002 16:14:45 +0100 (BST) [thread overview]
Message-ID: <200209161514.g8GFEjL0000740@darkstar.example.net> (raw)
In-Reply-To: <200209161444.g8GEhw2f017462@pimout1-ext.prodigy.net> from "Rob Landley" at Sep 16, 2002 05:43:50 AM
> > Talking about dumping oopsen, would there be any usefulness in outputting
> > crash data to the PC speaker, using a slow, (~300 bps) modulation that
> > would survive being captured on a cassette using a walkman with a
> > microphone, then decoded using a userspace program from a sampled .au file?
>
> This is easier and less error-prone than copying the oops down by hand?
Well, it is easy to make a mistake writing it down...
> I remember using 300 bps. On a closed electrical circuit without acoustic
> couplers, you still got line noise. Acoustic couplers put the speaker and
> microphone right on top of each other and surrounded them with a muffler to
> try to minimize ambient noise from the room...
WHAT? I have captured 1200/75 'prestel' style modem communications on tape, and played them back through a speaker, in to a phone handset, and had them faithfully reproduced on a terminal. Having said that, trying to use a 300 bps accustic coupler with a GSM phone wasn't successful, because you get some kind of inductive interference from the phone.
> > Just thought it might be easily implementable, as it doesn't have any
> > pre-requisits, (other than having a PC speaker, which *almost* everybody
> > has).
>
> Not everybody has a tape recorder, though.
>
> And the -ac branch already does output in morse code. Try taping that and
> writing a user mode interpreter for it, if you like...
Hmmm, that might be worth doing, because it gives you a way to automatically recover the data, rather than typing it in again, (which is prone to errors).
John.
next prev parent reply other threads:[~2002-09-16 15:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 11:52 [PATCH] Experimental IDE oops dumper v0.1 Rusty Russell
2002-09-16 12:18 ` Alan Cox
2002-09-16 12:39 ` jbradford
2002-09-16 9:43 ` Rob Landley
2002-09-16 15:14 ` jbradford [this message]
2002-09-16 19:55 ` Vojtech Pavlik
2002-09-16 19:52 ` Vojtech Pavlik
2002-09-16 22:22 ` Alan Cox
2002-09-17 0:49 ` Rusty Russell
2002-09-17 7:42 ` Andre Hedrick
2002-09-17 9:57 ` Alan Cox
2002-09-18 4:19 ` Rusty Russell
2002-09-18 6:00 ` Andre Hedrick
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=200209161514.g8GFEjL0000740@darkstar.example.net \
--to=jbradford@dial.pipex.com \
--cc=landley@trommello.org \
--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