From: Timothy Sample <samplet@ngyro.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, jeremiah@pdp10.guru
Subject: Punch cards (was Preparing the reduced bootstrap tarballs)
Date: Tue, 20 Nov 2018 10:28:10 -0500 [thread overview]
Message-ID: <87zhu34vlh.fsf_-_@ngyro.com> (raw)
In-Reply-To: <87sgzw885x.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 20 Nov 2018 09:28:26 +0100")
Hi,
Ricardo Wurmus <rekado@elephly.net> writes:
> jeremiah@pdp10.guru writes:
>
>>> for the lazyer like me, what about a punched card? :-)
>> If someone is willing to figure out how to read a deck of punched cards
>> without software, I'd be interested in learning more.
>
> Now that’s a project for a free hardware design that I’d happily work
> on :)
>
> Reading and transmitting of the bitstream can be done in hardware alone
> (shift register, MUX, photoresistors, …), though I’d need to know what
> kind of interface there is on the receiving side. Just flash memory /
> TTL shift register?
I’ve thought about this a bit. Would it be possible to go even more
mechanical, and implement the SPI protocol in switches toggled by holes
cut in some kind of insulating tape? You could have a couple of steel
balls (bearings?) balanced on top of each other, connected to a circuit
using brushes or springs. Then, you place the tape in between the
bearings. When there’s a hole in the insulating tape, they make
contact, and when there is no hole, no contact. Then, you have a row of
holes for the SPI clock, and a row of holes for the SPI data. All you
would have to do is hook up the right voltage to it, and you could write
to a flash ROM by pulling manually punched tape through it. (You could
use a crank or motor if the timing needs to be more precise.)
Then, you could take an x200 and setup the bootrom to be whatever you
wanted with no software whatsoever. If you adjusted stage0 to set up a
“cache-as-RAM” environment (like they do in coreboot), you could do
quite a bit of manoeuvring before having to initialize RAM. That is,
you could probably set up a tiny Scheme environment and do more hardware
initialization from there.
Obviously all of this would be easier on a simpler computer, but then
presumably you have to move from a simpler computer to a more
complicated computer at some point (depending on your needs). The nice
thing about booting the x200 as a simple computer is that you can just
expand its boundaries until it is full-featured.
Sorry for derailing a bit, I just wanted to share some idle thoughts.
> --
> Ricardo
-- Tim
prev parent reply other threads:[~2018-11-20 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 0:26 Preparing the reduced bootstrap tarballs jeremiah
2018-11-20 8:28 ` Ricardo Wurmus
2018-11-20 15:28 ` Timothy Sample [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=87zhu34vlh.fsf_-_@ngyro.com \
--to=samplet@ngyro.com \
--cc=guix-devel@gnu.org \
--cc=jeremiah@pdp10.guru \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.