How much information can you convey with a 1 bit interface?

Re:How much information can you convey with a 1 bit interface? by daturkel on Saturday June 29, 2013 @06:46PM (#5963971)

This isn't all that abstract or theoretical of a problem. There's lots of devices (printers without lcd screens, routers, for example) which use one or two lights, possibly with different color options, to display a bunch of different possible errors. Often this simply means creating a "key" for the interface (i.e. check the manual to look up what two blinking red leds means or what one steady green and one blinking red means) which is admittedly not fun for the user, but it's also damn hard to make things intuitive with so little resolution (literally!) to convey your info in.

[ Parent | on HN ]

Re:How much information can you convey with a 1 bit interface? by prezjordan on Saturday June 29, 2013 @07:00PM (#5964004)

My favorite example of this is how the linux kernel will actually give you morse code through the keyboard lights (num lock, scroll lock, caps lock) during a kernel panic [0].

[0]: http://www.linuxtoday.com/developer/2002072200326NWKNDV

[ Parent | on HN ]

Re:How much information can you convey with a 1 bit interface? by alex_h on Saturday June 29, 2013 @07:11PM (#5964028)

Cool, there is a scene in Neal Stephenson's Cryptonomicon where the protagonist programs his keyboard lights to play back messages to him in Morse Code. I had no idea it had been implemented IRL.

[ Parent | on HN ]

Re:How much information can you convey with a 1 bit interface? by georgemcbay on Saturday June 29, 2013 @09:16PM (#5964337)

Back in the early days of CHDK (custom firmware for Canon cameras) they would dump the original firmware code of new cameras by writing a tiny loader (that looked like a firmware update program to the camera), put that loader on a memory card in the camera, run the loader on the camera via the firmware upgrade menu option and that loader would just read the original firmware out of memory and blink an LED on the camera over time to send out all the bytes of the original firmware. A computer would then capture that signal with a photodiode connected via serial port or sound/mic input resulting in a binary dump of the camera's original firmware on the remote computer where it could be disassembled and reverse engineered and (eventually) extended to have all sorts of functions the camera didn't ship with.

http://chdk.wikia.com/wiki/Obtaining_a_firmware_dump

[ Parent | on HN ]

Re:How much information can you convey with a 1 bit interface? by pestaa on Saturday June 29, 2013 @07:22PM (#5964061)

That's certainly fun in a book, but honestly I'd freak out and suspect a virus if my Linux machine went mayday and the keyboard goes equally crazy.

[ Parent | on HN ]

Re:How much information can you convey with a 1 bit interface? by gizmo686 on Sunday June 30, 2013 @12:04AM (#5964663)

If your computer starts acting visibly funny (as apposed to funny in the sense of weird processes or network activity), you can almost entirely rule out a virus, those like to stay hidden.

[ Parent | on HN ]

Re:How much information can you convey with a 1 bit interface? by vidarh on Sunday June 30, 2013 @05:22AM (#5965208)

That's an interesting observation actually, because it didn't use to be the case. It used to be the case that most viruses would intentionally make a nuisance of themselves or display messages every now and again (e.g. you might get a message on boot every 10 times or so - too often and they would get eradicated before they spread).

Viruses that are intended to stay hidden and undiscovered is a new thing, relatively speaking.

[ Parent | on HN ]

Re:How much information can you convey with a 1 bit interface? by firegrind on Sunday June 30, 2013 @05:30AM (#5965226)

tleds (http://users.tkk.fi/jlohikos/tleds) reported network information by flashing the caps, num and scroll lock lights on your keyboard.

[ Parent | on HN ]