Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
On Tuesday 08 August 2006 04:15, Adeodato Simó wrote: * Felix Homann [Wed, 26 Jul 2006 10:12:11 +0200]: On Tuesday 25 July 2006 16:23, Filippo Giunchedi wrote: okay, I've updated bluetooth.sh and bluez-pcmcia-support.udev again, do you mind trying if it works as expected? It works as expected. Does this mean the bug is fixed in version 3.1-3 of the package, and so the bug can be closed? Yes, it can IMO. Kind regards, Felix
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
* Felix Homann [Wed, 26 Jul 2006 10:12:11 +0200]: On Tuesday 25 July 2006 16:23, Filippo Giunchedi wrote: okay, I've updated bluetooth.sh and bluez-pcmcia-support.udev again, do you mind trying if it works as expected? It works as expected. Does this mean the bug is fixed in version 3.1-3 of the package, and so the bug can be closed? Thanks, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org Under capitalism, man exploits man. Under communism, it's just the opposite. -- J.K. Galbraith
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
On Tuesday 25 July 2006 16:23, Filippo Giunchedi wrote:
okay, I've updated bluetooth.sh and bluez-pcmcia-support.udev again, do you
mind trying if it works as expected?
It works as expected.
Also can you paste the relevant udev
database entry for your card?
Here you go:
P: /class/tty/ttyS2
N: ttyS2
E: MANFID=0x025e
E: CARD_ID=0x1000
E: DEVICENAME=
searching the output of udevinfo -e might
help. Only the mapping for $DEVICENAME is left to figure out.
I don't understand what you expect here. As far as I can tell $DEVICENAME
_has_ to be empty since $name is not a valid key (at least not mentioned
in 'man udev'). It is not needed or used anywhere, so I think that
ENV{DEVICENAME}=$name should be removed.
If it was meant as a reaction on Marcel's remark about the DEVICE=`echo
$DEVNAME|sed -e 's_/dev/__'` line in bluetooth.sh you can safely remove
that line and use
/usr/sbin/hciattach $DEVNAME ...
I agree with Marcel in that the script should be renamed
into bluetooth_serial (and every other point he made!).
Kind regards,
Felix
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
On Fri, Jul 21, 2006 at 02:07:49PM +0200, Kay Sievers wrote:
The solution is to replace ENV{BUS} by ENV{PHYSDEVBUS} in
bluez-pcmcia-support.udev and to correspondingly change $DEVPATH to
$PHYSDEVPATH in bluetooth.sh, i. e. revert to the solution I sent in
#351106.
ENV{BUS} never existed, so it can't work. The PHYDEV* values are
deprecated and and should better not be used. They will not go away
soon, but if that can be solved without them, it would be nice.
PHYSDEVBUS is just the subsystem of the parent device, which can
probably be matched with BUS==pcmcia.
I've modified the rules file, it is available at
http://svn.debian.org/wsvn/pkg-bluetooth/bluez-utils/trunk/debian/bluez-pcmcia-support.udev?op=filerev=0sc=0
and the bluetooth.sh invoked on RUN available at
http://svn.debian.org/wsvn/pkg-bluetooth/bluez-utils/trunk/debian/bluetooth.sh?op=filerev=0sc=0
what about the change from DEVPATH to PHYSDEVPATH Felix proposed in
bluetooth.sh?
Felix: do you mind trying the first file to see if it works for you?
thanks in advance,
filippo
--
Filippo Giunchedi - http://esaurito.net
PGP key: 0x6B79D401
random quote follows:
UNIX IS user friendly, it is just selective who his friends are.
signature.asc
Description: Digital signature
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
On Tuesday 25 July 2006 11:12, Filippo Giunchedi wrote: I've modified the rules file, it is available at http://svn.debian.org/wsvn/pkg-bluetooth/bluez-utils/trunk/debian/bluez-pcm cia-support.udev?op=filerev=0sc=0 and the bluetooth.sh invoked on RUN available at http://svn.debian.org/wsvn/pkg-bluetooth/bluez-utils/trunk/debian/bluetooth .sh?op=filerev=0sc=0 what about the change from DEVPATH to PHYSDEVPATH Felix proposed in bluetooth.sh? Felix: do you mind trying the first file to see if it works for you? It's working, but only if PHYSDEVPATH is used in bluetooth.sh. Kind regards, Felix -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
On Tuesday 25 July 2006 11:12, Filippo Giunchedi wrote: what about the change from DEVPATH to PHYSDEVPATH Felix proposed in bluetooth.sh? Hi again, MANFID=`cat /sys/$PHYSDEVPATH/manf_id`,`cat /sys/$PHYSDEVPATH/card_id` and MANFID=`cat /sys/$DEVPATH/device/manf_id`,`cat /sys/$DEVPATH/device/card_id` seem to be equivalent in this setting. I don't know if either one is prefered or deprecated, but I would now prefer the latter since it's simpler: $DEVPATH - /class/tty/ttyS2 $PHYSDEVPATH - /devices/pci:00/:00:1e.0/:06:01.0/0.0 (on insertion of a SPHINX card) Kind regards, Felix -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
On Tue, 2006-07-25 at 12:52 +0200, Felix Homann wrote:
On Tuesday 25 July 2006 11:12, Filippo Giunchedi wrote:
what about the change from DEVPATH to PHYSDEVPATH Felix proposed in
bluetooth.sh?
Hi again,
MANFID=`cat /sys/$PHYSDEVPATH/manf_id`,`cat /sys/$PHYSDEVPATH/card_id`
and
MANFID=`cat /sys/$DEVPATH/device/manf_id`,`cat /sys/$DEVPATH/device/card_id`
seem to be equivalent in this setting. I don't know if either one is prefered
or deprecated, but I would now prefer the latter since it's simpler:
$DEVPATH - /class/tty/ttyS2
$PHYSDEVPATH - /devices/pci:00/:00:1e.0/:06:01.0/0.0
PHYSDEVPATH and the 'device' link are both deprecated and will go away
some day in the future, you better pass the values you want to use in
your script down from udev with $sysfs{}. That is not dependent on a
specific order of devices in sysfs.
Kay
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
On Tue, 2006-07-25 at 15:43 +0200, Felix Homann wrote:
On Tuesday 25 July 2006 13:18, Kay Sievers wrote:
PHYSDEVPATH and the 'device' link are both deprecated and will go away
some day in the future, you better pass the values you want to use in
your script down from udev with $sysfs{}. That is not dependent on a
specific order of devices in sysfs.
I've attached working (for me) rules+bluetooth.sh. $sysfs{manf_id} and
$sysfs{card_id} are passed to bluetooth.sh.
Looks fine, and should not break, if something in sysfs changes, which
is nice.
Btw, you should be able to just do RUN+=bluetooth.sh, as udev will
look in /lib/udev/ if it does not start with a '/'.
Thanks,
Kay
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
On Tuesday 25 July 2006 13:18, Kay Sievers wrote:
PHYSDEVPATH and the 'device' link are both deprecated and will go away
some day in the future, you better pass the values you want to use in
your script down from udev with $sysfs{}. That is not dependent on a
specific order of devices in sysfs.
Kay
Thanks,
I've attached working (for me) rules+bluetooth.sh. $sysfs{manf_id} and
$sysfs{card_id} are passed to bluetooth.sh.
Kind regards,
Felix
## PCMCIA-Cards
# Brain Boxes BL-620 Bluetooth Adapter
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==Brain Boxes,
SYSFS{prod_id2}==Bluetooth PC Card, RUN+=/lib/udev/bluetooth.sh
$sysfs{manf_id} $sysfs{card_id}
# Xircom CreditCard Bluetooth Adapter
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==Xircom,
SYSFS{prod_id3}==CBT, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# Xircom RealPort2 Bluetooth Adapter
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==Xircom,
SYSFS{prod_id3}==CBT, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# IBM Bluetooth PC Card II
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==IBM,
SYSFS{prod_id2}==Bluetooth PC Card II, RUN+=/lib/udev/bluetooth.sh
$sysfs{manf_id} $sysfs{card_id}
# TDK Bluetooth PC Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==TDK,
SYSFS{prod_id2}==Bluetooth PC Card II, RUN+=/lib/udev/bluetooth.sh
$sysfs{manf_id} $sysfs{card_id}
# AmbiCom BT2000C Bluetooth PC/CF Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==AmbiCom BT2000C,
SYSFS{prod_id2}==Bluetooth PC/CF Card, RUN+=/lib/udev/bluetooth.sh
$sysfs{manf_id} $sysfs{card_id}
# COM One Platinium Bluetooth PC Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==COM1 SA,
SYSFS{prod_id2}==MC310 CARD, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# Sphinx PICO Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==SPHINX,
SYSFS{prod_id2}==BT-CARD, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# H-Soft blue+Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==H-Soft,
SYSFS{prod_id2}==Blue+CARD, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# Compaq iPAQ Bluetooth Sleeve
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==CF CARD,
SYSFS{prod_id2}==GENERIC, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# Zoom Bluetooth Card
# Sitecom CN-504 Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==PCMCIA,
SYSFS{prod_id2}==Bluetooth Card, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
#
# dtl1_cs
#
# card Nokia Bluetooth Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==Nokia Mobile Phones,
SYSFS{prod_id2}==DTL-1, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==Nokia Mobile Phones,
SYSFS{prod_id2}==DTL-4, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# Socket Bluetooth Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==Socket,
SYSFS{prod_id2}==CF+ Personal Network Card, RUN+=/lib/udev/bluetooth.sh
$sysfs{manf_id} $sysfs{card_id}
#
# bt3c_cs
#
# 3Com Bluetooth PC Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==3COM,
SYSFS{prod_id3}==Bluetooth PC Card, RUN+=/lib/udev/bluetooth.sh
$sysfs{manf_id} $sysfs{card_id}
#
# bluecard_cs
#
# LSE041 Bluetooth PC Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==BlueCard,
SYSFS{prod_id2}==LSE041, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# LSE039 Bluetooth Compact Flash Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==WSS,
SYSFS{prod_id2}==LSE039, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# LSE139 Bluetooth Compact Flash Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==BTCFCARD,
SYSFS{prod_id2}==LSE139, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
#
# bt950_cs
#
# AmbiCom BT2000E Bluetooth Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==AmbiCom,Inc,
SYSFS{prod_id2}==BT2000E, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# Pretec BT2000E Bluetooth Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==Pretec,
SYSFS{prod_id2}==BT2000E, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# Billionton Bluetooth Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==Compact Flash,
SYSFS{prod_id2}==Bluetooth Card, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
#
# btuart_cs
#
# Cyber-blue Compact Flash Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==BT, SYSFS{prod_id2}==,
SYSFS{prod_id3}==, SYSFS{prod_id4}==, RUN+=/lib/udev/bluetooth.sh
$sysfs{manf_id} $sysfs{card_id}
bluetooth.sh
Description: application/shellscript
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
Hi,
PHYSDEVPATH and the 'device' link are both deprecated and will go away
some day in the future, you better pass the values you want to use in
your script down from udev with $sysfs{}. That is not dependent on a
specific order of devices in sysfs.
I've attached working (for me) rules+bluetooth.sh. $sysfs{manf_id} and
$sysfs{card_id} are passed to bluetooth.sh.
Looks fine, and should not break, if something in sysfs changes, which
is nice.
Btw, you should be able to just do RUN+=bluetooth.sh, as udev will
look in /lib/udev/ if it does not start with a '/'.
this is nice, but there is no need to run bluetooth.sh on non-serial
based Bluetooth cards like the Nokia DTL1 for example. They work
perfectly fine without any additional udev rule.
I also don't like that bluetooth.sh tries to run /etc/init.d/bluetooth,
because this should not be a task of an udev script. Either Bluetooth is
enabled to be started a system boot or not.
The other thing is that this is not Debian specific. So why does nobody
tried to start an upstream discussion on bluez-devel or linux-hotplug
mailing list.
Regards
Marcel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
On Tuesday 25 July 2006 17:12, Marcel Holtmann wrote: this is nice, but there is no need to run bluetooth.sh on non-serial based Bluetooth cards like the Nokia DTL1 for example. They work perfectly fine without any additional udev rule. The rules are essentially taken from SuSE, I don't know where they got them from. I also don't like that bluetooth.sh tries to run /etc/init.d/bluetooth, because this should not be a task of an udev script. Either Bluetooth is enabled to be started a system boot or not. Agreed! The other thing is that this is not Debian specific. So why does nobody tried to start an upstream discussion on bluez-devel or linux-hotplug mailing list. Very good point!!! Kind regards, Felix -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
On Tue, Jul 25, 2006 at 12:52:30PM +0200, Felix Homann wrote: On Tuesday 25 July 2006 11:12, Filippo Giunchedi wrote: what about the change from DEVPATH to PHYSDEVPATH Felix proposed in bluetooth.sh? Hi again, MANFID=`cat /sys/$PHYSDEVPATH/manf_id`,`cat /sys/$PHYSDEVPATH/card_id` and MANFID=`cat /sys/$DEVPATH/device/manf_id`,`cat /sys/$DEVPATH/device/card_id` seem to be equivalent in this setting. I don't know if either one is prefered or deprecated, but I would now prefer the latter since it's simpler: $DEVPATH - /class/tty/ttyS2 $PHYSDEVPATH - /devices/pci:00/:00:1e.0/:06:01.0/0.0 okay, I've updated bluetooth.sh and bluez-pcmcia-support.udev again, do you mind trying if it works as expected? Also can you paste the relevant udev database entry for your card? searching the output of udevinfo -e might help. Only the mapping for $DEVICENAME is left to figure out. thanks, filippo -- Filippo Giunchedi - http://esaurito.net PGP key: 0x6B79D401 random quote follows: Date: Tuesday, 2002/10/22 - 08:09 dselect proves the existence of Satan. It's the worst part of Debian. signature.asc Description: Digital signature
Bug#378839: bluez-pcmcia-support: udev support broken
On Wed, Jul 19, 2006 at 12:16:54PM +0200, Marco d'Itri wrote:
Is this correct?
- Forwarded message from [EMAIL PROTECTED] -
From: [EMAIL PROTECTED]
To: Debian Bug Tracking System [EMAIL PROTECTED]
Subject: bluez-pcmcia-support: udev support broken
Package: bluez-pcmcia-support
Version: 3.1-2
Severity: grave
Justification: renders package unusable
The udev rules supplied by the package don't work. At least on my
system tested with a SPHINX and a Sitecom card.
The solution is to replace ENV{BUS} by ENV{PHYSDEVBUS} in
bluez-pcmcia-support.udev and to correspondingly change $DEVPATH to
$PHYSDEVPATH in bluetooth.sh, i. e. revert to the solution I sent in
#351106.
ENV{BUS} never existed, so it can't work. The PHYDEV* values are
deprecated and and should better not be used. They will not go away
soon, but if that can be solved without them, it would be nice.
PHYSDEVBUS is just the subsystem of the parent device, which can
probably be matched with BUS==pcmcia.
Kay
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378839: bluez-pcmcia-support: udev support broken
Package: bluez-pcmcia-support
Version: 3.1-2
Severity: grave
Justification: renders package unusable
The udev rules supplied by the package don't work. At least on my
system tested with a SPHINX and a Sitecom card.
The solution is to replace ENV{BUS} by ENV{PHYSDEVBUS} in
bluez-pcmcia-support.udev and to correspondingly change $DEVPATH to
$PHYSDEVPATH in bluetooth.sh, i. e. revert to the solution I sent in
#351106.
In addition it is neccessary to link /etc/udev/bluez-pcmcia-support.rules to
/etc/udev/rules.d/86-bluez-pcmcia-support.rules.
Kind regards,
Felix Homann
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.4-jawaka-splash
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages bluez-pcmcia-support depends on:
ii bluez-utils 3.1-2 Bluetooth tools and daemons
ii pcmciautils 014-1 PCMCIA utilities for Linux 2.6
Versions of packages bluez-pcmcia-support recommends:
ii setserial 2.17-43controls configuration of serial p
-- no debconf information
--- bluez-utils-3.1/debian/bluetooth.sh 2006-07-18 23:33:57.0 +0200
+++ bluez-utils-3.1/debian/bluetooth.sh-patched 2006-07-18 23:41:20.0
+0200
@@ -17,7 +17,7 @@ start_serial() {
setserial $DEVNAME irq 0 ; setserial $DEVNAME irq $IRQ
DEVICE=`echo $DEVNAME|sed -e 's_/dev/__'`
- MANFID=`cat /sys/$DEVPATH/manf_id`,`cat /sys/$DEVPATH/card_id`
+ MANFID=`cat /sys/$PHYSDEVPATH/manf_id`,`cat /sys/$PHYSDEVPATH/card_id`
# I don't have a generic solution, sorry
if [ $MANFID = 0x0160,0x0002 ]; then
/usr/sbin/hciattach $DEVICE $MANFID 115200
--- bluez-utils-3.1/debian/bluez-pcmcia-support.udev2006-07-18
23:33:57.0 +0200
+++ bluez-utils-3.1/debian/bluez-pcmcia-support.udev-patched2006-07-18
23:39:15.0 +0200
@@ -1,37 +1,37 @@
## PCMCIA-Cards
# Brain Boxes BL-620 Bluetooth Adapter
-SUBSYSTEM==tty, ENV{BUS}==pcmcia, SYSFS{prod_id1}==Brain Boxes,
SYSFS{prod_id2}==Bluetooth PC Card, RUN+=/lib/udev/bluetooth.sh
+SUBSYSTEM==tty, ENV{PHYSDEVBUS}==pcmcia, SYSFS{prod_id1}==Brain Boxes,
SYSFS{prod_id2}==Bluetooth PC Card, RUN+=/lib/udev/bluetooth.sh
# Xircom CreditCard Bluetooth Adapter
-SUBSYSTEM==tty, ENV{BUS}==pcmcia, SYSFS{prod_id1}==Xircom,
SYSFS{prod_id3}==CBT, RUN+=/lib/udev/bluetooth.sh
+SUBSYSTEM==tty, ENV{PHYSDEVBUS}==pcmcia, SYSFS{prod_id1}==Xircom,
SYSFS{prod_id3}==CBT, RUN+=/lib/udev/bluetooth.sh
# Xircom RealPort2 Bluetooth Adapter
-SUBSYSTEM==tty, ENV{BUS}==pcmcia, SYSFS{prod_id1}==Xircom,
SYSFS{prod_id3}==CBT, RUN+=/lib/udev/bluetooth.sh
+SUBSYSTEM==tty, ENV{PHYSDEVBUS}==pcmcia, SYSFS{prod_id1}==Xircom,
SYSFS{prod_id3}==CBT, RUN+=/lib/udev/bluetooth.sh
# IBM Bluetooth PC Card II
-SUBSYSTEM==tty, ENV{BUS}==pcmcia, SYSFS{prod_id1}==IBM,
SYSFS{prod_id2}==Bluetooth PC Card II, RUN+=/lib/udev/bluetooth.sh
+SUBSYSTEM==tty, ENV{PHYSDEVBUS}==pcmcia, SYSFS{prod_id1}==IBM,
SYSFS{prod_id2}==Bluetooth PC Card II, RUN+=/lib/udev/bluetooth.sh
# TDK Bluetooth PC Card
-SUBSYSTEM==tty, ENV{BUS}==pcmcia, SYSFS{prod_id1}==TDK,
SYSFS{prod_id2}==Bluetooth PC Card II, RUN+=/lib/udev/bluetooth.sh
+SUBSYSTEM==tty, ENV{PHYSDEVBUS}==pcmcia, SYSFS{prod_id1}==TDK,
SYSFS{prod_id2}==Bluetooth PC Card II, RUN+=/lib/udev/bluetooth.sh
# AmbiCom BT2000C Bluetooth PC/CF Card
-SUBSYSTEM==tty, ENV{BUS}==pcmcia, SYSFS{prod_id1}==AmbiCom BT2000C,
SYSFS{prod_id2}==Bluetooth PC/CF Card, RUN+=/lib/udev/bluetooth.sh
+SUBSYSTEM==tty, ENV{PHYSDEVBUS}==pcmcia, SYSFS{prod_id1}==AmbiCom
BT2000C, SYSFS{prod_id2}==Bluetooth PC/CF Card, RUN+=/lib/udev/bluetooth.sh
# COM One Platinium Bluetooth PC Card
-SUBSYSTEM==tty, ENV{BUS}==pcmcia, SYSFS{prod_id1}==COM1 SA,
SYSFS{prod_id2}==MC310 CARD, RUN+=/lib/udev/bluetooth.sh
+SUBSYSTEM==tty, ENV{PHYSDEVBUS}==pcmcia, SYSFS{prod_id1}==COM1 SA,
SYSFS{prod_id2}==MC310 CARD, RUN+=/lib/udev/bluetooth.sh
# Sphinx PICO Card
-SUBSYSTEM==tty, ENV{BUS}==pcmcia, SYSFS{prod_id1}==SPHINX,
SYSFS{prod_id2}==BT-CARD, RUN+=/lib/udev/bluetooth.sh
+SUBSYSTEM==tty, ENV{PHYSDEVBUS}==pcmcia, SYSFS{prod_id1}==SPHINX,
SYSFS{prod_id2}==BT-CARD, RUN+=/lib/udev/bluetooth.sh
# H-Soft blue+Card
-SUBSYSTEM==tty, ENV{BUS}==pcmcia, SYSFS{prod_id1}==H-Soft,
SYSFS{prod_id2}==Blue+CARD, RUN+=/lib/udev/bluetooth.sh
+SUBSYSTEM==tty, ENV{PHYSDEVBUS}==pcmcia, SYSFS{prod_id1}==H-Soft,
SYSFS{prod_id2}==Blue+CARD, RUN+=/lib/udev/bluetooth.sh
# Compaq iPAQ Bluetooth Sleeve
-SUBSYSTEM==tty, ENV{BUS}==pcmcia, SYSFS{prod_id1}==CF CARD,
SYSFS{prod_id2}==GENERIC, RUN+=/lib/udev/bluetooth.sh
+SUBSYSTEM==tty, ENV{PHYSDEVBUS}==pcmcia, SYSFS{prod_id1}==CF CARD,
SYSFS{prod_id2}==GENERIC, RUN+=/lib/udev/bluetooth.sh
# Zoom Bluetooth Card
# Sitecom CN-504 Card
-SUBSYSTEM==tty, ENV{BUS}==pcmcia,
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
[I'm CCing udev maintainer to have some comments (if any)]
On Wed, Jul 19, 2006 at 10:57:04AM +0200, [EMAIL PROTECTED] wrote:
The udev rules supplied by the package don't work. At least on my
system tested with a SPHINX and a Sitecom card.
The solution is to replace ENV{BUS} by ENV{PHYSDEVBUS} in
bluez-pcmcia-support.udev and to correspondingly change $DEVPATH to
$PHYSDEVPATH in bluetooth.sh, i. e. revert to the solution I sent in
#351106.
Marco: comments on this? will this solution work for all cases in your opinion?
In addition it is neccessary to link /etc/udev/bluez-pcmcia-support.rules to
/etc/udev/rules.d/86-bluez-pcmcia-support.rules.
yes unfortunately this is a known bug in dh_installudev, I'll look forward for a
workaround.
thanks for your report,
filippo
--
Filippo Giunchedi - http://esaurito.net
PGP key: 0x6B79D401
random quote follows:
All language designers are arrogant. Goes with the territory...
-- Larry Wall
signature.asc
Description: Digital signature
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
On Wednesday 19 July 2006 12:00, Filippo Giunchedi wrote:
[I'm CCing udev maintainer to have some comments (if any)]
On Wed, Jul 19, 2006 at 10:57:04AM +0200, [EMAIL PROTECTED] wrote:
The udev rules supplied by the package don't work. At least on my
system tested with a SPHINX and a Sitecom card.
The solution is to replace ENV{BUS} by ENV{PHYSDEVBUS} in
bluez-pcmcia-support.udev and to correspondingly change $DEVPATH to
$PHYSDEVPATH in bluetooth.sh, i. e. revert to the solution I sent in
#351106.
Marco: comments on this? will this solution work for all cases in your
opinion?
Just one further comment: The solution is propose is not my own invention.
It's what SuSE has been doing for a long time. (I already mentioned this in
#351106.)
Kind regards,
Felix
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
