Hi Marcel,
Marcel Holtmann <marcel <at> holtmann.org> writes:
> Hi Peter,
>
> > I'm not that familiar with the architecture of BlueZ but with the
> > experiences for our own stack I can tell you this is not trivial. The main
> > problem here is that the Bluetooth Stack is not stateless. One possible
> > solution is to feed the reset done event to the higher layers (l2cap). But
> > than L2cap must be modified to correctly shut down all connections. It
> > would be easier if the HCI layer tracks the state of all ACL and SCO
> > connections (Marcel ??). Than a reset done event can be handled like a
> > unexpected link loss on all active connections and the higher layers do
> > not need any modifications (hopefully).
>
> we can do this and actually calling "hcitool cc" does this already, but
> it waits indeed for a timeout of the HCI_Disconnect.
Could you give a few more details on this one, please? What I want to do is what
Pieter suggested: have the Hardware Error event trigger an unexpected link loss
on all active connections.
Thanks,
Catalin
-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register
by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel