From: Emiliano Russo <emiliano@verdebinario.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] Introduce the aural error reporting framework
Date: Mon, 1 Apr 2019 15:45:16 +0200 [thread overview]
Message-ID: <6f0054fb-bc1a-b8f2-dccf-ec0088d1e382@verdebinario.org> (raw)
In-Reply-To: <20190401102456.11162-1-mcroce@redhat.com>
Il 01/04/19 12:24, Matteo Croce ha scritto:
> These are all cases when the aural errors framework comes to help. This
> framework adds to the kernel a generic library to play sounds, which can
> be used to report errors or generic events.
hello Matteo,
this reminds me of a hack that Mr. Ferruccio Zulian (chief system
architect for Olivetti, General Electric, Honeywell and IBM from 1965 to
1990) told us about during an interview we made for our computer art
exhibition "bin/art"
When testing the hardware of a new system, back in the mid-60s, the
engineers hooked audio output to circuitry for debugging purposes.
They kept in mind how a set of correctly executed operations
**literally** sounded like and therefore they were able to detect errors
in later executions when something sounded "wrong".
This was way more easy than looking at the light panels commonly used
for similar debugging activities, as listening to sounds does not force
you to be in a particular place, looking at a particular object.
As explained in the interview, an interesting side effect of this hack
led to the early computer music experiments with Pietro Grossi (a real
giant in contemporary and electronic music) that ended up in the
recording "GE-115 concerto" 7 inch vinyl, distributed as christmas gift
to all Olivetti/General Electric employees in 1967.
here's the link to a webpage with the interview (in italian)
https://binart.eu/ge-115-concerto/
and to the recording itself
side A: https://www.youtube.com/watch?v=CXosSsSekaU
side B: https://www.youtube.com/watch?v=bf8jMA_zizc
...so, what does this curious anectode say to us?
it looks like history is on the side of this patch :-)
hope it gets in the mainline code!
Ciao!
Emiliano Russo
---------------
Museo Interattivo di Archeologia Informatica (MIAI)
Museo dell'Informatica Funzionante (MusIF)
Computer Musea :-)
prev parent reply other threads:[~2019-04-01 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 10:24 Matteo Croce
2019-04-01 10:24 ` [PATCH 1/4] " Matteo Croce
2019-04-01 10:24 ` [PATCH 2/4] panic: use the aural error reporting framework to report panics Matteo Croce
2019-04-01 10:24 ` [PATCH 3/4] bug: use the aural error reporting framework to report warnings Matteo Croce
2019-04-01 10:24 ` [PATCH 4/4] oops: use the aural error reporting framework to report oopses Matteo Croce
2019-04-01 10:24 ` [PATCH 5/4] procfs: utility handler to trigger different errors Matteo Croce
2019-04-01 11:03 ` [PATCH 0/4] Introduce the aural error reporting framework Peter Zijlstra
2019-04-02 8:49 ` Thomas Gleixner
2019-04-02 11:50 ` Matteo Croce
2019-04-02 13:21 ` Thomas Gleixner
2019-04-01 13:45 ` Emiliano Russo [this message]
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=6f0054fb-bc1a-b8f2-dccf-ec0088d1e382@verdebinario.org \
--to=emiliano@verdebinario.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
all inboxes | Powered by JetHome®