A Linux kernel driver has been created that allows a rotary phone dial to be used as an input device. The driver translates the pulses generated by the rotary dial into numeric key presses, effectively turning the old-fashioned dial into a USB HID keyboard. It supports both clockwise and counter-clockwise rotation for dialing and navigating menus and also allows for customization of the pulse-to-digit mapping. This project makes it possible to integrate a rotary phone dial into a modern Linux system for unique input control.
The Apple II MouseCard's interrupt requests (IRQs) are indeed synchronized with the vertical blanking interval (VBL). Through oscilloscope analysis and examining the MouseCard's firmware, the author confirmed that the card cleverly uses the VBL signal to time its counter, ensuring consistent IRQ generation every 1/60th of a second. This synchronization prevents screen tearing and jerky mouse movement, as updates are coordinated with the display refresh. Despite prior speculation and documentation suggesting otherwise, the investigation conclusively demonstrates the VBL-synced nature of the MouseCard's IRQ.
HN commenters discuss the intricacies of the Apple II MouseCard's interrupt handling, particularly its synchronization with the vertical blanking interval (VBL). Some express admiration for the clever engineering required to achieve stable mouse input within the constraints of the Apple II's hardware. One commenter recounts experiences with similar timing challenges on the Atari 8-bit and C64, emphasizing the difficulty of accurate timing without dedicated hardware support. Others delve into the specifics of the MouseCard's design, mentioning the use of a shift register and the challenges of debouncing button presses. The overall tone is one of appreciation for the ingenuity required to implement seemingly simple features on older hardware.
Clawtype version 2.1 is a compact, one-handed input device combining a chorded keyboard and mouse. Using only five keys, it allows for typing, mouse movement, clicking, scrolling, and modifiers like shift and control. The device connects via USB and its small size makes it portable and suitable for use in confined spaces. The creator demonstrates its functionality in a video, showcasing text entry and mouse control, highlighting its potential for efficient one-handed computing.
Commenters on Hacker News generally expressed interest in the Clawtype keyboard, praising its compact design and potential for ergonomic benefits, especially for those with limited desk space or RSI concerns. Several questioned the practicality and learning curve, wondering about its speed compared to traditional keyboards and the difficulty of mastering the chords. Some offered suggestions for improvement, like adding a wrist rest or thumb cluster, while others shared experiences with similar one-handed keyboards, highlighting the tradeoffs between portability and typing proficiency. A few users requested information on key remapping and software customization options. Overall, the response was a mix of curiosity, cautious optimism, and practical considerations regarding the device's usability.
Ken Shirriff created a USB interface for a replica of the iconic "keyset" used in Douglas Engelbart's 1968 "Mother of All Demos." This keyset, originally designed for chordal input, now sends USB keystrokes corresponding to the original chord combinations. Shirriff's project involved reverse-engineering the keyset's wiring, designing a custom circuit board to read the key combinations, and programming an ATmega32U4 microcontroller to translate the chords into USB HID keyboard signals. This allows the replica keyset, originally built by Bill Degnan, to be used with modern computers, preserving a piece of computing history.
Commenters on Hacker News largely expressed fascination with the project, connecting it to a shared nostalgia for early computing and the "Mother of All Demos." Several praised the creator's dedication and the ingenuity of using a Teensy microcontroller to emulate the historical keyset. Some discussed the technical aspects, including the challenges of replicating the original chord keyboard's behavior and the choice of using a USB interface. A few commenters reminisced about their own experiences with similar historical hardware, highlighting the significance of preserving and interacting with these pieces of computing history. There was also some discussion about the possibility of using this interface with modern emulators or virtual machines.
Kanata is a cross-platform keyboard remapping tool that supports creating complex, layered keymaps. It allows users to define multiple layers, activate them with various methods (like modifier keys or keyboard shortcuts), and apply remappings specific to each layer. The configuration is text-based and highly customizable, offering fine-grained control over individual keys and combinations. Kanata is designed to be lightweight and portable, working across different operating systems including Windows, macOS, and Linux.
Hacker News users discussed Kanata's potential, praising its cross-platform compatibility and advanced features like multi-layer keymaps and scripting. Some expressed excitement about finally having a viable alternative to Karabiner on Windows and Linux. Concerns were raised about the project's early stage of development, documentation gaps, and reliance on Node.js for some core functionality. A few commenters questioned the necessity of Node.js, suggesting a native implementation could improve performance and reduce dependencies. Others shared their personal use cases and desired features, like integration with existing configuration tools and support for specific keyboard layouts. The overall sentiment was positive, with many users eager to try Kanata and contribute to its development.
The Steam Brick is a conceptual handheld gaming PC designed for minimalism. It features only a power button and a USB-C port, relying entirely on external displays and controllers. The idea is to offer a compact and portable PC capable of running Steam games, shifting the focus to user-chosen peripherals rather than built-in components. This approach aims to reduce e-waste by allowing users to upgrade or replace their peripherals independently of the core computing unit.
HN commenters generally found the Steam Brick an interesting, albeit impractical, project. Several discussed the potential utility of a dedicated Steam streaming device, particularly for travel or as a low-power alternative to a full PC. Some questioned the choice of using a Raspberry Pi Compute Module 4, suggesting a Rockchip RK3588 based device would be more powerful and efficient for video decoding. Others highlighted the project's complexity, especially regarding driver support, and contrasted it with commercially available options like the Steam Deck. A few appreciated the minimalist aesthetic and the focus on a single, dedicated function. There was also some discussion of alternative software options, such as using a pre-built Steam Link OS image or exploring GameStream from Nvidia. A significant point of discussion revolved around the lack of a hardware reset button, with many suggesting it as a crucial addition for a headless device.
Cosmos Keyboard is a project aiming to create a personalized keyboard based on a 3D scan of the user's hands. The scan data is used to generate a unique key layout and keycap profiles perfectly tailored to the user's hand shape and size. The goal is to improve typing ergonomics, comfort, and potentially speed by optimizing key positions and angles for individual hand physiology. The project is currently in the prototype phase and utilizes readily available 3D scanning and printing technology to achieve this customization.
Hacker News users discussed the Cosmos keyboard with cautious optimism. Several expressed interest in the customizability and ergonomic potential, particularly for those with injuries or unique hand shapes. Concerns were raised about the reliance on a phone's camera for scanning accuracy and the lack of key travel/tactile feedback. Some questioned the practicality of the projected keyboard for touch typing and the potential distraction of constantly looking at one's hands. The high price point was also a significant deterrent for many, with some suggesting a lower-cost, less advanced version could be more appealing. A few commenters drew comparisons to other projected keyboards and input methods, highlighting the limitations of similar past projects. Overall, the concept intrigued many, but skepticism remained regarding the execution and real-world usability.
Summary of Comments ( 15 )
https://news.ycombinator.com/item?id=44080803
Hacker News users generally expressed amusement and appreciation for the novelty of a rotary phone driver for Linux. Some questioned its practical use cases beyond nostalgia and hobby projects, while others suggested potential applications like museum exhibits or integrating rotary phones into modern VoIP systems. Several commenters delved into technical aspects, discussing the specifics of the driver implementation, pulse timing, and potential improvements like debouncing. A few reminisced about their experiences with rotary phones, highlighting the distinct tactile and auditory feedback they provided. There was also lighthearted debate about the proper nomenclature for the device (rotary vs. pulse dial).
The Hacker News post titled "Show HN: Rotary Phone Dial Linux Kernel Driver" sparked a discussion with several interesting comments.
Several users expressed admiration for the project, appreciating the ingenuity and the "old-school cool" factor of interfacing a rotary phone with a modern Linux system. One commenter mentioned the nostalgic appeal, recalling childhood memories of using rotary phones.
A significant portion of the discussion revolved around the technical aspects of the project. Users inquired about the specifics of the implementation, such as how the driver handles pulse timing and debouncing. The creator responded to these queries, explaining details like the use of interrupts and the method employed to translate the pulses into numerical digits. This back-and-forth provided valuable insight into the inner workings of the driver.
One commenter questioned the practical applications of such a driver, wondering what real-world use cases it might serve. Other users offered suggestions, ranging from retro-themed projects and art installations to educational demonstrations of historical technology. The possibility of using the driver for accessibility purposes was also raised.
There was a brief discussion about the challenges of working with older hardware. One user recounted their experience with the deteriorating rubber in old rotary phones, highlighting the difficulty of maintaining such devices.
A few commenters drew parallels between this project and other retro-computing endeavors, showcasing the continuing interest in preserving and interacting with older technologies in novel ways. They mentioned similar projects involving vintage hardware interfaced with modern systems.
Finally, some users offered constructive criticism and suggestions for improvement. They proposed ideas like adding support for different types of rotary phones and exploring alternative implementation approaches.