that means it SHOULD be ready for normal HCI operation. bcdDevice=1 is what
the driver uses to determine if it's only in the boot ROM. Yours either got
it in a previous boot, or it has a ROM with the full firmware.
Try starting bluetooth now and do an inquiry.
-a
On Thu, 18 Apr 2019 at 08:03, Alexey Dokuchaev <da...@freebsd.org> wrote:
> On Thu, Apr 18, 2019 at 07:58:34AM -0700, Adrian Chadd wrote:
> > Ok, so it found and loaded in the bluetooth firmware into the
> > bluetooth NIC RAM.
>
> Why do you think so?
>
> > On Thu, 18 Apr 2019 at 07:50, Matthias Apitz <g...@unixarea.de> wrote:
> > >
> > > I have booted the other C720 from USB and here are the results:
> > >
> > > # ./ath3kfw -D -d ugen0.4 -I
> > > ath3kfw: opening dev 0.4
> > > ath3k_is_3012: found AR3012
> > > main: AR3012; bcdDevice=2, exiting
>
> /* See if its an AR3012 */
> if (ath3k_is_3012(&d)) {
> is_3012 = 1;
>
> /* If it's bcdDevice > 1, don't attach */
> if (d.bcdDevice > 0x0001) {
> ath3k_debug("%s: AR3012; bcdDevice=%d, exiting\n",
> __func__,
> d.bcdDevice);
> exit(0);
> }
> }
>
> It looks to me it never reached the stage of loading the firmware because
> of bcdDevice=2.
>
> ./danfe
>
_______________________________________________
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
