Hello
Recently a user told me that he needed to use hex2hcd to get his
Broadcom firmware loaded by his bluetooth adaptor. We wonder about why
it's not installed by default when we build with "experimental"
configure option:
if EXPERIMENTAL
noinst_PROGRAMS += tools/bdaddr tools/avinfo tools/avtest \
tools/scotest tools/amptest tools/hwdb \
tools/hcieventmask tools/hcisecfilter \
tools/btmgmt tools/btinfo tools/btattach \
tools/btsnoop tools/btproxy tools/btiotest \
tools/cltest tools/seq2bseq tools/hex2hcd \
tools/ibeacon tools/btgatt-client
(in Makefile.tools)
Thanks a lot for the info
El dom, 14-09-2014 a las 12:07 +0200, Pacho Ramos escribió:
> Hello
>
> Recently a user told me that he needed to use hex2hcd to get his
> Broadcom firmware loaded by his bluetooth adaptor. We wonder about why
> it's not installed by default when we build with "experimental"
> configure option:
> if EXPERIMENTAL
> noinst_PROGRAMS += tools/bdaddr tools/avinfo tools/avtest \
> tools/scotest tools/amptest tools/hwdb \
> tools/hcieventmask tools/hcisecfilter \
> tools/btmgmt tools/btinfo tools/btattach \
> tools/btsnoop tools/btproxy tools/btiotest \
> tools/cltest tools/seq2bseq tools/hex2hcd \
> tools/ibeacon tools/btgatt-client
> (in Makefile.tools)
>
> Thanks a lot for the info
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
The same occurs with gatttool :/, do you know why they are explicitly
not installed?