Programmers Notes for PadOrbiter

From LinuxMCE
Revision as of 05:22, 25 August 2009 by Ray N (Talk | contribs)

(diff) ←Older revision | view current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

Contained on this page are my notes for the PadOrbiter. Particularly in regards to the various bits of glue software that make the user experience more convenient.


TabletCFG is the Configuration program for setting network parameters on the PadOrbiter. It modifies various configuration files to configure network parameters for the PadOrbiter to function properly.

Network Configuration Snippets

TabletCfg needs to modify various files to configure network parameters for the wireless card. These files are overwritten completely each time the configuration changes.


WPA-PSK requires that a configuration file for /etc/wpa_supplicant.conf and /etc/network/interfaces be modified.


       proto=WPA RSN
       pairwise=CCMP TKIP
       group=CCMP TKIP

Note: Add needed changes for using AES256 WPA encryption.

auto eth0
iface eth0 inet dhcp
pre-up wpa_supplicant -Bw -Dwext -ieth0 -c/etc/wpa_supplicant.conf
post-down killall -q wpa_supplicant

On-Screen Keyboard Notes

Due to the tablet nature of the PadOrbiter, an on-screen keyboard was necessary. It is embedded directly into the configuration window itself. I had tried various external keyboards, but was unsuccessful in finding a keyboard that was easy to use for this purpose.

The Keyboard merely appends the given letter to the cursor position (or removes it in the case of backspace) of the text field.

Method Snippets

In order for the xtest send fake key event function to work, it needs the active display. This can be gotten from this member function:

Display * QX11Info::display ()   [static]
Returns the default display for the application.
See also appScreen().

TODO: Find which ESSIDs are legal. Do I need to create an extended keyboard to support funky characters?


  • Finish TabletCFG (CRITICAL)
  • Replace bootscreen with LinuxMCE splash. (NICE TO HAVE)
  • Modify Orbiter to allow for automatic configuration without needing to create an orbiter in the web admin. (CRITICAL)
  • Optimize Boot process. (NICE TO HAVE)
  • Do Installer (SOON)


There are some differences between the DT336 and DT360, though they are very similar. -- Jimbodude 05:44, 22 November 2008 (CET)

VIA 6656 WiFi Card

There is a Mini PCI Express Wifi card in the DT360. It's a VIA 6656 based card. The most recent drivers can be found at the VIA arena. There are several issues with this driver:

  • There are no packaged versions of the kernel module (vntwusb) because the license is ambiguous
  • The license in the code is "Proprietary", even though it uses GPL-only features, so it won't compile on newer kernels
  • To use WPA, it is necessary to compile a custom version of WPA Supplicant with the viawget wpa driver, which is not the most up to date version.
    • This custom wpa driver is NOT wext - this means TabletCFG needs to change the way it generates things

As of this writing, the most recent version was 1.18. This version does not compile due to the license setting in the code. (If this setting is changed, the code compiles and runs, but does not function.) It does work on the Debian Stale kernel.

Replacing the PCI-Ex card or using a USB WiFi adapter is the current workaround.


The touchscreen is the same as the DT336, but the Y coordinates are inverted. Running penmount's gCalib fixes this. (Use the SUSE 11 package for the 9000 series touchscreen)

The resulting /etc/penmount.dat file is:

25 91 110 548 110 1009 112 1473 115 1939 112 92 560 546 564 1016 562 1480 561 1941 550 89 1012 545 1012 1011 1010 1473 1014 1936 1020 91 1476 546 1473 1014 1475 1481 1474 1942 1483 92 1924 547 1928 1011 1929 1473 1926 1937 1931 1 

Geode Graphics

Graphics are provided by the geode xorg driver. The tablet also seems to require the video=ofonly kernel option with the standard Debian installation - without it, the display pulses white every few seconds.

Drive Size

The flash drive in the DT360 is slightly smaller than the DT366 - by about 26MB. This makes DD images not directly compatible between the two versions.