[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [bluetooth-dev] hci inquiry timer
As what I can see right now,
1. No it isn't...
Though this timer has to be deleted when we receive a Command Status, since we wont get a Command Complete for this command.
2. The problem with the inquiry is that we will block the user application until we have received a Inquiry complete command, and this might take up to 40 seconds. But I agree that there is no reason for letting the inquiry command go through if other HCI commands are pending.
>From: Gordon McNutt [mailto:firstname.lastname@example.org]
>Sent: Thursday, March 15, 2001 12:05 AM
>Subject: [bluetooth-dev] hci inquiry timer
>This appears in hci.c : send_inq_cmd_block:
> /*FIXME: currently we have no timer for inquiry */
> tmp = send_cmd(cmd, len);
>Is there a reason inquiry commands can't use the same timer as
>blocking HCI commands? It looks like we're letting inquiry commands go
>through even if another (different) HCI command is pending. Is there a
>reason for this?
>To unsubscribe from this list: send the line "unsubscribe
>the body of a message to email@example.com
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to firstname.lastname@example.org