Ross154   The long, uneventful wait for Elite:Dangerous for Linux

March 8, 2011


Filed under: android,hardware,linux,technology,wearable,wishlist — Victor Tramp @ 2:37 am

Things I’ve been asking Santa to invent are finally being invented. Maybe I’ll get the RV that drives itself after all? Maybe.. Retirement in orbit around the moon still seems unlikely.. But maybe I can cruise western Cascadia without much actual driving.. We’ll see. But hey! Snowboard goggles running Android. That’s a start.

April 4, 2010

Science Friction

Filed under: advocacy,hardware,linux,technology,wearable,wishlist — Victor Tramp @ 9:33 pm
Science Friction

…If it only had 640×480 (or better) instead of QVGA.

…If only it had an accelerometer & magnetometer buried in that thick frame.

…If only it were VGA/DVI, and powered by USB by default.

…If only it had a halfway reasonable DDC reply.

…If only the company that once made this knew it’s true place in the market.

…If only ten other companies made things just like it.

…If only the connection between this class of device and Compiz/X11 (and to some degree KWin) weren’t so obvious..

..If only…

August 26, 2009

On World Domination…

Filed under: hardware,linux,technology,wearable,wishlist — Victor Tramp @ 1:00 pm
On World Domination...

(12:45:08 PM) mprov: it still seems like we’ll have to tackle HAL and XInput after we have a driver, but maybe understanding those layers will help us understand what, at the kernel level, we’re trying to achieve
(12:46:58 PM) mprov: HAL depends on (d-bus, and then) udev to provide the manifestation of the /dev entry for the device, when the kernel registers the device, it shows up in /sys, where udev gets the info it needs to generate the /dev entry. Then dbus provides the notification to HAL which provides the permissions and access to the device to XInput
(12:48:01 PM) mprov: that’s the flow of things, once we have a complete handler for the HID layer once we have a recognized device registration
(12:48:58 PM) mprov: what we need in the kernel seems to be just that, a handler for the HID registration, which will provide the /sys entries for /udev to make the device. then we can interface it higher up the stack
(12:49:30 PM) mprov: for udev to make the /dev entry i mean
(12:49:32 PM) mprov: not /udev
(12:50:34 PM) mprov: (i’m repeating myself here, but) once udev generates the device, d-bus will notify HAL to parse the device and register it with XInput, which will make it available to the user

After that.. Wearable computing on every computer, using any HMD, by any manufacturer. Death to monitors!