From 1711434fb794d93208f528118e256dc7fb3afcdf Mon Sep 17 00:00:00 2001 From: alexlan Date: Sun, 6 Jul 2008 02:07:47 +0000 Subject: [PATCH] Patch from Kevin Page : - corrected documentation for visor module use - removed 60-pilot.rules in preference to upstream's 60-libpisock.rules to match README.fedora --- 60-pilot.rules | 1 - README.fedora | 25 ++++++++++++++++++------- pilot-link.spec | 7 ++++--- 3 files changed, 22 insertions(+), 11 deletions(-) delete mode 100644 60-pilot.rules diff --git a/60-pilot.rules b/60-pilot.rules deleted file mode 100644 index 291d0ce..0000000 --- a/60-pilot.rules +++ /dev/null @@ -1 +0,0 @@ -BUS=="usb", SYSFS{product}=="Palm Handheld*|Handspring*",KERNEL=="ttyUSB[13579]", SYMLINK="pilot", GROUP="uucp", MODE="0660" diff --git a/README.fedora b/README.fedora index caadc8f..6ea6702 100644 --- a/README.fedora +++ b/README.fedora @@ -39,19 +39,30 @@ Unfortunately this solution is inherently imperfect when used with udev 1) disable libusb: remove (or comment out the contents) of /etc/modprobe.d/blacklist-visor -2) Configure udev to detect the Palm and create /dev/pilot: copy -60-pilot.rules from /usr/share/pilot-link/udev/ to /etc/udev/rules.d/ +2) Configure udev to detect the Palm: +2a) copy 60-libpisock.rules from /usr/share/pilot-link/udev/ to +/etc/udev/rules.d/ +2b) within 60-libpisock.rules change all instances of GROUP="dialout" to +GROUP="uucp" 3) Configure permissions so that a console user can access /dev/pilot: copy 60-pilot.perms from /usr/share/pilot-link/udev/ to /etc/security/console.perms.d/ -If your palm is not working you could try to change the symlink -created in 60-pilot.rules - change the tag KERNEL=="ttyUSB[13579]" to -KERNEL=="ttyUSB[02468]". +When you connect your Palm handheld, watch /var/log/messages - the visor +module should create two ttyUSB devices. Depending on your handheld +model you will need to use either the first or second of these as the +--port argument with pilot-link based programs. -For a discussion of the inherent problems related to the Visor module, -see: +Some users like the convenience of linking this device to /dev/pilot. +To do this add SYMLINK="pilot" and one of either KERNEL=="ttyUSB[02468]" +or KERNEL=="ttyUSB[13579]" to each line in 60-libpisock.rules, depending +on whether you need to use the first or second visor ttyUSB device. +N.B. This is inherently unreliable since another driver could create an +odd number of ttyUSB devices before the /dev/pilot symlink is created. + +For further discussion of the inherent problems related to the Visor +module, see: https://bugzilla.redhat.com/show_bug.cgi?id=158809 diff --git a/pilot-link.spec b/pilot-link.spec index 1db6a6c..cd93cbf 100644 --- a/pilot-link.spec +++ b/pilot-link.spec @@ -3,7 +3,7 @@ Name: pilot-link Version: 0.12.3 -Release: 13%{?dist} +Release: 14%{?dist} Epoch: 2 License: GPLv2 and GPLv2+ and LGPLv2+ and TCL Group: Applications/Communications @@ -14,7 +14,6 @@ Source0: pilot-link-%{version}.tar.bz2 Source3: blacklist-visor Source4: README.fedora Source5: 60-pilot.perms -Source6: 60-pilot.rules ExcludeArch: s390 s390x #Patch1: pilot-link-0.11.0-perlmd5.patch # May be still applied @@ -151,7 +150,6 @@ cp %{SOURCE4} README.fedora # install visor configs to share/udev install -p -m644 %{SOURCE5} %{buildroot}%{_datadir}/pilot-link/udev -install -p -m644 %{SOURCE6} %{buildroot}%{_datadir}/pilot-link/udev %post -p /sbin/ldconfig @@ -181,6 +179,9 @@ rm -rf %{buildroot} %{_datadir}/aclocal/*.m4 %changelog +* Fri Jun 06 2008 Kevin Page - 2:0.12.3-14 +- corrected documentation for visor module use + * Wed Mar 26 2008 Ivana Varekova 2:0.12.3-13 - remove HAL/PolicyKit staff (is in hal package now)