ok, lemme go rescue my ar9462 hardware and test again.
-a
On Tue, 23 Apr 2019 at 12:46, Serge Semenenko wrote:
> in /boot/device.hints I have
> hint.ath.0.btcoex_profile="wb222"
>
> it seems working
>
> kernel: ar9300_hw_attach: ar9300_eeprom_attach returned 0
> kernel: ath0: Enabling WB222 BTC
in /boot/device.hints I have
hint.ath.0.btcoex_profile="wb222"
it seems working
kernel: ar9300_hw_attach: ar9300_eeprom_attach returned 0
kernel: ath0: Enabling WB222 BTCOEX
kernel: ath0: [HT] enabling HT modes
kernel: ath0: [HT] enabling short-GI in 20MHz mode
kernel: ath0: [HT] 1 stream STBC re
Do you have the kernel environment variable setup to say it's a WB222?
-a
On Tue, 23 Apr 2019 at 12:37, Serge Semenenko wrote:
> Could it matter that I load modules from rc.conf?
>
> kld_list="if_ath if_ath_pci linux linsysfs linprocfs xhci umass ums
> snd_hda /boot/modules/i915kms.ko /boot/m
Could it matter that I load modules from rc.conf?
kld_list="if_ath if_ath_pci linux linsysfs linprocfs xhci umass ums snd_hda
/boot/modules/i915kms.ko /boot/modules/acpi_call.ko"
вс, 21 апр. 2019 г. в 11:05, Matthias Apitz :
> El día sábado, abril 20, 2019 a las 02:16:49p. m. +0300, Serge Semene
El día sábado, abril 20, 2019 a las 02:16:49p. m. +0300, Serge Semenenko
escribió:
> Hi
>
> It works for me with such section in devd.conf
>
> attach 200 {
>device-name "ubt[0-9]+";
>match "vendor" "0x0cf3";
>match "product" "0xe006";
>action "sleep 2 && /usr/sbi
ooo please send me a pull request with the device id update!
-a
On Sat, 20 Apr 2019 at 04:17, Serge Semenenko wrote:
> Hi
>
> It works for me with such section in devd.conf
>
> attach 200 {
>device-name "ubt[0-9]+";
>match "vendor" "0x0cf3";
>match "product" "0xe006";
>
Hi
It works for me with such section in devd.conf
attach 200 {
device-name "ubt[0-9]+";
match "vendor" "0x0cf3";
match "product" "0xe006";
action "sleep 2 && /usr/sbin/ath3kfw -d $ugen && sleep 2 &&
/etc/rc.d/bluetooth quietstart $device-name";
};
More info:
# unam
Hi!
Ok, I'm going to have to find my NIC and see what's going on.
-a
>
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.or
El día Thursday, April 18, 2019 a las 07:02:38PM +0200, Matthias Apitz escribió:
> El día Thursday, April 18, 2019 a las 08:05:53AM -0700, Adrian Chadd escribió:
>
> > 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
hi,
On Thu, 18 Apr 2019 at 10:02, Matthias Apitz wrote:
> El día Thursday, April 18, 2019 a las 08:05:53AM -0700, Adrian Chadd
> escribió:
>
> > 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 eith
El día Thursday, April 18, 2019 a las 08:05:53AM -0700, Adrian Chadd escribió:
> 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
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,
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 wrote:
> >
> > I have booted the other C720 from USB and here are the results:
>
Ok, so it found and loaded in the bluetooth firmware into the bluetooth NIC
RAM.
https://www.freebsd.org/doc/handbook/network-bluetooth.html
Your goal is to have devices show up in in an inquiry command.
-a
On Thu, 18 Apr 2019 at 07:50, Matthias Apitz wrote:
>
> I have booted the other C72
I have booted the other C720 from USB and here are the results:
root@c720-r342378-usb:~guru/ath3k/src/usr.bin/ath3k # grep ath dmesg*
ath0: mem 0xe040-0xe047 at device 0.0 on pci1
ath0: Enabling WB222 BTCOEX
ath0: [HT] enabling HT modes
ath0: [HT] enabling short-GI in 20MHz mode
ath0: [
Try loading firmware, see if it can do a bt scan.
Try also bringing up the 2g wifi and connect to a 2g station; see if that
also allows a bt scan to work.
-a
On Wed, 17 Apr 2019 at 11:17, Matthias Apitz wrote:
> Am Mittwoch, 17. April 2019 19:59:17 CEST schrieb Adrian Chadd
> :
> > no flashi
Am Mittwoch, 17. April 2019 19:59:17 CEST schrieb Adrian Chadd
:
no flashing occurs. it's running out of ram on the chip.
-a
So, what do you want me to test exactly?
ma
--
Sent from my Ubuntu phone
http://www.unixarea.de/
___
freebsd-wireless@fr
no flashing occurs. it's running out of ram on the chip.
-a
On Wed, 17 Apr 2019 at 10:56, Matthias Apitz wrote:
> Am Mittwoch, 17. April 2019 18:59:08 CEST schrieb Adrian Chadd
> :
> > Did you copy it into /usr/share/ or did you pass the command line arg in
> to
> > set the base directory? :)
Am Mittwoch, 17. April 2019 18:59:08 CEST schrieb Adrian Chadd
:
Did you copy it into /usr/share/ or did you pass the command line arg in to
set the base directory? :)
I was aware of the flag -f to specify the dir or file of the
firmware to use. I did not set this by intention to *not* flash
t
Did you copy it into /usr/share/ or did you pass the command line arg in to
set the base directory? :)
-a
On Wed, 17 Apr 2019 at 09:57, Matthias Apitz wrote:
> El día Wednesday, April 17, 2019 a las 02:35:51PM +, Alexey Dokuchaev
> escribió:
>
> > On Tue, Apr 16, 2019 at 12:34:12PM +0200,
El día Wednesday, April 17, 2019 a las 02:35:51PM +, Alexey Dokuchaev
escribió:
> On Tue, Apr 16, 2019 at 12:34:12PM +0200, Matthias Apitz wrote:
> > # ./ath3kfw -D -d ugen0.3 -I
> > ath3kfw: opening dev 0.3
> > ath3k_is_3012: found AR3012
> > main: state=0x0e
> > ROM version: 285343744, buil
On Tue, Apr 16, 2019 at 12:34:12PM +0200, Matthias Apitz wrote:
> # ./ath3kfw -D -d ugen0.3 -I
> ath3kfw: opening dev 0.3
> ath3k_is_3012: found AR3012
> main: state=0x0e
> ROM version: 285343744, build version: 155, ram version: 155, ref clock=1
> ath3kfw: ath3k_fw_read: open:
> /usr/share/firmwa
El día lunes, abril 15, 2019 a las 05:35:03p. m. +, Alexey Dokuchaev
escribió:
> Ah, OK, I understand. Anyways, now that this little confusion is resolved,
> could you try to upload the firmware using this tool? For me it didn't
> work, but that might be because of the particular hardware (
i thought i had the various combinations working when i last poked at this
stuff. I'll have to go re-test it all.
-a
On Mon, 15 Apr 2019 at 10:35, Alexey Dokuchaev wrote:
> On Mon, Apr 15, 2019 at 02:52:17PM +0200, Matthias Apitz wrote:
> > I have not missed (or deleted) any mail in this thre
On Mon, Apr 15, 2019 at 02:52:17PM +0200, Matthias Apitz wrote:
> I have not missed (or deleted) any mail in this thread of 24++ mails.
> But as Adrian said "Does ath3k load OK?" I was confused and thinking
> in a loadable kernel module.
Ah, OK, I understand. Anyways, now that this little confusi
El día lunes, abril 15, 2019 a las 12:26:52p. m. +, Alexey Dokuchaev
escribió:
> I've posted exact instructions how to use it and debug log earlier in
> this thread, you being CC'ed, I don't understand how could you've missed
> those emails.
I have not missed (or deleted) any mail in this th
On Sat, Apr 13, 2019 at 12:35:30PM -0700, Adrian Chadd wrote:
> On Sat, 13 Apr 2019 at 12:14, Alexey Dokuchaev wrote:
> > ...
> > If you tell me how to implement Linuxish usleep_range() correctly in
> > our userland, I can do that. :-)
>
> usleep_range() is just the same as usleep() at either min,
On Mon, Apr 15, 2019 at 06:48:36AM +0200, Matthias Apitz wrote:
> I git cloned it and built it, but this does not give any kernel module
> to load: [...]
>
> $ ./ath3kfw
> Usage: ath3kfw (-D) -d ugenX.Y (-f firmware path) (-I)
> -D: enable debugging
> -d: device to operate upon
> -f: f
it's a userland program. :-) All ath3k in linux does is detect the hardware
and squeeze firmware into it. That's literally it.
-adrian
On Sun, 14 Apr 2019 at 21:48, Matthias Apitz wrote:
> El día domingo, abril 14, 2019 a las 09:42:46a. m. -0700, Adrian Chadd
> escribió:
>
> > no, it's the use
El día domingo, abril 14, 2019 a las 09:42:46a. m. -0700, Adrian Chadd escribió:
> no, it's the userland ath3kfw tool from my git (github.com/erikarn/ath3k)
>
> Those NICs need firmware/config squirted onto them after ath(4) loads and
> sets up the btcoex.
>
>
I git cloned it and built it, but
no, it's the userland ath3kfw tool from my git (github.com/erikarn/ath3k)
Those NICs need firmware/config squirted onto them after ath(4) loads and
sets up the btcoex.
-adrian
On Sun, 14 Apr 2019 at 09:38, Matthias Apitz wrote:
> El día domingo, abril 14, 2019 a las 09:18:18a. m. -0700, Adria
El día domingo, abril 14, 2019 a las 09:18:18a. m. -0700, Adrian Chadd escribió:
> ok, so you've added the WB222 coex bits. Does ath3k load OK?
>
I do not have this module:
root@c720-r342378:/home/guru # uname -a
FreeBSD c720-r342378 13.0-CURRENT FreeBSD 13.0-CURRENT GENERIC amd64
root@c720-r3
ok, so you've added the WB222 coex bits. Does ath3k load OK?
-a
On Sun, 14 Apr 2019 at 09:02, Matthias Apitz wrote:
> El día domingo, abril 14, 2019 a las 08:56:52a. m. -0700, Adrian Chadd
> escribió:
>
> > hi!
> >
> > Ok, so there's two parts:
> >
> > * loading in the firmware and/or bt nic
El día domingo, abril 14, 2019 a las 08:56:52a. m. -0700, Adrian Chadd escribió:
> hi!
>
> Ok, so there's two parts:
>
> * loading in the firmware and/or bt nic setup (clock rate, etc) via
> ath3kfw; and
> * bluetooth coex/antenna setup in ath(4).
>
> The latter I can do. The former may require
hi!
Ok, so there's two parts:
* loading in the firmware and/or bt nic setup (clock rate, etc) via
ath3kfw; and
* bluetooth coex/antenna setup in ath(4).
The latter I can do. The former may require USB stack debugging.
Which NIC is in the C720? Ar9485, right?
-adrian
On Sun, 14 Apr 2019 at 0
El día sábado, abril 13, 2019 a las 02:20:06p. m. +, Alexey Dokuchaev
escribió:
> On Fri, Apr 12, 2019 at 05:12:18PM +, Alexey Dokuchaev wrote:
> > I've then rebooted back into FreeBSD. Apparently, this AR3012 hardware
> > is very fragile, it can be easily left in confused state and won'
On Sat, 13 Apr 2019 at 12:14, Alexey Dokuchaev wrote:
> On Sat, Apr 13, 2019 at 11:44:25AM -0700, Adrian Chadd wrote:
> > Hm, is this a problem with our usb3 stack itself?
> >
> > If you send me a pull request against ath3k I'll merge it into my git
> > tree just for completeness.
>
> If you tell
On Sat, Apr 13, 2019 at 11:44:25AM -0700, Adrian Chadd wrote:
> Hm, is this a problem with our usb3 stack itself?
>
> If you send me a pull request against ath3k I'll merge it into my git
> tree just for completeness.
If you tell me how to implement Linuxish usleep_range() correctly in our
userla
Hm, is this a problem with our usb3 stack itself?
If you send me a pull request against ath3k I'll merge it into my git tree
just for completeness.
Maybe we need to loop in hps@ with a bunch of usbdump output to see what
the transactions look like...
-adrian
On Sat, 13 Apr 2019 at 07:21, Ale
On Fri, Apr 12, 2019 at 05:12:18PM +, Alexey Dokuchaev wrote:
> I've then rebooted back into FreeBSD. Apparently, this AR3012 hardware
> is very fragile, it can be easily left in confused state and won't accept
> further commands, "usbconfig reset" does not help. To avoid this, it is
> better
Well, yeah, qualcomm developers did a lot of the linux ath9k/ath3k support
:)
-a
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@fre
On Thu, Apr 11, 2019 at 02:23:50PM +, Alexey Dokuchaev wrote:
> On Thu, Apr 11, 2019 at 06:36:26AM -0700, Adrian Chadd wrote:
> > I have a tool to upload firmware -- github.com/erikarn/ath3k.
> > See if that helps!
>
> Something's wrong:
>
> $ git clone https://github.com/erikarn/ath3k.git
>
> Hi,
>
I'm trying to figure out an ath sta mode crash and some ath10k things. I
have the AR9485 / AR9462 hardware here so please just keep poking me here
and on irc over the next couple weeks to get it working.
There's also some weird antenna coex stuff that needs setting up in the HAL
too tha
On Thu, Apr 11, 2019 at 04:05:27PM +, Matthias Apitz wrote:
> On Thu, 11 Apr 2019 14:23:50 +, Alexey Dokuchaev wrote:
> > On Thu, Apr 11, 2019 at 06:36:26AM -0700, Adrian Chadd wrote:
> >> I have a tool to upload firmware -- github.com/erikarn/ath3k.
> >> See if that helps!
> >
> > Somethin
On Thu, 11 Apr 2019 14:23:50 +, Alexey Dokuchaev wrote:
> On Thu, Apr 11, 2019 at 06:36:26AM -0700, Adrian Chadd wrote:
>> I have a tool to upload firmware -- github.com/erikarn/ath3k.
>> See if that helps!
>
> Something's wrong:
>
> $ git clone https://github.com/erikarn/ath3k.git
> $ cd a
On Thu, Apr 11, 2019 at 06:36:26AM -0700, Adrian Chadd wrote:
> I have a tool to upload firmware -- github.com/erikarn/ath3k.
> See if that helps!
Something's wrong:
$ git clone https://github.com/erikarn/ath3k.git
$ cd ath3k/src/usr.bin/ath3k
$ make
$ usbconfig list | grep 0x0930
ugen2
I have a tool to upload firmware - github.com/erikarn/ath3k. See if that
helps!
-a
On Thu, 11 Apr 2019 at 06:19, Alexey Dokuchaev wrote:
> On Thu, Apr 11, 2019 at 03:13:28PM +0200, Matthias Apitz wrote:
> > # usbconfig list
> > ...
> > ugen0.3: at usbus0, cfg=0 md=HOST
> > spd=FULL (12Mbps)
On Thu, Apr 11, 2019 at 03:13:28PM +0200, Matthias Apitz wrote:
> # usbconfig list
> ...
> ugen0.3: at usbus0, cfg=0 md=HOST
> spd=FULL (12Mbps) pwr=ON (100mA)
>
> The later vendor 0x0489 product 0xe056 seems to be:
>
> https://cateee.net/lkddb/web-lkddb/BT_ATH3K.html
Yes, it is also Atheros AR
El día jueves, abril 11, 2019 a las 12:52:42p. m. +, Alexey Dokuchaev
escribió:
> > ath0: Enabling WB222 BTCOEX
> > ...
> >
> > But I don't know how to further enable any BT device.
>
> What does "usbconfig list" say about your BT device? Mine is
> 0x0930:0x021c, which is AR3012 with sflas
On Thu, Apr 11, 2019 at 12:46:47PM +0200, Matthias Apitz wrote:
> > ...
> > I've just stumbled upon this email* of Adrian's that tells how to enable
> > Bluetooth Coexistence by adding ``hint.ath.0.btcoex_profile="wb222"'' to
> > /boot/device.hints (for AR9462 cards). I've done that, and logs tell
El día jueves, abril 11, 2019 a las 09:27:58a. m. +, Alexey Dokuchaev
escribió:
> On Wed, Apr 10, 2019 at 03:22:50PM +, Alexey Dokuchaev wrote:
> > On Tue, Apr 09, 2019 at 04:03:44PM +, Alexey Dokuchaev wrote:
> > > On Sun, Jun 02, 2013 at 09:59:05AM -0700, Adrian Chadd wrote:
> > > >
On Wed, Apr 10, 2019 at 03:22:50PM +, Alexey Dokuchaev wrote:
> On Tue, Apr 09, 2019 at 04:03:44PM +, Alexey Dokuchaev wrote:
> > On Sun, Jun 02, 2013 at 09:59:05AM -0700, Adrian Chadd wrote:
> > > Hi,
> > >
> > > It's supported in -HEAD.
>
> Driver attaches correctly if I move module loa
On Tue, Apr 09, 2019 at 04:03:44PM +, Alexey Dokuchaev wrote:
> On Sun, Jun 02, 2013 at 09:59:05AM -0700, Adrian Chadd wrote:
> > Hi,
> >
> > It's supported in -HEAD.
>
> Hmm, almost six years later, apparently it is still not:
>
> % uname -UK
> 1300014 1300014
>
> # kldload if_ath_pci if_a
On Sun, Jun 02, 2013 at 09:59:05AM -0700, Adrian Chadd wrote:
> Hi,
>
> It's supported in -HEAD.
Hmm, almost six years later, apparently it is still not:
% uname -UK
1300014 1300014
# kldload if_ath_pci if_ath
% pciconf -lv | tail -4
none2@pci0:3:0:0: class=0x028000 card=0x66ad chip=
Hi,
It's supported in -HEAD.
Bluetooth may or may not work. I've not sat down and focused on that, sorry.
adrian
On 2 June 2013 08:00, Miguel Clara wrote:
> Hi,
>
> Sorry for the direct mail, but I not sure about the correct steps to
> take when a driver is missing... if there a mailling list
55 matches
Mail list logo
