| 1 |
neysx 07/10/08 10:28:03 |
| 2 |
|
| 3 |
Added: pda-guide.xml |
| 4 |
Log: |
| 5 |
Removed outdated drafts, moved pda-guide to /doc/en/ with added disclaimer |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.1 xml/htdocs/doc/en/pda-guide.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/pda-guide.xml?rev=1.1&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/pda-guide.xml?rev=1.1&content-type=text/plain |
| 12 |
|
| 13 |
Index: pda-guide.xml |
| 14 |
=================================================================== |
| 15 |
<?xml version='1.0' encoding="UTF-8"?> |
| 16 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 17 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/pda-guide.xml,v 1.1 2007/10/08 10:28:03 neysx Exp $ --> |
| 18 |
|
| 19 |
<guide disclaimer="draft"> |
| 20 |
<title>Gentoo PDA Guide</title> |
| 21 |
|
| 22 |
<author title="Author"> |
| 23 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
| 24 |
</author> |
| 25 |
<author title="Author"> |
| 26 |
<mail link="chriswhite@g.o">Chris White</mail> |
| 27 |
</author> |
| 28 |
|
| 29 |
<abstract> |
| 30 |
Nowadays, personal digital assistants, or PDAs, are quite popular. Not only do |
| 31 |
they provide more features than before, they are also easy to handle, even by |
| 32 |
people who aren't that computer literate. But how can you synchronise these PDAs |
| 33 |
with your Gentoo Linux installation if they are almost all running Windows |
| 34 |
Mobile? |
| 35 |
</abstract> |
| 36 |
|
| 37 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 38 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 39 |
<license/> |
| 40 |
|
| 41 |
<version>1.0</version> |
| 42 |
<date>2007-09-27</date> |
| 43 |
|
| 44 |
<chapter> |
| 45 |
<title>Setting up PDA Support</title> |
| 46 |
<section> |
| 47 |
<title>Introduction</title> |
| 48 |
<body> |
| 49 |
|
| 50 |
<p> |
| 51 |
PDAs are everywhere. They are an evolution of the paper journals and address |
| 52 |
books and have become very feature-rich: addresses and telephone numbers, |
| 53 |
pictures and movies, small spreadsheets or documents, calender entries, ... |
| 54 |
anything is possible with PDAs. And thanks to wireless technology, PDAs can |
| 55 |
manipulate or receive data from various devices (like GPS devices or other PDAs) |
| 56 |
or join the world-wide Internet. |
| 57 |
</p> |
| 58 |
|
| 59 |
<p> |
| 60 |
However, most PDAs run a propriatary operating system and might not be easy to |
| 61 |
synchronise with your computer if you are not running software of the same |
| 62 |
vendor. Luckily, the free software community has made serious efforts in reverse |
| 63 |
engineering access to the PDAs and some companies have even opened their |
| 64 |
specification to connect with the PDA. This guide will cover accessing and |
| 65 |
synchronizing PDAs with your system. |
| 66 |
</p> |
| 67 |
|
| 68 |
</body> |
| 69 |
</section> |
| 70 |
<section> |
| 71 |
<title>Kernel Setup</title> |
| 72 |
<body> |
| 73 |
|
| 74 |
<p> |
| 75 |
The first thing we need to do is get the kernel to recognize our device. Open up |
| 76 |
the kernel configuration (for instance, through <c>make menuconfig</c>) and add |
| 77 |
support for your PDA. If your device uses USB to connect to a computer you will |
| 78 |
most likely find support for it under <e>Device Drivers -> USB support -> |
| 79 |
USB Serial Converter support</e>. For instance, iPAQ users (and many others) can |
| 80 |
use the <e>USB PocketPC PDA Driver</e>. |
| 81 |
</p> |
| 82 |
|
| 83 |
<pre caption="Kernel Driver Setup"> |
| 84 |
<M> USB Serial Converter support |
| 85 |
[ ] USB Serial Console device support (EXPERIMENTAL) |
| 86 |
[ ] USB Generic Serial Driver |
| 87 |
< > USB Belkin and Peracom Single Port Serial Driver |
| 88 |
< > USB ConnectTech WhiteHEAT Serial Driver |
| 89 |
< > USB Digi International AccelePort USB Serial Driver |
| 90 |
< > USB Cypress M8 USB Serial Driver |
| 91 |
< > USB Empeg empeg-car Mark I/II Driver |
| 92 |
< > USB FTDI Single Port Serial Driver (EXPERIMENTAL) |
| 93 |
< > USB Handspring Visor / Palm m50x / Sony Clie Driver |
| 94 |
<M> USB PocketPC PDA Driver |
| 95 |
</pre> |
| 96 |
|
| 97 |
<p> |
| 98 |
You might wonder why it is called a <e>Serial Converter</e>. This is because you |
| 99 |
are going to use USB (technology) to talk with your device, even though the |
| 100 |
device itself is accessed using a serial protocol. |
| 101 |
</p> |
| 102 |
|
| 103 |
<p> |
| 104 |
You will also need asynchronous PPP support: |
| 105 |
</p> |
| 106 |
|
| 107 |
<pre caption="Kernel Driver Setup for Async PPP"> |
| 108 |
Device Drivers ---> |
| 109 |
Network device support ---> |
| 110 |
<M> PPP (point-to-point protocol) support |
| 111 |
<M> PPP support for async serial ports |
| 112 |
</pre> |
| 113 |
|
| 114 |
<p> |
| 115 |
Rebuild the kernel and its modules. If you only had to modify a module, you can |
| 116 |
install the modules and continue. Otherwise, set up the new kernel in your boot |
| 117 |
loader and reboot. |
| 118 |
</p> |
| 119 |
|
| 120 |
</body> |
| 121 |
</section> |
| 122 |
<section> |
| 123 |
<title>Detecting Your PDA</title> |
| 124 |
<body> |
| 125 |
|
| 126 |
<p> |
| 127 |
Ok, now that we have the kernel module setup, let's go ahead and get some |
| 128 |
information. Plug in your device and take a look at your modules list if |
| 129 |
you have build support for the device as a kernel module: |
| 130 |
</p> |
| 131 |
|
| 132 |
<pre caption="Checking if your PDA is detected"> |
| 133 |
# <i>lsmod</i> |
| 134 |
Module Size Used by |
| 135 |
ipaq 30736 0 |
| 136 |
usbserial 25120 1 ipaq |
| 137 |
<comment>(...)</comment> |
| 138 |
|
| 139 |
# <i>dmesg | grep Pocket</i> |
| 140 |
drivers/usb/serial/usb-serial.c: USB Serial support registered for PocketPC PDA |
| 141 |
drivers/usb/serial/ipaq.c: USB PocketPC PDA driver v0.5 |
| 142 |
ipaq 3-2:1.0: PocketPC PDA converter detected |
| 143 |
usb 3-2: PocketPC PDA converter now attached to ttyUSB0 |
| 144 |
|
| 145 |
# <i>ls -la /dev/ttyUSB0</i> |
| 146 |
crw-rw---- 1 root uucp 188, 0 Sep 27 19:21 /dev/ttyUSB0 |
| 147 |
</pre> |
| 148 |
|
| 149 |
<p> |
| 150 |
As we can see, the device has been detected and is now accessible through |
| 151 |
<path>/dev/ttyUSB0</path>. |
| 152 |
</p> |
| 153 |
|
| 154 |
</body> |
| 155 |
</section> |
| 156 |
</chapter> |
| 157 |
|
| 158 |
<chapter> |
| 159 |
<title>Using SynCE</title> |
| 160 |
<section> |
| 161 |
<title>Introduction</title> |
| 162 |
<body> |
| 163 |
|
| 164 |
<p> |
| 165 |
<uri link="http://www.synce.org">SynCE</uri> is the tool you can use to connect |
| 166 |
to and work with Windows Mobile and Windows CE powered devices. The tool |
| 167 |
connects, through the device set up earlier, to the device and allows |
| 168 |
applications to synchronise appointments, addresses and more. |
| 169 |
</p> |
| 170 |
|
| 171 |
<p> |
| 172 |
A list of devices supported through SynCE can be found on the |
| 173 |
<uri link="http://www.synce.org">SynCE website</uri>. |
| 174 |
</p> |
| 175 |
|
| 176 |
<p> |
| 177 |
SynCE is not available through a stable ebuild though, so before installing it, |
| 178 |
you will first need to mark them in <path>/etc/portage/package.keywords</path>. |
| 179 |
</p> |
| 180 |
|
| 181 |
<pre caption="List of packages to list in package.keywords"> |
| 182 |
app-pda/synce |
| 183 |
app-pda/synce-software-manager |
| 184 |
app-pda/synce-librapi2 |
| 185 |
app-pda/synce-libsynce |
| 186 |
app-pda/synce-multisync_plugin |
| 187 |
app-pda/synce-rra |
| 188 |
dev-libs/libmimedir |
| 189 |
app-pda/synce-dccm |
| 190 |
app-pda/synce-trayicon |
| 191 |
app-pda/orange |
| 192 |
app-pda/dynamite |
| 193 |
app-pda/synce-kde |
| 194 |
app-pda/synce-gnomevfs |
| 195 |
app-pda/synce-serial |
| 196 |
</pre> |
| 197 |
|
| 198 |
<p> |
| 199 |
Then, install the <c>app-pda/synce</c> and <c>net-dialup/ppp</c> packages to |
| 200 |
obtain the necessary tools. |
| 201 |
</p> |
| 202 |
|
| 203 |
</body> |
| 204 |
</section> |
| 205 |
<section> |
| 206 |
<title>Configuring the PDA</title> |
| 207 |
<body> |
| 208 |
|
| 209 |
<p> |
| 210 |
The next task is to configure the serial device we found earlier |
| 211 |
(<path>/dev/ttyUSB0</path> in our example) to be used with SynCE: |
| 212 |
</p> |
| 213 |
|
| 214 |
<pre caption="Configuring the serial device for SynCE"> |
| 215 |
~# <i>synce-serial-config ttyUSB0</i> |
| 216 |
|
| 217 |
You can now run synce-serial-start to start a serial connection. |
| 218 |
</pre> |
| 219 |
|
| 220 |
<p> |
| 221 |
This step only has to be performed once: it stored the necessary PPP-related |
| 222 |
information inside <path>/etc/ppp/peers/synce-device</path> which is read by PPP |
| 223 |
when it is called by <c>synce-serial-start</c>. |
| 224 |
</p> |
| 225 |
|
| 226 |
</body> |
| 227 |
</section> |
| 228 |
<section> |
| 229 |
<title>Accessing The Device</title> |
| 230 |
<body> |
| 231 |
|
| 232 |
<p> |
| 233 |
Now, log on as the user who will be using the PDA and run the <c>vdccm</c> |
| 234 |
command. This tool is the connection manager for SynCE through which programs |
| 235 |
connect to the device. |
| 236 |
</p> |
| 237 |
|
| 238 |
<pre caption="Launching the connection manager"> |
| 239 |
~$ <i>vdccm</i> |
| 240 |
</pre> |
| 241 |
|
| 242 |
<p> |
| 243 |
As root again, run <c>synce-serial-start</c> which will connect to the device. |
| 244 |
With some PDAs, you will notice this on the PDA itself through a synchronisation |
| 245 |
symbol or any other event. |
| 246 |
</p> |
| 247 |
|
| 248 |
<pre caption="Running synce-serial-start"> |
| 249 |
~# <i>synce-serial-start</i> |
| 250 |
</pre> |
| 251 |
|
| 252 |
<p> |
| 253 |
In some cases, the first attempts fail but this isn't shown immediately. You |
| 254 |
can rerun the command a few times until the command replies that a serial |
| 255 |
connection is already started. To verify that the connection is done, check if a |
| 256 |
ppp interface (like ppp0) is created and has an IP address attached to it. |
| 257 |
</p> |
| 258 |
|
| 259 |
<p> |
| 260 |
TODO default route gone? rerun dhcpcd, but this shouldn't happen. |
| 261 |
</p> |
| 262 |
|
| 263 |
</body> |
| 264 |
</section> |
| 265 |
<section> |
| 266 |
<title>File Navigation and Manipulation</title> |
| 267 |
<body> |
| 268 |
|
| 269 |
<p> |
| 270 |
The SynCE project provides a number of programs to communicate with the PDA and |
| 271 |
exchange files. The tools have similar namings as on a regular Unix system but |
| 272 |
with a <c>p</c> prepended to it: <c>pcp</c>, <c>pls</c>, <c>pmv</c>, <c>prm</c>, |
| 273 |
<c>pmkdir</c>, <c>prmdir</c>. Other tools are specific for PDAs, like |
| 274 |
<c>prun</c> to launch a program, <c>synce-install-cab</c> to install a CAB file |
| 275 |
or <c>pstatus</c> to display information about the device. |
| 276 |
</p> |
| 277 |
|
| 278 |
<p> |
| 279 |
Beware though, the behavior of the tools is not all that intuïtive. For |
| 280 |
instance, the <c>pls</c> tool shows the contents of the <path>My |
| 281 |
Documents</path> directory whereas the <c>pcp</c> tool starts from the <path>My |
| 282 |
Device</path> location. As an example, we'll upload a file to the <path>My |
| 283 |
Documents</path> folder: |
| 284 |
</p> |
| 285 |
|
| 286 |
<pre caption="Uploading a file"> |
| 287 |
~$ <i>pls</i> |
| 288 |
Directory Tue 01 Jan 2002 01:00:00 PM CET Business/ |
| 289 |
Directory Tue 01 Jan 2002 01:00:00 PM CET Personal/ |
| 290 |
Directory Tue 01 Jan 2002 01:00:00 PM CET Templates/ |
| 291 |
~$ <i>pcp music.mp3 :"My Documents/music.mp3"</i> |
| 292 |
File copy of 3852416 bytes took 0 minutes and 38 seconds, that's 101379 bytes/s. |
| 293 |
~$ <i>pls</i> |
| 294 |
Archive 3852416 Wed 02 Jan 2002 07:05:06 PM CET music.mp3 |
| 295 |
Directory Tue 01 Jan 2002 01:00:00 PM CET Business/ |
| 296 |
Directory Tue 01 Jan 2002 01:00:00 PM CET Personal/ |
| 297 |
Directory Tue 01 Jan 2002 01:00:00 PM CET Templates/ |
| 298 |
</pre> |
| 299 |
|
| 300 |
</body> |
| 301 |
</section> |
| 302 |
<section> |
| 303 |
<title>SynCE for KDE Project</title> |
| 304 |
<body> |
| 305 |
|
| 306 |
<p> |
| 307 |
The <uri link="http://synce.sourceforge.net/synce/kde/">SynCE for KDE |
| 308 |
Project</uri> aims to support PDAs within KDE by facilitating file exchange, |
| 309 |
synchronisation and installation and even provide mirroring capabilities so you |
| 310 |
can control your PDA from within KDE. |
| 311 |
</p> |
| 312 |
|
| 313 |
|
| 314 |
<p> |
| 315 |
The <c>raki</c> tool is SynCE's PocketPC management tool for KDE. The first time |
| 316 |
you launch it, it asks whether you use <c>dccm</c> or <c>vdccm</c>. Once you |
| 317 |
selected the connection manager you use (in our example it would be |
| 318 |
<c>vdccm</c>) your KDE session (or any environment which supports KDE applets) |
| 319 |
will now have a PDA applet from which you can browse and synchronise your PDA. |
| 320 |
</p> |
| 321 |
|
| 322 |
</body> |
| 323 |
</section> |
| 324 |
</chapter> |
| 325 |
|
| 326 |
<chapter> |
| 327 |
<title>MultiSync</title> |
| 328 |
<section> |
| 329 |
<title>Introduction</title> |
| 330 |
<body> |
| 331 |
|
| 332 |
<p> |
| 333 |
The <uri link="http://multisync.sourceforge.net/news.php">MultiSync</uri> |
| 334 |
project provides plugins for various Gnome and Gnome related tools, including |
| 335 |
Evolution, to synchronise data with external devices, including PDAs. MultiSync |
| 336 |
uses SynCE to communicate with Windows CE/Mobile devices although it also |
| 337 |
supports PDAs that run non-Windows operating systems. |
| 338 |
</p> |
| 339 |
|
| 340 |
</body> |
| 341 |
</section> |
| 342 |
</chapter> |
| 343 |
|
| 344 |
</guide> |
| 345 |
|
| 346 |
|
| 347 |
|
| 348 |
-- |
| 349 |
gentoo-doc-cvs@g.o mailing list |
Archives