From: Vojtech Pavlik <vojtech@suse.cz>
To: Rob Landley <landley@trommello.org>
Cc: jbradford@dial.pipex.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Experimental IDE oops dumper v0.1
Date: Mon, 16 Sep 2002 21:55:22 +0200 [thread overview]
Message-ID: <20020916215522.B60197@ucw.cz> (raw)
In-Reply-To: <200209161444.g8GEhw2f017462@pimout1-ext.prodigy.net>; from landley@trommello.org on Mon, Sep 16, 2002 at 05:43:50AM -0400
On Mon, Sep 16, 2002 at 05:43:50AM -0400, Rob Landley wrote:
> On Monday 16 September 2002 08:39 am, jbradford@dial.pipex.com wrote:
> > 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?
Works in X. Hand copying doesn't. But serial (or printer) console is
probably easier.
> 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...
Well, this is simplex only, so it's a bit easier. And we could use even
slower speed, 75 bps would also work.
> > 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...
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-09-16 19:50 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
2002-09-16 19:55 ` Vojtech Pavlik [this message]
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=20020916215522.B60197@ucw.cz \
--to=vojtech@suse.cz \
--cc=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