From Noisebridge
Revision as of 11:45, 22 December 2011 by Subdeuxed (Talk | contribs)

Jump to: navigation, search

Kiang is a round tabletop computer for general use.


please feel free to use the table as a kiosk, but be prepared for unpredictable uptime while the system is experimented with. OpenSSH server is installed for remote management.

user: noisetable
pass: noisebridge


  • Zytouch capacaitive touch screen built into it, and a small x86 embedded system underneath that..
  • VIA Eden board with a code name 'Esther' processor on it. It clocks at 400mHz but cat /proc/cpuinfo shows it may be able to go up to 1Ghz (with active cooling?)
  • there are faster drivers than the default vesa setting in the xorg.conf file. they should be installed now
  • bluetooth
  • wifi card
    • 05:08.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)
  • Ubuntu 10.04 installed on a 80gig 3.5 IDE drive. The generic install works fine out of the box, but optimizations for an older memory and speed limited system would never hurt.
    • 2011-10-02: upgrade to 11.04 in progress

To Do

  • Cant get the openchrome Xorg driver to work well with the VIA eden board. The Ubuntu package is called xserver-xorg-video-openchrome. xorg.conf was modified to use the 'openchrome' device and dpkg-reconfigure -phigh xserver-xorg was run. Then gdm was cycled by /etc/init.d/gdm restart

  1. A round tabletop system presents challenges to window management designer, it would be interesting to get a touch based system like Android running on this machine. The machine may be down for work on projects like this.
  2. It needs some Zytouch driver love, which comes from the touch-base website:
  3. The serial connection has been routed through a keyspan 19HS serial-to-USB converter. Unfortunately, drivers for the damned thing are only available for Windows, and John has been bashing his head against getting the Ubuntu host to recognize the converter and pass the serial connection through to wine. Windows may need to be installed.
  4. Another option is to reverse engineer a driver. This could theoretically be a userland daemon providing an input device to Xorg. There are many ways to help this effort:

Here is a hex dump of the serial data sent by the touchpad with "no interaction":

I can't guarantee that the output represents _zero_ interaction because some values in the stream appear to be _very_ sensitive to proximity.

There are 11 or so unique values sent from the touchscreen. We have to figure out what they mean and when they are sent.

If you want to have a look at those values, open the homebrew "driver" in the works: ~/noisetap/noisetap.c

There you will find the list of values and the best explanations we can come up with as to what they mean.

Another way to help out would be to bring a Windows box with a serial connection to the table (see what I did there?). If you can get the touchscreen driver to work, we may be able to step through the driver code and reverse engineer it that way. This would probably be a lot easier than figuring it out from the raw data dump, but it requires some Windows know-how (That's a tough thing to find at Noisebridge). If you want to lend a Windows box to the project, John will gladly take care of the gory details involved in DLL sniffing (or whatever it is we need to do).

Personal tools