Date: Sun, 27 Sep 2015 06:19:51 -0700 From: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> To: Dirk Engling <erdgeist@erdgeist.org> Cc: "freebsd-bluetooth@freebsd.org" <freebsd-bluetooth@freebsd.org> Subject: Re: first shot at user friendly bluetooth-config script Message-ID: <CAFPOs6qu6h3=wQLH_62ekP3X37Q_qwCOf%2BsW2pq1CA=jvPTdpw@mail.gmail.com> In-Reply-To: <56072A53.4010005@erdgeist.org> References: <56072A53.4010005@erdgeist.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello! thank you for your work. can you please put it into review? also, what is the proposed usage scenario? can you please describe it? thanks max On Sat, Sep 26, 2015 at 4:29 PM, Dirk Engling <erdgeist@erdgeist.org> wrote: > Find attached a script that tries to tie together essential parts of the > bluetooth sub-system in a human friendly manner. > > Currently I implemented all the steps necessary to get a hid running, > and helping out the user along the way. Next up I want to implement > setting up everything necessary to get connected using the DUN profile, > if available. > > Still some questions remain about pairing: besides grepping debug.log's > output, is there a reliable way to get pairing status? Looking into > /var/db/hcsecd.keys may give me positive results, but info like whether > a PIN_Code_Negative_Reply has been sent to the device because of a wrong > pin code would be helpful. It would also be helpful to know if the > device never sent a PIN_Code_Request in the first place. And how do you > use hcsecd to actively start pairing? > > The script's style may still be a little concise, but is extensively > documented, I will factor out code blocks into functions later. I am > also trying to make it more usable from a script by adding a quiet mode > that is not interactive and tries to automatically resolve everything by > the info passed on command line. > > Now I wonder, where the code will be heading. Is it likely to go into > the bluetooth framework or should I start writing a port? Do you have > suggestions where the user might be provided additional info on how to > continue, especially if stuff breaks? > > Regards, > > erdgeist > > _______________________________________________ > freebsd-bluetooth@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth > To unsubscribe, send any mail to " > freebsd-bluetooth-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFPOs6qu6h3=wQLH_62ekP3X37Q_qwCOf%2BsW2pq1CA=jvPTdpw>