Date: Wed, 22 Apr 2015 10:45:05 -0700 From: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> To: Waitman Gobble <gobble.wa@gmail.com> Cc: "freebsd-bluetooth@freebsd.org" <freebsd-bluetooth@freebsd.org> Subject: Re: question about bthidd client.c Message-ID: <CAFPOs6oySELB%2BFsf8nt92OAtizkEn425qeFmy-oc9NHdkFwUNA@mail.gmail.com> In-Reply-To: <CAFuo_fzVganO6M07neAWBVqda1vzV9VNWurU6EsP_3Mc78-dMA@mail.gmail.com> References: <CAFuo_fzVganO6M07neAWBVqda1vzV9VNWurU6EsP_3Mc78-dMA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 21, 2015 at 10:34 PM, Waitman Gobble <gobble.wa@gmail.com> wrote: > > I notice that if bthidd is running, and bluetooth is not active, or > the configured host is out of range, the client_rescan() function > generates new vkbd devices every 20 seconds or so. I believe this will > eventually lock up the machine. > may be... usually devices will reconnect, i.e. reconnect_initiate would be 1. however, this is a known problem. for whatever reason "cloned" devices are not completely going away when closed. similar problem exists with other "cloned" devices. its not bthidd or bluetooth code specific. thanks max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFPOs6oySELB%2BFsf8nt92OAtizkEn425qeFmy-oc9NHdkFwUNA>