Attachment 308517 Details for Bug 280251 – Fix visor module fallback config and documentation

[patch] Fix visor module fallback config and documentation

pilot-link-fixeddoc-krp.patch (text/plain), 6.83 KB, created by Kevin R. Page on 2008-06-06 08:21:50 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Kevin R. Page

Created: 2008-06-06 08:21:50 UTC

Size: 6.83 KB

patch

obsolete

>diff -urN pilot-link.orig/F-8/60-pilot.rules pilot-link.newdoc/F-8/60-pilot.rules
>--- pilot-link.orig/F-8/60-pilot.rules	2008-01-10 13:47:21.000000000 +0000
>+++ pilot-link.newdoc/F-8/60-pilot.rules	1970-01-01 01:00:00.000000000 +0100
>@@ -1 +0,0 @@
>-BUS=="usb", SYSFS{product}=="Palm Handheld*|Handspring*",KERNEL=="ttyUSB[13579]", SYMLINK="pilot", GROUP="uucp", MODE="0660"
>diff -urN pilot-link.orig/F-8/pilot-link.spec pilot-link.newdoc/F-8/pilot-link.spec
>--- pilot-link.orig/F-8/pilot-link.spec	2008-06-06 09:07:25.000000000 +0100
>+++ pilot-link.newdoc/F-8/pilot-link.spec	2008-06-06 09:04:48.000000000 +0100
>@@ -3,7 +3,7 @@
> 
> Name: pilot-link
> Version: 0.12.2
>-Release: 20%{?dist}
>+Release: 21%{?dist}
> Epoch: 2
> License: GPLv2 and GPLv2+ and LGPLv2+ and TCL
> Group: Applications/Communications
>@@ -18,7 +18,6 @@
> Source4: blacklist-visor
> Source5: README.fedora
> Source6: 60-pilot.perms
>-Source7: 60-pilot.rules
> 
> ExcludeArch: s390 s390x
> #Patch1: pilot-link-0.11.0-perlmd5.patch  # May be still applied
>@@ -162,7 +161,6 @@
> 
> # install visor configs to share/udev
> install -p -m644 %{SOURCE6} %{buildroot}%{_datadir}/pilot-link/udev
>-install -p -m644 %{SOURCE7} %{buildroot}%{_datadir}/pilot-link/udev
> 
> %post -p /sbin/ldconfig
> 
>@@ -196,6 +194,9 @@
> %{_datadir}/aclocal/*.m4
> 
> %changelog
>+* Fri Jun 06 2008 Kevin Page <krp[AT]fedoraproject org> - 2:0.12.2-21
>+- corrected documentation for visor module use
>+
> * Fri May 23 2008 Kevin Page <krp[AT]fedoraproject org> - 2:0.12.2-20
> - Resolves: #280251
>   change hal rules to subsitute for pending hal-0.5.11
>diff -urN pilot-link.orig/F-8/README.fedora pilot-link.newdoc/F-8/README.fedora
>--- pilot-link.orig/F-8/README.fedora	2008-01-10 13:53:12.000000000 +0000
>+++ pilot-link.newdoc/F-8/README.fedora	2008-06-06 09:02:16.000000000 +0100
>@@ -39,19 +39,30 @@
> 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.
>+
>+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 a discussion of the inherent problems related to the Visor module,
>-see:
>+For further discussion of the inherent problems related to the Visor 
>+module, see:
> https://bugzilla.redhat.com/show_bug.cgi?id=158809
> 
> 
>diff -urN pilot-link.orig/F-9/60-pilot.rules pilot-link.newdoc/F-9/60-pilot.rules
>--- pilot-link.orig/F-9/60-pilot.rules	2008-01-11 09:45:55.000000000 +0000
>+++ pilot-link.newdoc/F-9/60-pilot.rules	1970-01-01 01:00:00.000000000 +0100
>@@ -1 +0,0 @@
>-BUS=="usb", SYSFS{product}=="Palm Handheld*|Handspring*",KERNEL=="ttyUSB[13579]", SYMLINK="pilot", GROUP="uucp", MODE="0660"
>diff -urN pilot-link.orig/F-9/pilot-link.spec pilot-link.newdoc/F-9/pilot-link.spec
>--- pilot-link.orig/F-9/pilot-link.spec	2008-03-26 12:25:47.000000000 +0000
>+++ pilot-link.newdoc/F-9/pilot-link.spec	2008-06-06 09:05:50.000000000 +0100
>@@ -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 @@
> 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 @@
> 
> # 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 @@
> %{_datadir}/aclocal/*.m4
> 
> %changelog
>+* Fri Jun 06 2008 Kevin Page <krp[AT]fedoraproject org> - 2:0.12.3-14
>+- corrected documentation for visor module use
>+
> * Wed Mar 26 2008 Ivana Varekova <varekova@redhat.com> 2:0.12.3-13
> - remove HAL/PolicyKit staff (is in hal package now)
> 
>diff -urN pilot-link.orig/F-9/README.fedora pilot-link.newdoc/F-9/README.fedora
>--- pilot-link.orig/F-9/README.fedora	2008-01-11 09:45:55.000000000 +0000
>+++ pilot-link.newdoc/F-9/README.fedora	2008-06-06 08:56:53.000000000 +0100
>@@ -39,19 +39,30 @@
> 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.
>+
>+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 a discussion of the inherent problems related to the Visor module,
>-see:
>+For further discussion of the inherent problems related to the Visor 
>+module, see:
> https://bugzilla.redhat.com/show_bug.cgi?id=158809
> 
>

Actions: View | Diff

Attachments on bug 280251: 284421 | 294103 | 294520 | 294521 | 295803 | 306554 | 308517 | 309418