From: "David D. Hagood" <wowbagger@sktc.net>
To: Andrew Rodland <arodland@noln.com>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>, linux-kernel@vger.kernel.org
Subject: Re: Speaker twiddling [was: Re: Panicking in morse code]
Date: Sat, 27 Jul 2002 07:57:42 -0500 [thread overview]
Message-ID: <3D4298C6.9080103@sktc.net> (raw)
In-Reply-To: 20020727015703.21f47a37.arodland@noln.com
I don't understand the direction this discussion is taking.
Either you are trying to output the panic information with minimal
hardware, and in a form a human might be able to decode, in which case
the Morse option seems to me to be the best, or you are trying to panic
in a machine readable format - in which case just dump the data out
/dev/ttyS0 and be done with it!
To my way of thinking, the idea of the Morse option is that if an oops
happens when you are not expecting it, and you haven't set up any
equipment to help you, you still have a shot at getting the data.
Trying to dump the oops data out by some form of FSK in most cases seems
silly - if you have taken the time to set up a microphone and decoder,
why not just set up a serial terminal?
next prev parent reply other threads:[~2002-07-27 12:54 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 5:13 [PATCH -ac] Panicking in morse code Andrew Rodland
2002-07-19 5:29 ` William Lee Irwin III
2002-07-19 16:36 ` Thorsten Kranzkowski
2002-07-19 17:00 ` Andrew Rodland
2002-07-19 17:27 ` Eli Carter
2002-07-19 17:32 ` Andrew Rodland
2002-07-19 23:02 ` [PATCH -ac] Panicking in morse code, v2 Andrew Rodland
2002-07-20 10:58 ` Daniel Phillips
2002-07-20 11:19 ` Thunder from the hill
2002-07-20 13:22 ` Ville Herva
2002-07-20 14:18 ` Daniel Phillips
2002-07-20 14:55 ` Tomas Szepe
2002-07-20 16:05 ` Daniel Phillips
2002-07-20 19:51 ` Thunder from the hill
2002-07-20 0:35 ` [PATCH -ac] Panicking in morse code Alan Cox
2002-07-20 0:39 ` Andrew Rodland
2002-07-20 0:48 ` Thunder from the hill
2002-07-25 12:51 ` Bill Davidsen
2002-07-26 3:43 ` Daniel Phillips
2002-07-26 4:47 ` Daniel Phillips
2002-07-26 4:52 ` jdow
2002-07-26 5:13 ` Daniel Phillips
2002-07-26 13:50 ` Bill Davidsen
2002-07-26 13:38 ` Bill Davidsen
2002-07-26 14:39 ` Richard B. Johnson
2002-07-26 20:09 ` Bill Davidsen
2002-07-26 23:25 ` Jens Schmidt
2002-07-27 2:05 ` Albert D. Cahalan
2002-07-27 4:00 ` Andrew Rodland
[not found] ` <200207270526.g6R5Qw942780@saturn.cs.uml.edu>
2002-07-27 5:57 ` Speaker twiddling [was: Re: Panicking in morse code] Andrew Rodland
2002-07-27 9:46 ` Daniel Phillips
2002-07-27 12:57 ` David D. Hagood [this message]
2002-07-27 15:45 ` Andrew Rodland
2002-07-29 17:47 ` Pavel Machek
2002-07-29 22:02 ` Ray Friess
2002-07-29 17:49 ` Pavel Machek
2002-07-29 20:35 ` Albert D. Cahalan
2002-07-29 21:08 ` Pavel Machek
2002-07-27 18:56 ` Albert D. Cahalan
2002-07-27 19:44 ` Ville Herva
2002-07-27 22:40 ` Alan Cox
2002-07-27 21:35 ` Ville Herva
2002-07-31 15:20 ` Thunder from the hill
2002-07-27 21:40 ` Ryan Anderson
2002-07-28 10:26 ` Lars Magne Ingebrigtsen
2002-07-29 20:03 ` Albert D. Cahalan
2002-08-13 17:20 ` Mark H. Wood
2002-07-27 4:04 ` [PATCH -ac] Panicking in morse code Andrew Rodland
2002-07-29 11:50 ` Bill Davidsen
2002-07-29 12:34 ` Richard B. Johnson
2002-07-29 19:57 ` Albert D. Cahalan
2002-07-31 17:54 ` Bill Davidsen
2002-07-20 21:32 ` [PATCH -ac] Panicking in morse code v3 Andrew Rodland
2002-07-21 8:49 ` Brad Hards
2002-07-21 9:08 ` Russell King
2002-07-21 10:50 ` Zwane Mwaikambo
2002-07-21 15:43 ` Daniel Phillips
2002-07-22 17:18 ` Andrew Rodland
[not found] <04a801c235b9$03f699f0$1125a8c0@wednesday>
2002-07-28 0:43 ` Speaker twiddling [was: Re: Panicking in morse code] Albert D. Cahalan
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=3D4298C6.9080103@sktc.net \
--to=wowbagger@sktc.net \
--cc=acahalan@cs.uml.edu \
--cc=arodland@noln.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