From: Matthias Thomae <bluez@thomae-privat.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Edd Dumbill <edd@usefulinc.com>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] starting order in debian init script for bluez
Date: Sun, 11 Jul 2004 12:25:22 +0200 [thread overview]
Message-ID: <40F11592.8090704@thomae-privat.de> (raw)
In-Reply-To: <1089485717.13519.75.camel@pegasus>
Hi Marcel, Edd,
Marcel Holtmann wrote:
>>Wouldn't it be better to start it before rfcomm/sdpd/pand/hidd, to allow
>>these services to use the dongle immediately?
>
> no, because the hcid/sdpd/rfcomm/pand/hidd etc. can be started without
> any real device attached. And when you run hid2hci to switch into HCI
> mode, the hidd must already running to accept the reconnect from your
> HID devices.
Ok, I see.
>>I had a problem connection a Logitech-Hub-dongled PC to a NAP, and
>>changing the order (and adding 'sleep 2' before start_pan, but that's a
>>different story I guess) helped here.
>
>
> If you start a client connection then this is really a different story.
So it would still make sense to call hci2hid before rfcomm/dund/pand,
wouldn't it?
BTW, this is exactly the case in the init script contained in
bluez-utils 2.8:
start)
echo -n "Starting $DESC:"
if $HCID_ENABLE && [ -x "$HCID_EXEC" -a -f "$HCID_CONFIG" ] ; then
$HCID_EXEC -f $HCID_CONFIG
echo -n " $HCID_NAME"
fi
if $SDPD_ENABLE && [ -x "$SDPD_EXEC" ] ; then
$SDPD_EXEC
echo -n " $SDPD_NAME"
fi
if $HIDD_ENABLE && [ -x "$HIDD_EXEC" ] ; then
$HIDD_EXEC $HIDD_OPTIONS --server || true
echo -n " $HIDD_NAME"
fi
if $HID2HCI_ENABLE && [ -x "$HID2HCI_EXEC" ] ; then
$HID2HCI_EXEC --tohci > /dev/null 2>&1 || true
echo -n " $HID2HCI_NAME"
fi
if $RFCOMM_ENABLE && [ -x "$RFCOMM_EXEC" -a -f "$RFCOMM_CONFIG"
] ; then
$RFCOMM_EXEC -f $RFCOMM_CONFIG bind all || true
echo -n " $RFCOMM_NAME"
fi
if $DUND_ENABLE && [ -x "$DUND_EXEC" -a -n "$DUND_OPTIONS" ] ; then
$DUND_EXEC $DUND_OPTIONS
echo -n " $DUND_NAME"
fi
if $PAND_ENABLE && [ -x "$PAND_EXEC" -a -n "$PAND_OPTIONS" ] ; then
$PAND_EXEC $PAND_OPTIONS
echo -n " $PAND_NAME"
fi
echo "."
;;
Regards.
Matthias
next prev parent reply other threads:[~2004-07-11 10:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-10 18:27 [Bluez-devel] starting order in debian init script for bluez Matthias Thomae
2004-07-10 18:55 ` Marcel Holtmann
2004-07-11 10:25 ` Matthias Thomae [this message]
2004-07-11 15:22 ` Marcel Holtmann
2004-07-11 15:27 ` Matthias Thomae
2004-07-11 17:17 ` Edd Dumbill
2004-07-11 19:32 ` Matthias Thomae
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40F11592.8090704@thomae-privat.de \
--to=bluez@thomae-privat.de \
--cc=bluez-devel@lists.sourceforge.net \
--cc=edd@usefulinc.com \
--cc=marcel@holtmann.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.