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
* 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
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:
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
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
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
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
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{}.
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
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)
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
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
[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
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
14 matches
Mail list logo
