Bug#484236: libpisock9 shouldn't blacklist visor module
On Tue, Jun 03, 2008 at 10:38:27PM +0200, Ludovic Rousseau wrote: It is a regression for you but a real benefit for many users. Using libusb is much faster that using the visor kernel module. From pilot-link 0.12.0 version release notes: We now have native libusb support. With libusb, you can synchronize your Palm device without using the Linux kernel visor driver. You also get a 60%-80% increase in speed. You can remove the visor blacklist on your local system. But I do not plan to do this in the Debian package. OK. Sorry for not having responded earlier. Maybe you can close this one and/or tag it as wontfix ? In waiting for #459500 to be fixed, I commented the backlist in /etc/modprobe.d/libpisock9 and got it working again. Thanks for your help. Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#484236: libpisock9 shouldn't blacklist visor module
Package: libpisock9 Version: 0.12.3-4+b1 Severity: important libpisock9 seems to assume that visor module should no longer be loaded, and instead of using its devices /dev/ttyUSB* one should now sync over usb:. However, as explained in #459500, it won't work for my Sony CLié over usb: Thus, I think that the module shouldn't be blacklisted in /etc/modprobe.d/libpisock9, allowing the autoloading of visor once trying to sync, which renders /dev/ttyUSB* devices usable, as was previously. Hope this regression can be fixed. Best regards, P.S.: Similar report in Ubuntu : https://bugs.launchpad.net/ubuntu/+source/gnome-pilot/+bug/108512 -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libpisock9 depends on: ii libbluetooth23.30-1 Library to use the BlueZ Linux Blu ii libc62.7-10 GNU C Library: Shared libraries ii libusb-0.1-4 2:0.1.12-11 userspace USB programming library libpisock9 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484236: libpisock9 shouldn't blacklist visor module
Olivier Berger a écrit : Package: libpisock9 Version: 0.12.3-4+b1 Severity: important libpisock9 seems to assume that visor module should no longer be loaded, and instead of using its devices /dev/ttyUSB* one should now sync over usb:. Exact. However, as explained in #459500, it won't work for my Sony CLié over usb: I reported the bug upstream to pilot-link. No news yet. Thus, I think that the module shouldn't be blacklisted in /etc/modprobe.d/libpisock9, allowing the autoloading of visor once trying to sync, which renders /dev/ttyUSB* devices usable, as was previously. Hope this regression can be fixed. It is a regression for you but a real benefit for many users. Using libusb is much faster that using the visor kernel module. From pilot-link 0.12.0 version release notes: We now have native libusb support. With libusb, you can synchronize your Palm device without using the Linux kernel visor driver. You also get a 60%-80% increase in speed. You can remove the visor blacklist on your local system. But I do not plan to do this in the Debian package. Regards, -- Dr. Ludovic Rousseau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
